Bug 1753627
| Summary: | foreman-maintain service restart ends successfully even though qpidd service is not started | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Lucie Vrtelova <lvrtelov> |
| Component: | Satellite Maintain | Assignee: | Martin Bacovsky <mbacovsk> |
| Status: | CLOSED WONTFIX | QA Contact: | Jameer Pathan <jpathan> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.6.0 | CC: | apatel, inecas, jpathan, kgaikwad, mbacovsk |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-09 17:02:24 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: | |||
this could possibly be related to https://bugzilla.redhat.com/show_bug.cgi?id=1781386 Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you. |
Description of problem: Foreman-maintain service restart end successfully even though qpidd service is not started. Version-Release number of selected component (if applicable): rubygem-foreman_maintain-0.4.9-1.el7sat.noarch How reproducible: always Steps to Reproduce: 1. foreman-maintain service restart 2. 3. Actual results: OK Expected results: FAIL Additional info: # foreman-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 | starting qpidd Job for qpidd.service failed because a timeout was exceeded. See "systemctl status qpidd.service" and "journalctl -xe" for details. \ All services started [OK] -------------------------------------------------------------------------------- # foreman-maintain service start --only qpidd Running Start Services ================================================================================ Check if command is run as root user: [OK] -------------------------------------------------------------------------------- Start applicable services: Starting the following service(s): qpidd - starting qpidd Job for qpidd.service failed because a timeout was exceeded. See "systemctl status qpidd.service" and "journalctl -xe" for details. \ All services started [OK] -------------------------------------------------------------------------------- # systemctl status qpidd.service ● qpidd.service - An AMQP message broker daemon. Loaded: loaded (/usr/lib/systemd/system/qpidd.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/qpidd.service.d └─wait-for-port.conf Active: failed (Result: timeout) since Thu 2019-09-19 07:17:50 EDT; 5min ago Docs: man:qpidd(1) http://qpid.apache.org/ Process: 81597 ExecStart=/usr/sbin/qpidd --config /etc/qpid/qpidd.conf (code=killed, signal=TERM) Main PID: 81597 (code=killed, signal=TERM) Sep 19 07:16:20 +hostname+ systemd[1]: Starting An AMQP message broker daemon.... Sep 19 07:17:50 +hostname+ systemd[1]: qpidd.service start-post operation timed out. Stopping. Sep 19 07:17:50 +hostname+ systemd[1]: Failed to start An AMQP message broker daemon.. Sep 19 07:17:50 +hostname+ systemd[1]: Unit qpidd.service entered failed state. Sep 19 07:17:50 +hostname+ systemd[1]: qpidd.service failed. # systemctl restart qpidd.service Job for qpidd.service failed because a timeout was exceeded. See "systemctl status qpidd.service" and "journalctl -xe" for details. # echo $? 1