Bug 1392613
Summary: | OSP8 Upgrade to OSP9 failed during the keystone upgrade step. | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Jeremy <jmelvin> |
Component: | openstack-tripleo-heat-templates | Assignee: | Sofer Athlan-Guyot <sathlang> |
Status: | CLOSED DUPLICATE | QA Contact: | Amit Ugol <augol> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9.0 (Mitaka) | CC: | augol, bschmaus, cpaquin, jcoufal, jstransk, mburns, mfuruta, michele, morazi, rhel-osp-director-maint, sathlang |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
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: | 2017-03-08 11:20:19 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
Jeremy
2016-11-07 21:47:51 UTC
seems similar to https://bugzilla.redhat.com/show_bug.cgi?id=1354046 , however they are already on the fixed version: Indeed this looks like bug 1354046 (CCing Michele). We are already checking that Keystone disappears from pacemaker before re-managing httpd: https://github.com/openstack/tripleo-heat-templates/blob/stable/mitaka/extraconfig/tasks/major_upgrade_pacemaker_migrations.sh#L67-L87 so it's not immediately obvious how the problem could have happened. Perhaps more logs could be useful in order to see the exact time progression of events. Ideally relevant apache logs showing the failure, /var/log/cluster/..., and the portion of the os-collect-config log (the upgrade.log mentioned earlier). Also just to double check re workaround -- you managed to work around the issue by removing the openstack-keystone-clone resource manually, and running the major-upgrade-keystone-liberty-mitaka.yaml step again, right? Jiri, yes that's the workaround , or stopping keystone in pcs. I will collect those logs and update. Thanks! Moving to upgrades group, workaround available, not blocking any important cases. We will investigate proper fix asap. Hi, I think I found the issue. I could reproduce the exact same error message: Error: /Stage[main]/Keystone/Exec[keystone-manage bootstrap]: Failed to call refresh: keystone-manage bootstrap --bootstrap-password 39EnVE8U7QaxGXYzpKhH47kXh returned 2 instead of one of [0] Error: /Stage[main]/Keystone/Exec[keystone-manage bootstrap]: keystone-manage bootstrap --bootstrap-password 39EnVE8U7QaxGXYzpKhH47kXh returned 2 instead of one of [0] by upgrading the puppet-module to osp9-director before running the keystone migration. The fix is to completely ignore in the documentation: https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/paged/upgrading-red-hat-openstack-platform/chapter-3-director-based-environments-performing-upgrades-to-major-versions in this section: 3.4.3. Upgrading Keystone this command: "Before running the upgrade, update the openstack-puppet-modules package on each node with the following command on the Undercloud: " for i in $(nova list|grep ctlplane|awk -F' ' '{ print $12 }'|awk -F'=' '{ print $2 }'); do ssh -o StrictHostKeyChecking=no heat-admin@$i "sudo yum -y update openstack-puppet-modules" ; done This is a documentation issue and has been raised: - here: https://bugzilla.redhat.com/show_bug.cgi?id=1414917 - there: https://bugzilla.redhat.com/show_bug.cgi?id=1414784 Could you confirm that if you don't upgrade the openstack-puppet-modules before doing the migration then the issue disapear and you don't have to run the workaround any more ? Regards, Can you confirm with the documentation mentioned above in place that we should close this BZ out? This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release. Yes it's only a documentation bug and it has been fixed there https://bugzilla.redhat.com/show_bug.cgi?id=1414784#c5 Closing it as it's fixed in the documentation. *** This bug has been marked as a duplicate of bug 1414784 *** |