Bug 1691363

Summary: Curator failes in metrics store installation
Product: [oVirt] ovirt-engine-metrics Reporter: Shirly Radco <sradco>
Component: GenericAssignee: Shirly Radco <sradco>
Status: CLOSED CURRENTRELEASE QA Contact: Ivana Saranova <isaranov>
Severity: high Docs Contact:
Priority: high    
Version: 1.2.1.1CC: bugs, lleistne
Target Milestone: ovirt-4.3.3Flags: sradco: ovirt-4.3?
lleistne: testing_ack+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-metrics-1.2.1.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-16 13:58:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Metrics RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1631193    

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.