Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1486669 - OSP11 -> OSP12 upgrade: cannot rerun major-upgrade-composable-steps-docker.yaml after the pacemaker resources have been deleted
OSP11 -> OSP12 upgrade: cannot rerun major-upgrade-composable-steps-docker.ya...
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
urgent Severity urgent
: beta
: 12.0 (Pike)
Assigned To: mathieu bultel
Marius Cornea
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-30 06:38 EDT by Marius Cornea
Modified: 2018-02-05 14:12 EST (History)
9 users (show)

See Also:
Fixed In Version: openstack-tripleo-heat-templates-7.0.1-0.20170927205938.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-13 16:59:22 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1716031 None None None 2017-09-08 14:32 EDT
OpenStack gerrit 501734 None None None 2017-09-08 14:32 EDT
OpenStack gerrit 504420 None None None 2017-10-10 10:19 EDT
Red Hat Product Errata RHEA-2017:3462 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-15 20:43:25 EST

  None (edit)
Description Marius Cornea 2017-08-30 06:38:59 EDT
Description of problem:
OSP11 -> OSP12 upgrade: cannot rerun major-upgrade-composable-steps-docker.yaml after the pacemaker resources have been deleted. The overcloud deploy command fails with:

2017-08-30 10:21:03Z [overcloud]: UPDATE_FAILED  resources.AllNodesDeploySteps: resources.ControllerUpgrade_Step2: Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2

 Stack overcloud UPDATE_FAILED 

overcloud.AllNodesDeploySteps.ControllerUpgrade_Step2.0:
  resource_type: OS::Heat::SoftwareDeployment
  physical_resource_id: 5ab172b9-7096-43f0-8688-3820207267d3
  status: UPDATE_FAILED
  status_reason: |
    Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2
  deploy_stdout: |
    ...
    TASK [set is_bootstrap_node fact] **********************************************
    ok: [localhost]
    
    TASK [Disable the haproxy cluster resource.] ***********************************
    fatal: [localhost]: FAILED! => {"changed": false, "error": "Error: resource/clone/master/group/bundle 'haproxy' does not exist\n", "failed": true, "msg": "Failed, to set the resource haproxy to the statedisable", "output": "", "rc": 1}
        to retry, use: --limit @/var/lib/heat-config/heat-config-ansible/7c63dab0-fd92-4f7f-9097-5aff99a62126_playbook.retry
    
    PLAY RECAP *********************************************************************
    localhost                  : ok=7    changed=4    unreachable=0    failed=1   
    
    (truncated, view all with --long)


Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-7.0.0-0.20170821194253.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Deploy OSP11
2. Run major-upgrade-composable-steps-docker.yaml  step to upgrade to OSP12
3. Fail after the pacemaker resources have been deleted
4. Fix the failure cause
5. Rerun the major-upgrade-composable-steps-docker.yaml step

Actual results:
Upgrade fails with error": "Error: resource/clone/master/group/bundle 'haproxy' does not exist because the haproxy pacemaker resource has been deleted.

Expected results:
major-upgrade-composable-steps-docker.yaml should be idempotent. If the resource has already been stopped/deleted then it should proceed to the next step.  

Additional info:
Comment 6 errata-xmlrpc 2017-12-13 16:59:22 EST
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/RHEA-2017:3462

Note You need to log in before you can comment on or make changes to this bug.