~$ rvm gemset create rubysdk-test
@@ -47,7 +53,7 @@ One way you could easily do this is by setting up a new rvm gemset and install t
Next, you can run the following script using admin credentials, it will scan the whole collection database and report any collection that didn't pass the check:
-{% codeblock as python %}
+{% codeblock as ruby %}
require 'arvados'
require 'arvados/keep'
@@ -80,7 +86,11 @@ while true
break if offset > req[:items_available]
end
-invalid.each {|c| puts "#{c[:uuid]} (Created at #{c[:created_at]}): #{c[:error]}" }
+if invalid.empty?
+ puts "No invalid collection manifests found"
+else
+ invalid.each {|c| puts "#{c[:uuid]} (Created at #{c[:created_at]}): #{c[:error]}" }
+end
{% endcodeblock %}
The script will return a final report enumerating any invalid collection by UUID, with its creation date and error message so you can take the proper correction measures, if needed.
@@ -121,6 +131,10 @@ h4. Centos7 package for libpam-arvados depends on the python-pam package, which
As part of story "#9945":https://dev.arvados.org/issues/9945, it was discovered that the Centos7 package for libpam-arvados was missing a dependency on the python-pam package, which is available from the EPEL repository. The dependency has been added to the libpam-arvados package. This means that going forward, the EPEL repository will need to be enabled to install libpam-arvados on Centos7.
+h4. New configuration
+
+Arvados is migrating to a centralized configuration file for all components. During the migration, legacy configuration files will continue to be loaded. See "Migrating Configuration":config-migration.html for details.
+
h3. v1.3.0 (2018-12-05)
This release includes several database migrations, which will be executed automatically as part of the API server upgrade. On large Arvados installations, these migrations will take a while. We've seen the upgrade take 30 minutes or more on installations with a lot of collections.