Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1627495

Summary: minor update on OSP13 failing on controllers
Product: Red Hat OpenStack Reporter: Dave Cain <dcain>
Component: rhosp-directorAssignee: Jiri Stransky <jstransk>
Status: CLOSED DUPLICATE QA Contact: Gurenko Alex <agurenko>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: abays, dbecker, jfrancoa, mburns, morazi
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-17 13:53:10 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 Dave Cain 2018-09-10 17:21:45 UTC
Description of problem:
Preforming a minor update on OSP13 (deployed a day ago) using the 'openstack overcloud update run --nodes Controller" command fails immediately with the following error message:

u'fatal: [vco2-controller1]: FAILED! => {"failed": true, "reason": "no action detected in task. This often indicates a misspelled module name, or incorrect module path.\\n\\nThe error appears to have been in \'/var/lib/mistral/b119ae98-e50b-41e8-bd6f-39b97862188f/Controller/update_tasks.yaml\': line 83, column 5, but may\\nbe elsewhere in the file depending on the exact syntax problem.\\n\\nThe offending line appears to be:\\n\\n    register: haproxy_cert_mounted\\n  - name: Disable the haproxy cluster resource\\n    ^ here\\n\\n\\nThe error appears to have been in \'/var/lib/mistral/b119ae98-e50b-41e8-bd6f-39b97862188f/Controller/update_tasks.yaml\': line 83, column 5, but may\\nbe elsewhere in the file depending on the exact syntax problem.\\n\\nThe offending line appears to be:\\n\\n    register: haproxy_cert_mounted\\n  - name: Disable the haproxy cluster resource\\n    ^ here\\n\\nexception type: <class \'ansible.errors.AnsibleParserError\'>\\nexception: no action detected in task. This often indicates a misspelled module name, or incorrect module path.\\n\\nThe error appears to have been in \'/var/lib/mistral/b119ae98-e50b-41e8-bd6f-39b97862188f/Controller/update_tasks.yaml\': line 83, column 5, but may\\nbe elsewhere in the file depending on the exact syntax problem.\\n\\nThe offending line appears to be:\\n\\n    register: haproxy_cert_mounted\\n  - name: Disable the haproxy cluster resource\\n    ^ here\\n"}'

This seems to work with Compute nodes.  sosreport from the controller system available if you'd like.


Version-Release number of selected component (if applicable):
13.0


How reproducible:
Everytime


Steps to Reproduce:
1. openstack overcloud update run -nodes Controller

Actual results:
See error message above.

Expected results:
Minor updates work on Controller systems.

Comment 1 Andrew Bays 2018-09-12 17:09:20 UTC
I am able to reproduce this in one of my OSP-13 environments.  Templates can be found here: https://github.com/atyronesmith/ha-director-install/tree/ir-osp13-hci-odl

Comment 2 Andrew Bays 2018-09-12 18:02:04 UTC
This looks like it is caused by a missing "ansible-pacemaker" package, as the error itself seems to be complaining about "pacemaker_resource" being an unknown module.  I installed "ansible-pacemaker" and then re-ran the command successfully.

Comment 3 Jiri Stransky 2018-09-17 13:53:10 UTC
Did you maybe skip the `openstack undercloud upgrade` part of minor update? The ansible-pacemaker package should be installed by that command i think.

This issue shouldn't appear when the minor update workflow is performed in full as documented. Still, it's worth solving it better than it is currently. Instead of relying on the `undercloud upgrade` command, we should have it pulled in as a dependency of openstack-tripleo-heat-templates RPM.

We have this already reported as bug 1622992, so i'll close this one as duplicate.

If you did in fact run `openstack undercloud upgrade` and still hit this issue, please reopen the BZ.

*** This bug has been marked as a duplicate of bug 1622992 ***

Comment 4 Andrew Bays 2018-09-17 14:11:17 UTC
Not sure if this matters, but I had just installed the latest OSP-13 version of the undercloud from scratch.  Then I deployed my overcloud and attempted the "openstack overcloud update run --nodes Controller" command immediately after the overcloud finished deploying.  Shouldn't I have already had the ansible-pacemaker package at that point since I had just installed a new undercloud?  Maybe this use case is invalid, but it seems like maybe ansible-pacemaker should have already been there.

Comment 5 Jiri Stransky 2018-09-27 09:48:48 UTC
Before running the `overcloud update run`, we're always supposed to run `undercloud upgrade` to ensure we have the latest tripleo-heat-templates at least, and that command would also install ansible-pacemaker.

But you're absolutely right that we should have ansible-pacemaker installed on undercloud even after installing it from scratch. Bug 1622992 is in MODIFIED now so this should be fixed soon.