Bug 1463759
Summary: | OSP8 -> OSP9 upgrade: pacemaker resources are stopped and unmanaged post upgrade | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> | |
Component: | python-networking-bigswitch | Assignee: | mathieu bultel <mbultel> | |
Status: | CLOSED ERRATA | QA Contact: | Amit Ugol <augol> | |
Severity: | urgent | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 9.0 (Mitaka) | CC: | cchen, dbecker, ebarrera, jjoyce, jliberma, jschluet, lhh, mbultel, mburns, morazi, rhel-osp-director-maint, sathlang, skinjo, yprokule, yroblamo | |
Target Milestone: | zstream | Keywords: | Regression, Triaged, ZStream | |
Target Release: | 9.0 (Mitaka) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | python-networking-bigswitch-8.40.7-2.el7ost | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1472738 (view as bug list) | Environment: | ||
Last Closed: | 2017-07-12 13:18: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: | 1472738 |
Description
Marius Cornea
2017-06-21 16:58:48 UTC
Hi, there is the infamous bns table error: Jun 23 13:50:38 controller-0.localdomain "Table 'ovs_neutron.bsn_routerrules' doesn't exist\") [SQL: u'ALTER TABLE bsn_routerrules ADD COLUMN tenant_id VARCHAR(255)']\n", "deploy_status_code": 1} during step2, but somehow it achieves to get to Step4 which fails: /Stage[main]/Keystone/Exec[keystone-manage bootstrap]: Failed to call refresh: Command exceeded timeout\u001b[0m\n\u001b[1;31mError: /Stage[main]/Keystone/Exec[keystone-manage bootstrap]: Command exceeded timeout\nWrapped exception:\nexecution expired\u001b[0m\n", "deploy_status_code": 6 and make the upgrade fails. As we didn't get to Step~6 where the cluster is brought back to managed, we have this overall unmanaged stuff. Moving it to Mathieu as he has deal with this issue before. I created the fix for the 9 branch When is the fix scheduled to land? Reviewer is needed on the fix, I will ping folks this morning. The fix is landed, it should be available in the next Z release. 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/RHBA-2017:1736 |