Hide Forgot
Created attachment 1192558 [details] host deploy log Description of problem: The engine tries to install NGN packages on RHEL host the host was NGN and was provisioned to RHEL while it stayed connected to the engine (host remove was not done) Version-Release number of selected component (if applicable): How reproducible: 50% Steps to Reproduce: 1. Have NGN host connected to an engine 2. reprovision host to RHEL 3. upgrade icon appears 4. press upgrade Actual results: the engine tries to install NGN packages: redhat-virtualization-host-image-update.noarch imgbased.noarch the host moves to status 'install failed' can be activated again and the upgrade icon will stay there Expected results: the engine should know the host is RHEL now Additional info: looking at vds_dynamic table the engine knows its a RHEL host (and in the UI as well)
Created attachment 1192559 [details] engine log it happened at around 11am on the 19th
If the host was installed as NGN in webadmin, it will stay NGN, even though you have tried to install normal RHEL packages on it. The type of the host is determined during host deploy and you can check it: 1. In db running checking column vds_type in vds_static table: 0 - RHEL 1 - NGN 2 - Vintage Node 2. In RESTAPI this is reported in host details within HostType You were looking into vds_dynamic table where we have two columns: host_os - this is name-version-release reported by VDSM, but here you will always see RHEL even when it's NGN (we want to report underlying RHEL version here) pretty_name - here full description of host OS, there should be NGN and its correct version I'm not aware of any way host to change OS type from NGN to RHEL other than removing the host and re-adding it again.
im not installing rhel packages on the host, im doing reprovision to rhel & reinstall in the manager, i would expect reinstall to update this info, just as the UI is updated (the software tab) reinstall definitely allows to install a host with different os, so i can imagine 2 options: 1. reinstall will update this info as it updates the software info 2. reinstall shouldnt allow reinstall of different OS what do you think?
Allowing host type change during reinstallation may cause side effects, so we will add checks to host deploy process which will fail reinstallation of a host if host type change is detected (for example switching from NGN to RHEL or from Fedora to Centos). If someone wants to change host type, the only correct way how to do that is remove the host from engine, reinstall and add it to engine again.
There are several paths that need to be fixed if we intent to support detecting vds type change. The user can put the host in maintenance, reprovision the host and then activate/upgrade/reinstall the host. Fixing all the paths needs changes to code in engine as well as in otopi. In my opinion we should not allow the user to reprovision the host, only way to change the host type should be to remove the host, reinstall and add it to engine again.
Because it's quite a corner case and the amount of code needed to fail correctly on all possible reprovisioning scenarios would be very high, we will not fix this in our codebase. But we need to mention in our documentation that reprovisioning the host while it's in Maintenance with different OS is not supported (more info in Doc Text). Moving bug to Doc Team
Updating product and assignee information to allow proper tracking.
Customer will either use RHV-H or RHEL and not mix and match as we do in testing. Therefore this is so unlikely to happen and I'm closing this request.