Fencing configuration generator fails deployment if action parameter is used
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Chris Jones |
Bug Description
If the "action" parameter is used for "openstack overcloud generate fencing" with recent versions of Pacemaker, the following error occurs during deployment:
overcloud.
resource_type: OS::Heat:
physical_
status: CREATE_FAILED
status_reason: |
Error: resources[2]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2
deploy_stdout: |
...
" with Stdlib:
"Error: pcs -f /var/lib/
"Error: /Stage[
]
}
tl;dr it was a mistake (of mine) to ever add this parameter (it doesn't do what I thought it did, and it makes the cluster unstable), and it should be immediately deprecated and no-op'ed.
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in tripleo: | |
milestone: | none → rocky-1 |
Changed in tripleo: | |
assignee: | Chris Jones (cmsj) → Alex Schultz (alex-schultz) |
Changed in tripleo: | |
assignee: | Alex Schultz (alex-schultz) → Chris Jones (cmsj) |
Fix proposed to branch: master /review. openstack. org/550028
Review: https:/