Bug 1580331 - [RFE] puppet-qdr plugin
Summary: [RFE] puppet-qdr plugin
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-qdr
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M3
: 14.0 (Rocky)
Assignee: Martin Magr
QA Contact: Leonid Natapov
URL:
Whiteboard:
: 1640502 (view as bug list)
Depends On:
Blocks: 1566081 1566094 1580338 1639759 1691501 1691506
TreeView+ depends on / blocked
 
Reported: 2018-05-21 09:47 UTC by Martin Magr
Modified: 2019-03-21 18:45 UTC (History)
12 users (show)

Fixed In Version: puppet-qdr-2.3.1-1.el7ost puppet-tripleo-9.3.1-0.20181010034748.157eaab.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1691506 (view as bug list)
Environment:
Last Closed: 2019-01-11 11:49:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
RDO 17343 0 None None None 2018-11-13 16:35:10 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:50:16 UTC

Comment 4 Thierry Vignaud 2018-10-23 13:19:57 UTC 
*** Bug 1640502 has been marked as a duplicate of this bug. ***
Comment 11 Leonid Natapov 2018-11-12 16:20:27 UTC 
Although I can see puppet-qdr RPM in the OSP14 puddle directory it's not installed by the director. Should it be on undercloud and then installed on overcloud while overclpud deployment ? Or should it be included in overcloud image ?

Bottom line metrics-qdr container not conigured automatically and overcloud deployment fails because of missing puppet-qdr package.


WorkAround - After overcloud deployment failed ,I manually installed puppet-qdr rpm on overcloud nodes and re-run the overcloud deployment. After this I metrics-qdr container was created and running.
Comment 14 Jon Schlueter 2018-11-13 11:26:59 UTC 
Make sure this is also happening in RDO.
Comment 17 errata-xmlrpc 2019-01-11 11:49:59 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/RHEA-2019:0045
Note You need to log in before you can comment on or make changes to this bug.