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

Bug 1743411

Summary: puppet-etcd doesn't include EL8 in its list of supported OS versions
Product: Red Hat OpenStack Reporter: Alan Bishop <abishop>
Component: puppet-etcdAssignee: Alan Bishop <abishop>
Status: CLOSED ERRATA QA Contact: Tzach Shefi <tshefi>
Severity: high Docs Contact:
Priority: high    
Version: 15.0 (Stein)CC: gcharot, jvisser, pgrist
Target Milestone: z2Keywords: Triaged, ZStream
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-etcd-1.12.4-0.20191025050419.123d2af.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-05 11:59:15 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: 1636040, 1794654    

Description Alan Bishop 2019-08-19 20:38:03 UTC
Description of problem:

The DLM required to support running cinder active/active relies on puppet-etcd to configure the etcd3 service. Unfortunately, puppet-etcd appears to whitelist support for specific Red Hat OS versions, and EL8 is not in that list.

As a result, puppet-etcd will fail, like this:

 "2019-08-18 07:12:28,196 WARNING: 36404 -- Retrying running container: etcd",
        "2019-08-18 07:12:40,020 ERROR: 36404 -- ['/usr/bin/podman', 'start', '-a', 'container-puppet-etcd'] run failed after + mkdir -p /etc/puppet",
        "<13>Aug 18 07:12:35 puppet-user:                     with Stdlib::Compat::Hash. There is further documentation for validate_legacy function in the README. at [\"/etc/puppet/modules/tripleo/manifests/profile/base/etcd.pp\", 68]:[\"/etc/config.pp\", 3]",
        "<13>Aug 18 07:12:35 puppet-user: Warning: ModuleLoader: module 'etcd' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\\n   (file & line not available)",
        "<13>Aug 18 07:12:35 puppet-user: Error: Evaluation Error: Error while evaluating a Function Call, Unsupported RedHat release. (file: /etc/puppet/modules/etcd/manifests/params.pp, line: 19, column: 21) on node controller-0.redhat.local",
<snip>

Note the "Unsupported RedHat release."


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

puppet-etcd-1.12.3-0.20190729090440.7555287.el8ost.noarch

How reproducible: always

Steps to Reproduce:
1. Deploy overcloud with "-e environments/cinder-active-active.yaml"
2.
3.

Actual results:

Overcloud deployment fails

Expected results:


Additional info:

Comment 1 Alan Bishop 2019-08-19 20:39:47 UTC
Patch submitted upstream: https://github.com/cristifalcas/puppet-etcd/pull/35

Comment 4 Alan Bishop 2019-08-20 12:51:17 UTC
Targeting for 15z1 based on comment #3.

Comment 5 Alan Bishop 2019-08-21 14:28:09 UTC
Upstream patch was accepted.

Comment 8 Tzach Shefi 2019-12-10 10:19:10 UTC
Dear Errata, 
It could very well be ON_QA
however latest build P1 -> "RHOS_TRUNK-15.0-RHEL-8-20191115.n.0"
Hasn't yet provided a sufficient fixed-in 1.12.4 >  puppet-etcd-1.12.3-0.20190729090440.7555287.el8ost.noarch

Guess I'll wait for a newer puddle before I retry.

Comment 9 Tzach Shefi 2019-12-16 12:12:57 UTC
Verified on:
puppet-etcd-1.12.4-0.20191025050419.123d2af.el8ost


Awesome we finally manage to deploy Cinder A/A :)

(overcloud) [stack@undercloud-0 ~]$ cinder service-list
+------------------+---------------------------+------+---------+-------+----------------------------+-----------------+
| Binary           | Host                      | Zone | Status  | State | Updated_at                 | Disabled Reason |
+------------------+---------------------------+------+---------+-------+----------------------------+-----------------+
| cinder-backup    | controller-0              | nova | enabled | up    | 2019-12-16T12:08:13.000000 | -               |
| cinder-scheduler | controller-0              | nova | enabled | up    | 2019-12-16T12:08:06.000000 | -               |
| cinder-scheduler | controller-1              | nova | enabled | up    | 2019-12-16T12:08:05.000000 | -               |
| cinder-scheduler | controller-2              | nova | enabled | up    | 2019-12-16T12:08:05.000000 | -               |
| cinder-volume    | controller-0@tripleo_ceph | nova | enabled | up    | 2019-12-16T12:08:06.000000 | -               |
| cinder-volume    | controller-1@tripleo_ceph | nova | enabled | up    | 2019-12-16T12:08:07.000000 | -               |
| cinder-volume    | controller-2@tripleo_ceph | nova | enabled | up    | 2019-12-16T12:08:06.000000 | -               |
+------------------+---------------------------+------+---------+-------+----------------------------+-----------------+

Yep 3 c-vols, so any Cinder A/A requirements including so puppet-etcd installed as needed. 

Even created a test cinder vol:
(overcloud) [stack@undercloud-0 ~]$ cinder list
+--------------------------------------+-----------+------+------+-------------+----------+-------------+
| ID                                   | Status    | Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+------+------+-------------+----------+-------------+
| 645899e2-a3bc-42ca-b5a4-e4927002ac2a | available | -    | 1    | tripleo     | false    |             |
+--------------------------------------+-----------+------+------+-------------+----------+-------------+

Comment 10 Alex McLeod 2020-02-19 12:44:01 UTC
If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to '-'.

Comment 11 Alan Bishop 2020-02-19 21:18:56 UTC
No doc required for this.

Comment 13 errata-xmlrpc 2020-03-05 11:59:15 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-2020:0643