Bug 1677240 - Link in metrics' config.yml.example is broken
Summary: Link in metrics' config.yml.example is broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-metrics
Classification: oVirt
Component: Generic
Version: 1.2.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
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-02-14 10:39 UTC by Jan Zmeskal
Modified: 2019-04-16 13:58 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-04-16 13:58:18 UTC
oVirt Team: Metrics
Embargoed:
sradco: ovirt-4.3?
lleistne: testing_ack+


Attachments (Terms of Use)

Description Jan Zmeskal 2019-02-14 10:39:16 UTC
Description of problem:
There's a link in etc/config.yml.example on line 12 that reads like this:
https://www.ovirt.org/develop/release-management/features/metrics/metrics-store-installation/#ovirt-metrics-store-setup
It's supposed to contain more info on metrics setup, but it returns 404

Comment 1 Jan Zmeskal 2019-02-25 13:35:52 UTC
Moving to POST since the patch this BZ depends on (https://gerrit.ovirt.org/#/c/97643/) has not been merged yet. Once it's merged, this can be moved to MODIFIED. Once it's a part of consumable package, this can be moved to ON_QA and verified by QA.

Comment 2 Sandro Bonazzola 2019-03-12 12:54:23 UTC
4.3.1 has been released, please re-target this bug as soon as possible.

Comment 3 Ivana Saranova 2019-04-02 15:56:00 UTC
Steps:
1) Check that link in /etc/ovirt-engine-metrics/config.yml.example is working

Results:
Link directs to actual ovirt metrics page, no 404 error.

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 4 Sandro Bonazzola 2019-04-16 13:58:18 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.