Bug 1622992 - [OSP13] anible-pacemaker needs to be installed by default in the undercloud
Summary: [OSP13] anible-pacemaker needs to be installed by default in the undercloud
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: All
OS: All
medium
medium
Target Milestone: z3
: 13.0 (Queens)
Assignee: Jiri Stransky
QA Contact: Gurenko Alex
URL:
Whiteboard:
: 1627495 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-28 10:49 UTC by Michele Baldessari
Modified: 2018-11-13 22:29 UTC (History)
5 users (show)

Fixed In Version: openstack-tripleo-heat-templates-8.0.4-29.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-13 22:28:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3587 0 None None None 2018-11-13 22:29:30 UTC

Description Michele Baldessari 2018-08-28 10:49:13 UTC
Description of problem:
while it is true that we do state that an undercloud upgrade should be performed before making a minor update for the overcloud, it makes sense to have ansible-pacemaker pulled in from the start (think installation with all the latest packages, it makes no sense to demand an undercloud upgrade in this context).

This has been fixed upstream via:
https://review.rdoproject.org/r/#/c/15684/ (queens)
https://review.rdoproject.org/r/#/c/15957/ (pike)

If you do not have ansible-pacemaker on the undercloud you will hit these errors during a minor update:
u'TASK [include]
*****************************************************************',
 u'Thursday 09 August 2018  06:55:47 -0400 (0:00:00.388)
 0:00:10.970 ******* ',
  u'fatal: [controller-2]: 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/dd74d929-9322-44ba-817a-e6e2a4792169/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/dd74d929-9322-44ba-817a-e6e2a4792169/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/dd74d929-9322-44ba-817a-e6e2a4792169/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"}',
   u'',

Comment 1 Jiri Stransky 2018-08-28 10:55:28 UTC
Just checked OSP 14 too, there it's good, t-h-t RPM spec has:

Requires:       ansible-pacemaker

Comment 3 Jiri Stransky 2018-09-17 13:53:10 UTC
*** Bug 1627495 has been marked as a duplicate of this bug. ***

Comment 5 Gurenko Alex 2018-10-21 09:51:49 UTC
Verified on puddle 2018-10-02.1

[stack@undercloud-0 ~]$ rpm -q ansible-pacemaker
ansible-pacemaker-1.0.4-0.20180220234310.0e4d7c0.el7ost.noarch

Comment 11 errata-xmlrpc 2018-11-13 22:28:47 UTC
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-2018:3587


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