Bug 1696862
| Summary: | foreman-maintain service restart - should not require foreman-maintain-hammer.yml | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | sthirugn <sthirugn> |
| Component: | Satellite Maintain | Assignee: | Martin Bacovsky <mbacovsk> |
| Status: | CLOSED ERRATA | QA Contact: | Jameer Pathan <jpathan> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4.2 | CC: | apatel, bbuckingham, egolov, inecas, jpathan, kgaikwad, mbacovsk, pcreech |
| Target Milestone: | 6.6.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-foreman_maintain-0.4.5 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-22 19:49:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
sthirugn@redhat.com
2019-04-05 19:04:36 UTC
Hi Anurag, Can you or someone on foreman-maintain take a quick look at this bugzilla. Is this change in behavior intended or required? This bug originated from investigation in to the following bugzilla created for satellite-clone: bug 1696731. Brad, what is probably going on here is that foreman-maintain is trying to obtain the hammer credentials from existing hammer config and if it fails it tries installer answer file. If no valid information is found it prompts for the credentials. The behavior described can typically happen when admin password was changed in UI/DB and hammer config was not updated accordingly. This has not changed recently and is not a regression. If there are any ideas how to improve the procedure let me know. What can be done and what I'll use this bug to track is that the server ping will be performed by direct call to the API outside of hammer. The call does not require auth so the credentials will not be needed and service restart won't to ask for it. However the described behavior will persist for other operations requiring hammer. Created redmine issue https://projects.theforeman.org/issues/26779 from this bug Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26779 has been resolved. This issue is fixed in upstream and released in foreman-maintain 0.4.5. Verified Verified with: - Satellite 6.6.0 snap - rubygem-foreman_maintain-0.4.8-1.el7sat.noarch Test steps: - Have invalid admin password in files .hammer/cli.modules.d/foreman.yml, /etc/foreman-maintain/foreman-maintain-hammer.yml, and /etc/foreman-installer/scenarios.d/satellite-answers.yaml - Or remove files .hammer/cli.modules.d/foreman.yml, /etc/foreman-maintain/foreman-maintain-hammer.yml - Run # satellite-maintain service restart # satellite-maintain service restart Running Restart Services ================================================================================ Check if command is run as root user: [OK] -------------------------------------------------------------------------------- Restart applicable services: Stopping the following service(s): rh-mongodb34-mongod, postgresql, qdrouterd, qpidd, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, smart_proxy_dynflow_core, tomcat, dynflowd, httpd, puppetserver, foreman-proxy / All services stopped Starting the following service(s): rh-mongodb34-mongod, postgresql, qdrouterd, qpidd, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, smart_proxy_dynflow_core, tomcat, dynflowd, httpd, puppetserver, foreman-proxy - All services started [OK] -------------------------------------------------------------------------------- Observation: - "satellite-maintain service restart" don't require hammer password to run. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3172 |