Description of problem:
https://bugzilla.redhat.com/show_bug.cgi?id=1421098 introduced 3.6 NGN for 3.6 but there's an issue in 3.6 version host-deploy which doesn't recognize correctly 3.6 NGN while adding it into 3.6 engine.
thus 3.6 ngn cannot be updated correctly via engine and thus https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html/upgrade_guide/updating_virtualization_hosts cannot be followed strictly.
there should be probably a 'Note' section mentioning that host upgrade manager can't upgrade 3.6 NGN inside 4.0 engine if it was added in time of 3.6 engine (ie. with host-deploy from 3.6 engine). See https://bugzilla.redhat.com/show_bug.cgi?id=1431226 and https://bugzilla.redhat.com/show_bug.cgi?id=1425660
This issue can be repaired only in 4.0 with 'Reinstall' button or via direct modification of the DB right now or a KB...
fyi where is info about adding new repo/channel for upgrade from 3.6 ngn to 4.0 ngn?
Version-Release number of selected component (if applicable):
4.0
How reproducible:
100%
Steps to Reproduce:
1. add 3.6 ngn into 3.6 engine
2. upgrade engine to 4.0
3. follow upgrade guide
Actual results:
no upgrade would appear as 3.6 ngn has wrong vds_type in the DB thus there will be notification for upgrade...
Expected results:
it should be clear for 3.6 ngn users what to do how to get updates 3.6 -> 4.0ngn working
Additional info:
We will cover the upgrade scenario and update workaround in bug 1445157.
I am changing the scope of this bug to cover the installation flow for the new 3.6 RHVH, because the upgrade flow depends on the user installing 3.6 RHVH.
Assigning to Byron for review.