Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionChristian Marineau
2017-08-14 15:51:30 UTC
Document URL:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/installation_guide
Section Number and Name:
7.1. UPDATING SATELLITE SERVER
6. Perform the update
[https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/installation_guide/updating_satellite_server_capsule_server_and_content_hosts#updating_satellite_server_to_next_minor_version]
Describe the issue:
If we follow the instructions step by step and the "yum update" did not update the kernel, we might not have reboot the server and the katello-service will be stopped.
When running the following:
# satellite-installer --scenario satellite --upgrade --noop
If will fail with postgres and httpd error because services are not responding:
/Stage[main]/Foreman::Database::Postgresql/Postgresql::Server::Db[foreman]/Postgresql::Server::Role[foreman]/Postgresql_psql[CREATE ROLE foreman ENCRYPTED PASSWORD ****]: Could not evaluate: Error evaluating 'unless' clause, returned pid 97580 exit 2: 'psql: could not connect to server: No such file or directory
/Stage[main]/Candlepin::Database::Postgresql/Postgresql::Server::Db[candlepin]/Postgresql::Server::Role[candlepin]/Postgresql_psql[CREATE ROLE candlepin ENCRYPTED PASSWORD ****]: Could not evaluate: Error evaluating 'unless' clause, returned pid 97584 exit 2: 'psql: could not connect to server: No such file or directory
Report processor failed: Could not send report to Foreman at https://mysatellite.com/api/reports: Connection refused - connect(2)
Suggestions for improvement:
Option 1. Modify the documentation so that we make the user reboot no matter what.
Option 2. Add an extra step to make the user start katello-service if they want to run the --noop
Option 3. Modify the --noop option to Warn that services are stopped and they must be started.
Additional info:
This could be leading to a situation where we think that would be an issue with the upgrade and prevent the user from moving forward.
Hello Christian
Unfortunately, it is not safe to have Satellite Server running after doing a `yum update` and before running the upgrade step.
we have this text in some sections:
"Because the above "no operation" command does not actually create the files, and some Puppet resources in the module expect them to be there, some failure messages are to be expected. "
see "Upgrading a Connected Satellite Server" for example.