Description of problem: db-control advices to stop all services except "postgresql" on a system with only "postgresql92-postgresql" installed Version-Release number of selected component (if applicable): Satellite-5.7.0-RHEL6-re20141114.0-x86_64 # rpm -qa | grep -e postgresql -e dobby | sort postgresql-8.4.20-1.el6_5.x86_64 postgresql92-postgresql-9.2.8-2.el6.x86_64 postgresql92-postgresql-contrib-9.2.8-2.el6.x86_64 postgresql92-postgresql-libs-9.2.8-2.el6.x86_64 postgresql92-postgresql-pltcl-9.2.8-2.el6.x86_64 postgresql92-postgresql-server-9.2.8-2.el6.x86_64 postgresql92-runtime-1.1-21.el6.x86_64 postgresql-jdbc-8.4.704-2.el6.noarch postgresql-libs-8.4.20-1.el6_5.x86_64 spacewalk-backend-sql-postgresql-2.3.3-18.el6sat.noarch spacewalk-dobby-2.3.2-18.el6sat.noarch spacewalk-java-postgresql-2.3.8-67.el6sat.noarch spacewalk-postgresql-2.3.0-1.5.el6sat.noarch spacewalk-setup-postgresql-2.3.0-8.el6sat.noarch How reproducible: always Steps to Reproduce: 1. Have Satellite with embedded PostgreSQL 9.2 DB 2. # rhn-satellite restart # make sure all your services are running 3. # db-control restore /some/backup Actual results: # db-control restore /tmp/tmp.5J0Zhj6na1/online-backup-dir/backup There are running spacewalk services which are using database. Run 'spacewalk-service --exclude=postgresql stop' to stop them. Expected results: Hint could look like: Run 'spacewalk-service --exclude=postgresql92-postgresql stop' to stop them.
Taking ...
Fixed in spacewalk master by commit 1ff960e80118520294d57a1cdf9175c316a8d812 1165070 - use correct service name
Backported to SATELLITE-5.7 as commit 7ed9e038dbf7119d7ed879782798c62a83a325fe 1165070 - use correct service name
With the release of Red Hat Satellite 5.7 on January 12th 2015 this bug is being moved to a Closed Current Release state. The Satellite 5.7 GA Errata: - https://rhn.redhat.com/errata/RHSA-2015-0033.html Satellite 5.7 Release Notes: - https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html-single/Release_Notes/index.html Satellite Customer Portal Blog announcement for release: - https://access.redhat.com/blogs/1169563/posts/1315743 Cliff NOTE: This bug has not been re-verified (moved to RELEASE_PENDING) prior to release. We assume that the bug has indeed been fixed and not regressed since we initially verified it. Please re-open in the future if needed.