Bug 1351712
Summary: | rhel-osp-director: 8.0 -> 9.0 upgrade that follows successfull 8.0GA->8.0async update: "openstack undercloud upgrade" exits with error. | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> | ||||
Component: | rhosp-director | Assignee: | Marios Andreou <mandreou> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Omri Hochman <ohochman> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 9.0 (Mitaka) | CC: | dbecker, jason.dobies, jcoufal, lbezdick, mburns, morazi, rhel-osp-director-maint, sasha, tvignaud | ||||
Target Milestone: | ga | Keywords: | Triaged | ||||
Target Release: | 9.0 (Mitaka) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | related to https://bugzilla.redhat.com/show_bug.cgi?id=1353346 | ||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-07-29 14:33:57 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1333977 | ||||||
Attachments: |
|
Description
Alexander Chuzhoy
2016-06-30 15:51:47 UTC
Created attachment 1174667 [details]
install-undercloud.log
Didn't reproduce on: 1. Deploy 8.0async 2. Update undercloud to 9.0 2016-06-30 11:24:43,003 INFO: [1;31mError: /Stage[main]/Apache::Service/Service[httpd]: Failed to call refresh: Could not restart Service[httpd]: Execution of '/bin/systemctl restart httpd' returned 1: Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.[0m could you look for what happend to httpd? config file of httpd and logs? I think bug 1351712 and bug 1353346 are related - they are both about a failed undercloud upgrade for 8..9 and afaics both have the same root symptom, that httpd fails to come up on the undercloud during the upgrade. I think it makes sense to keep both as the issue manifests in slightly different circumstances; update 8.. 8 latest and then upgrade to 9, or upgrade 7..8, and then do the 8..9 upgrade. I see from logs/description that the root cause is httpd not coming up as part of the upgrade. I can't see enough information, either in the install-undercloud.log from bug 1351712 or in the description of bug 1353346. Basically we need the httpd logs. I think the rest of the errors from the trace (e.g. keystone related errors) are a consequence of the httpd not starting. Can we please have the httpd logs from the undercloud when this happens? Another thought is, I suspect that incorporating a stop on all undercloud services like at https://review.openstack.org/#/c/331804/ before invoking the "openstack undercloud upgrade" might solve this problem. You could try this if you can reproduce on an enviroonment. Otherwise needs logs/more info. It could yet be another root cause, but if the service stop before upgrade works we can land that to unblock us on these two bugs. For clarity, before "openstack undercloud upgrade" stop services (this has been my workflow for all 8..9 upgrades testing for the undercloud): sudo rm -rf /etc/yum.repos.d/* sudo rhos-release 9-director -d sudo rhos-release 9 -d sudo yum clean all && sudo yum clean metadata && sudo yum clean dbcache && sudo yum makecache sudo yum -y update sudo systemctl stop openstack-* sudo systemctl stop neutron-* openstack undercloud upgrade thanks, marios Environment: openstack-tripleo-heat-templates-kilo-2.0.0-18.el7ost.noarch instack-undercloud-4.0.0-8.el7ost.noarch openstack-tripleo-heat-templates-2.0.0-18.el7ost.noarch openstack-tripleo-heat-templates-liberty-2.0.0-18.el7ost.noarch openstack-puppet-modules-8.1.5-1.el7ost.noarch Didn't reproduce the issue. Closing as not a bug based on sasha's last comment. |