Bug 1829656
| Summary: | Failed to register 4.3 host to 4.4 engine with 4.3 cluster (4.4.0-0.33.master.el8ev) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | cshao <cshao> | ||||||
| Component: | ovirt-engine | Assignee: | Dana <delfassy> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | cshao <cshao> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | 4.4.0 | CC: | cshao, delfassy, dougsland, lsurette, lsvaty, mavital, michal.skrivanek, mperina, mtessun, nlevy, peyu, qiyuan, rdlugyhe, sbonazzo, shlei, srevivo, weiwang, yaniwang, yturgema | ||||||
| Target Milestone: | ovirt-4.4.1 | Flags: | delfassy:
needinfo-
|
||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | ovirt-engine-4.4.0.3 | Doc Type: | Known Issue | ||||||
| Doc Text: |
Known issue: Unsubscribed RHVH hosts do not get package updates when you perform a 'Check for upgrade' operation. Instead, you get a 'no updates found' message. This happens because RHVH hosts that are not registered to Red Hat Subscription Management (RHSM) do not have repos enabled. Workaround: To get updates, register the RHVH host with Red Hat Subscription Management (RHSM).
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-08-04 13:22:48 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
cshao
2020-04-30 02:08:21 UTC
Created attachment 1683158 [details]
RHVH log
Created attachment 1683159 [details]
engine.log
Chen, looking at host deploy logs looks like the host wasn't registered, no repositories available. Can you confirm? (In reply to Sandro Bonazzola from comment #3) > Chen, looking at host deploy logs looks like the host wasn't registered, no > repositories available. > Can you confirm? Sandro, You are right, after RHVH registered, host can up. Is this necessary steps for register 4.3 host to 4.4 engine? If so, I'd like close this bug as NOT A BUG. (In reply to cshao from comment #4) > (In reply to Sandro Bonazzola from comment #3) > > Chen, looking at host deploy logs looks like the host wasn't registered, no > > repositories available. > > Can you confirm? > > Sandro, > > You are right, after RHVH registered, host can up. Is this necessary steps > for register 4.3 host to 4.4 engine? > If so, I'd like close this bug as NOT A BUG. We used to have an offline deploy mode provided by ovirt-host-deploy, I don't know enough well the ansible implementation of the deploy flow. Dana, is the subscription now a must have? If so, can you open a doc bug to cover it? (In reply to Sandro Bonazzola from comment #5) > (In reply to cshao from comment #4) > > (In reply to Sandro Bonazzola from comment #3) > > > Chen, looking at host deploy logs looks like the host wasn't registered, no > > > repositories available. > > > Can you confirm? > > > > Sandro, > > > > You are right, after RHVH registered, host can up. Is this necessary steps > > for register 4.3 host to 4.4 engine? > > If so, I'd like close this bug as NOT A BUG. > > We used to have an offline deploy mode provided by ovirt-host-deploy, I > don't know enough well the ansible implementation of the deploy flow. > Dana, is the subscription now a must have? If so, can you open a doc bug to > cover it? I'm not aware of any offline deploy mode in classic host deploy. I remember that RHVH could be registered into engine using some UI/command line on RHVH itself, but administrators still need to perform Install/Reinstall on those nodes to become operational. The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again. so what is it that breaks it, actually? For some unknown reason we are supporting RHVH installation without any subscription attached. We have updated host deploy to support that (no checks about updates), but check-for-upgrade will just be broken for those RHVHs and will always show errors during check for upgrade. With the current implementation of check for updates the task doesn't result with an error, but with 'no updates found' message regardless of existing updates $ git tag --contains d3b6b07d4c00b7bcbfbab27ad842a5346c600a75 ovirt-engine-4.4.0.3 ovirt-engine-4.4.1 ovirt-engine-4.4.1.1 ovirt-engine-4.4.1.2 Test version: redhat-virtualization-host-4.3.11-20200611.0.el7_9 engine: 4.4.1.1-0.5.el8ev Register 4.3 host to 4.4 engine with 4.3 cluster can succeed, so the bug is fixed. Change bug status to VERIFIED. I just fixed a typo in the description Regarding the doc type - it is sort of a combination - the bug of not being able to register the host was fixed by not attempting to download updated packages, and then there's the known issue which is described well, so I suppose it could be either 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 (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), 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/RHSA-2020:3247 |