Bug 1522819 - ovirt-node was not respined after ovirt-host package introduction to 3.6
Summary: ovirt-node was not respined after ovirt-host package introduction to 3.6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhev-hypervisor-ng
Version: 4.2.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ovirt-3.6.z-async
: ---
Assignee: Ryan Barry
QA Contact: dguo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-06 14:07 UTC by Pavol Brilla
Modified: 2019-05-16 12:54 UTC (History)
22 users (show)

Fixed In Version: rhev-hypervisor7-7.3-20180129.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-19 15:00:09 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0328 0 normal SHIPPED_LIVE redhat-virtualization-host bug fix and enhancement update for RHV 3.6.12 2018-02-19 20:00:32 UTC

Description Pavol Brilla 2017-12-06 14:07:09 UTC
Description of problem:

ovirt-host metapackage for 3.6 was introduce in Sept release, but ovirt-node was not respined with it


Version-Release number of selected component (if applicable):
redhat-virtualization-host-3.6-20170616.1
on
ovirt-engine 4.2.1

How reproducible:
100%

Steps to Reproduce:
1. add 3.6 ovirt-node to 4.2 engine 3.6 cluster
2. host failed to be added, check additional info

Actual results:
Host failed to be added

Expected results:
Host should be added


Additional info:
2017-12-06 12:30:43,184+0100 DEBUG otopi.context context._executeMethod:143 method exception
Traceback (most recent call last):
  File "/tmp/ovirt-zpm3bgg3Ta/pythonlib/otopi/context.py", line 133, in _executeMethod
    method['method']()
  File "/tmp/ovirt-zpm3bgg3Ta/otopi-plugins/ovirt-host-deploy/host/packages.py", line 69, in _validation
    'Cannot locate ovirt-host package, '
RuntimeError: Cannot locate ovirt-host package, possible cause is incorrect channels

Comment 7 Dan Kenigsberg 2017-12-08 09:28:58 UTC
I never liked the idea of backporting ovirt-host. I this that is is much simpler to teach ovirt-host-deploy of 4.2 to handle old hosts properly.

However: who is affected by this bug? Customers that have a big RHVH-3.6 deployment, have upgraded to engine-4.2, and would like to add another RHV-3.6 host. Their clusters are all >= 3.6 (as their engine is 4.2) so there should be no problem to install fresh RHV-H-4.2 hosts.

Pavol, kudos for catching this bug, but I think we should not fix it.

Comment 8 Jiri Belka 2017-12-08 09:58:50 UTC
(In reply to Dan Kenigsberg from comment #7)

> Pavol, kudos for catching this bug, but I think we should not fix it.

It was me who found that :)

Comment 14 dguo 2018-01-17 02:58:55 UTC
Test version:
redhat-virtualization-host-3.6-20180103.0
rhvm-4.2.0.2-0.1.el7
vdsm-4.17.44-2.el7ev.noarch

Test step:
1.Install rhevh-ngn
2.Create a datacenter with Compatibility Version 3.6
3.Add rhevh-ngn to the above dc

Test results:
An error has occurred during installation of Host ngn-bug: Failed to execute stage 'Setup validation': Cannot locate ovirt-host package, possible cause is incorrect channels.

QE set qa-ack based on above result

Comment 15 dguo 2018-01-30 09:53:04 UTC
For the latest vintage build rhev-hypervisor7-20180129.0, the ovirt-host package is already included.
[root@dell-per515-01 ~]# rpm -q ovirt-host
ovirt-host-3.6.0-1.el7ev.noarch
But failed to add vintage rhevh to rhvm4.2, already file another bug 1540101 to trace

For the ngn build redhat-virtualization-host-3.6-20180129.0, the ovirt-host package is included too.
Add 3.6 ngn to rhvm4.2 with compatibility version 3.6 dc successfully.

So, once the bug changed to on_qa, will verify this bug.

Comment 17 cshao 2018-02-13 11:04:11 UTC
Verify this bug according #c15.

Comment 20 errata-xmlrpc 2018-02-19 15:00:09 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-2018:0328

Comment 21 Franta Kust 2019-05-16 12:54:48 UTC
BZ<2>Jira re-sync


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