Bug 1691363 - Curator failes in metrics store installation
Summary: Curator failes in metrics store installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-metrics
Classification: oVirt
Component: Generic
Version: 1.2.1.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.3.3
: ---
Assignee: Shirly Radco
QA Contact: Ivana Saranova
URL:
Whiteboard:
Depends On:
Blocks: 1631193
TreeView+ depends on / blocked
 
Reported: 2019-03-21 13:37 UTC by Shirly Radco
Modified: 2019-04-16 13:58 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-metrics-1.2.1.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-16 13:58:33 UTC
oVirt Team: Metrics
Embargoed:
sradco: ovirt-4.3?
lleistne: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 98641 0 master MERGED Fix bug with curator update 2019-03-26 13:35:47 UTC

Description Shirly Radco 2019-03-21 13:37:01 UTC 
Description of problem:
Curator failes in metrics store installation

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

How reproducible:
100%

Steps to Reproduce:
1. Install oVirt metrics store
2. Inspect Curator pod after a few hours since it is created with cron job.
3.

Actual results:
Pod is in error state

Expected results:
Pod should be running

Additional info:
Comment 1 Ivana Saranova 2019-04-04 14:37:18 UTC 
Steps to Reproduce:
1. Install oVirt metrics store according to documentation and README
2. Inspect Curator pod after a few hours

Result:
Pod is in state completed, therefore I believe this is intended correct behavior.

Verified in: 
ovirt-engine-4.2.8.5-0.1.el7ev.noarch
ovirt-engine-metrics-1.2.1.3-1.el7ev.noarch

Also verified in:
ovirt-engine-4.3.3.1-0.1.el7.noarch
ovirt-engine-metrics-1.2.1.3-1.el7ev.noarch
Comment 2 Sandro Bonazzola 2019-04-16 13:58:33 UTC 
This bugzilla is included in oVirt 4.3.3 release, published on April 16th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.