Bug 1444450
Summary: | 3.6ngn cannot be reinstalled on 4.1 engine | ||
---|---|---|---|
Product: | [oVirt] ovirt-host-deploy | Reporter: | Jiri Belka <jbelka> |
Component: | General | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED DUPLICATE | QA Contact: | Pavel Stehlik <pstehlik> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | master | CC: | bugs, danken, jbelka, oourfali |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-04-25 14:00:28 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jiri Belka
2017-04-21 11:01:58 UTC
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 *** |