Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693610 - [Test Only] Testing 4.3 hosts in 4.2 engine with 4.2 cluster compatibility
Summary: [Test Only] Testing 4.3 hosts in 4.2 engine with 4.2 cluster compatibility
Keywords:
Status: VERIFIED
Alias: None
Product: ovirt-engine-metrics
Classification: oVirt
Component: Generic
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.2.8-4
: ---
Assignee: Shirly Radco
QA Contact: Ivana Saranova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-28 10:06 UTC by Lukas Svaty
Modified: 2019-04-05 16:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Metrics
dfediuck: ovirt-4.2+
lsvaty: testing_ack+


Attachments (Terms of Use)

Description Lukas Svaty 2019-03-28 10:06:02 UTC
Description of problem:
Make sure after 4.3 is released 4.3 host is supported in 4.2 cluster in 4.2 engine with metrics deployed.

Please test 4.3 host in 4.2 cluster and metrics store installation afterwards.
And 4.2 deployed with metrics store and afterwards adding 4.3 host.

Comment 1 Ivana Saranova 2019-04-05 16:34:44 UTC
Steps:
1) Have 4.2 engine with 4.2 compatibility cluster
2) Connect it to metrics-store
3) Add 4.3 host
4) Check that host deploy didn't fail

Result: Host is successfully added


Steps:
1) Have 4.2 engine with 4.2 compatibility cluster not connected to metrics-store
2) Add 4.3 host
3] Connect engine and host to metrics store

Result: Engine and host were successfully connected to the metrics-store and there is data in Kibana

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


Note You need to log in before you can comment on or make changes to this bug.