Bug 1476711
| Summary: | OSP9 -> OSP10 upgrade: major-upgrade-pacemaker.yaml fails with Error: Unable to find constraint - 'INFINITY' | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> | ||||
| Component: | openstack-tripleo-heat-templates | Assignee: | Sofer Athlan-Guyot <sathlang> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Amit Ugol <augol> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 10.0 (Newton) | CC: | arkady_kanevsky, dbecker, ealcaniz, erik.young, gabrioux, jjoyce, mburns, mflusche, morazi, rhel-osp-director-maint, sathlang, sclewis, smerrow | ||||
| Target Milestone: | z4 | Keywords: | Regression, Triaged, ZStream | ||||
| Target Release: | 10.0 (Newton) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | openstack-tripleo-heat-templates-5.3.0-3.el7ost | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-09-06 17:11:37 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: | 1335596, 1356451 | ||||||
| Attachments: |
|
||||||
While we wait for the upstream/downstream process, user can use this snippet:
curl https://review.openstack.org/changes/490422/revisions/current/patch?download | \
base64 -d | \
sudo patch -f -d /usr/share/openstack-tripleo-heat-templates -p1
It must be applied after undercloud upgrade and before any overcloud step.
I tested this patch since I was hitting that issue. It works fine, it has fixed the bug. so this would work. We solved it by replacing the two effected lines with:
COL_CONSTRAINTS=$(pcs constraint colocation show --full | awk -F: 'NR>1{gsub(/\)/, "") ; print $NF}')
ORD_CONSTRAINTS=$(pcs constraint order show --full | awk -F: 'NR>1{gsub(/\)/, "") ; print $NF}')
which are both more "correct" in this context, more concise, and work fine as far back as Juno.
-esy
Created attachment 1315627 [details]
bugfix patch
corrects the use of pcs config show to use pcs constraint instead with --full option.
*** Bug 1483121 has been marked as a duplicate of this bug. *** Is this landing onto Aug 30 z-stream? 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:2654 |
Description of problem: OSP9 -> OSP10 upgrade: major-upgrade-pacemaker.yaml fails with Error: Unable to find constraint - 'INFINITY' Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-5.2.0-25.el7ost.noarch How reproducible: Steps to Reproduce: 1. Deploy OSP9 2. Upgrade to OSP10 Actual results: During major-upgrade-pacemaker.yaml step upgrade fails. Expected results: Upgrade completes fine. Additional info: [stack@undercloud-0 ~]$ openstack stack failures list overcloud overcloud.UpdateWorkflow.ControllerPacemakerUpgradeDeployment_Step1.0: resource_type: OS::Heat::SoftwareDeployment physical_resource_id: d60db86f-995f-47aa-b344-4488cc2e47a3 status: CREATE_FAILED status_reason: | Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 1 deploy_stdout: | mysql upgrade required: 0 Mon Jul 31 09:16:10 UTC 2017 a568a3b9-0e83-4702-bf69-33e68de0392d tripleo-upgrade controller-0 Deleting colocation constraint INFINITY from CIB deploy_stderr: | Error: Unable to find constraint - 'INFINITY'