Bug #19276
closed--reset should stop workers or it will fail on pulp-manage-db
Description
If you do not do katello-service stop before --reset you hit this:
[ WARN 2017-04-14 04:04:41 verbose] /Stage[main]/Pulp::Database/Exec[migrate_pulp_db]/returns: The following processes are still running, please stop the running workers before retrying the pulp-manage-db command.
[ WARN 2017-04-14 04:04:41 verbose] /Stage[main]/Pulp::Database/Exec[migrate_pulp_db]/returns: scheduler@satellite.satlab.lan
[ WARN 2017-04-14 04:04:41 verbose] /Stage[main]/Pulp::Database/Exec[migrate_pulp_db]/returns: reserved_resource_worker-0@satellite.satlab.lan
[ WARN 2017-04-14 04:04:41 verbose] /Stage[main]/Pulp::Database/Exec[migrate_pulp_db]/returns: resource_manager@satellite.satlab.lan
[ WARN 2017-04-14 04:04:41 verbose] /Stage[main]/Pulp::Database/Exec[migrate_pulp_db]/returns: reserved_resource_worker-1@satellite.satlab.lan
[ERROR 2017-04-14 04:04:41 verbose] pulp-manage-db && touch /var/lib/pulp/init.flag returned 70 instead of one of [0]
[ERROR 2017-04-14 04:04:41 verbose] /usr/share/ruby/vendor_ruby/puppet/util/errors.rb:106:in `fail'
[ERROR 2017-04-14 04:04:41 verbose] /usr/share/ruby/vendor_ruby/puppet/type/exec.rb:160:in `sync'
Adding in katello-service stop