Description of problem: 3.6ngn which was added in time of 3.6 engine, this engine got updated to 4.0 and 4.1 later on, cannot be successfully "Reinstall"-ed - ie. to make DB change vds_type to '1' - because of 'collectd issue' (https://bugzilla.redhat.com/show_bug.cgi?id=1433434) this BZ is opened for consideration if we could not update vds_type invisibly as we already know by other ways that 3.6 ngn is rhvh - see 'pretty_name' in the vds table below. this will impact scenario considered by ykaul@ at https://bugzilla.redhat.com/show_bug.cgi?id=1431226#c40 2017-04-21 12:47:52 ERROR otopi.plugins.otopi.packagers.yumpackager yumpackager.error:85 Yum Cannot queue package collectd: Package collectd cannot be found 2017-04-21 12:47:52 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/tmp/ovirt-iOzUcZ31yl/pythonlib/otopi/context.py", line 132, in _executeMethod method['method']() File "/tmp/ovirt-iOzUcZ31yl/otopi-plugins/ovirt-host-deploy/collectd/packages.py", line 53, in _packages 'collectd-write_http', File "/tmp/ovirt-iOzUcZ31yl/otopi-plugins/otopi/packagers/yumpackager.py", line 307, in installUpdate ignoreErrors=ignoreErrors File "/tmp/ovirt-iOzUcZ31yl/pythonlib/otopi/miniyum.py", line 883, in installUpdate **kwargs File "/tmp/ovirt-iOzUcZ31yl/pythonlib/otopi/miniyum.py", line 500, in _queue package=package, RuntimeError: Package collectd cannot be found engine=# select vds_name,pretty_name,rpm_version,vds_type from vds; vds_name | pretty_name | rpm_version | vds_type ----------------+-----------------------------------------+----------------------+---------- dell-r210ii-13 | Red Hat Virtualization Host 3.6 (el7.3) | vdsm-4.17.39-1.el7ev | 0 (1 row) engine=# Version-Release number of selected component (if applicable): ovirt-host-deploy-1.6.3-1.el7ev.noarch ovirt-engine-4.1.1.8-0.1.el7.noarch How reproducible: 100% Steps to Reproduce: 1. install 3.6ngn in 3.6 engine 2. update only engine to 4.0 and then to 4.1 3. put 3.6 ngn into maintenance and click reinstall Actual results: reinstall failure Expected results: not sure what we expect here... Additional info: just be aware that 4.1 ngn is shipped to 'rhel-7-server-rhvh-4-rpms', thus if a customer upgrades engine to 4.1 then the host would not be usable; it does work fine in 4.0 engine as this engine version doesn't require as mandatory collectd etc... various details and comments can be found in https://bugzilla.redhat.com/show_bug.cgi?id=1433434
3.6 ngn was rhvh-3.6-0.20170413.0+1
(In reply to Jiri Belka from comment #0) > Description of problem: > > 3.6ngn which was added in time of 3.6 engine, this engine got updated to 4.0 > and 4.1 later on, cannot be successfully "Reinstall"-ed - ie. to make DB > change vds_type to '1' - because of 'collectd issue' > (https://bugzilla.redhat.com/show_bug.cgi?id=1433434) > > this BZ is opened for consideration if we could not update vds_type > invisibly as we already know by other ways that 3.6 ngn is rhvh - see > 'pretty_name' in the vds table below. I have no idea, but if that's what you want, it's not a bug in host-deploy - host-deploy does not update the db. Please describe exactly what you want.
I guess that's the same issue as Bug 1433434.
A RFE to correct DB transparently during upgrade if vds_type is wrong for 'Red Hat Virtualization Host X.Y (elX.Y)' in pretty_name column, suggested by danken@ https://bugzilla.redhat.com/show_bug.cgi?id=1445297
Seems like we decided to fix the collectd issue, see bug 1443508. Can we close current?
*** This bug has been marked as a duplicate of bug 1443508 ***