For making sure we run with a tested set of (mostly) python dependencies we should include all the cinderlib/ceph dependencies we require. Since it's annoying to enable that on every host maually let's try to automate that in host upgrade, we alreayd have code manipulating with virt streams We want to enable: openstack-16.2-cinderlib-for-rhel-8-x86_64-rpms rhceph-4-tools-for-rhel-8-x86_64-rpms assuming that the subscription is already there and the system is attached to a valid SKU that has them available. Since it's also possible to use local mirrors or remap channel names in satellite any error should not be treated as a blocker and we should continue with upgrade.
Can you please detail the changes needed? Right now oVirt ovirt-host package is requiring cinderlib dependenices for all hosts and ovirt-release44 is providing these dependencies. On the other side RHV ovirt-host package is not requiring cinderlib dependencies. Are we going to align oVirt to RHV and have the ovirt-ansible-host-deploy taking care of repos and deps instead? If so, are we moving the requirements on cinderlib from ovirt-host to oVirt Node / RHV-H kickstart?
(In reply to Sandro Bonazzola from comment #2) > Can you please detail the changes needed? > Right now oVirt ovirt-host package is requiring cinderlib dependenices for > all hosts and ovirt-release44 is providing these dependencies. > On the other side RHV ovirt-host package is not requiring cinderlib > dependencies. > > Are we going to align oVirt to RHV and have the ovirt-ansible-host-deploy > taking care of repos and deps instead? > > If so, are we moving the requirements on cinderlib from ovirt-host to oVirt > Node / RHV-H kickstart? This is purely RHV feature, the idea is: 1. During host upgrade we are going to check if some selected ceph/cinderlib package is available 2. If not, we will try to enable channels. And if there will be some error enabling them, we will add an error to audit log, but the upgrade flow is going to continue So there will be value only for RHEL hypervisors, where we are going to automatically enable channels, so customers won't need to enable them manually. Of course if they have some non-standard channel setup (for example satellite with custom channel names), this feature will not help them and they will need to manually setup their channels on each host. So this change is not visible in oVirt, because we should already have both repos in ovirt-release-44. And it will also not be visible in standard QE setup, where they have required repositories enabled
How can we make sure that any special subscriptions are needed? Or this is already handled, since we have the instructions in the appendix?
(In reply to Martin Perina from comment #4) > This is purely RHV feature, the idea is: > > 1. During host upgrade we are going to check if some selected ceph/cinderlib > package is available > 2. If not, we will try to enable channels. And if there will be some error > enabling them, we will add an error to audit log, but the upgrade flow is > going to continue > > So there will be value only for RHEL hypervisors, where we are going to > automatically enable channels, so customers won't need to enable them > manually. Of course if they have some non-standard channel setup (for > example satellite with custom channel names), this feature will not help > them and they will need to manually setup their channels on each host. Given above, I assume that: - ovirt-host upstream needs to keep requiring cinderlib - ovirt-host downstream needs to keep NOT requiring cinderlib - RHV-H requires a change in its kickstart for including cinderlib packages by default. Correct?
(In reply to Sandro Bonazzola from comment #7) > > Given above, I assume that: > - ovirt-host upstream needs to keep requiring cinderlib yes > - ovirt-host downstream needs to keep NOT requiring cinderlib no, it shall also require cinderlib > - RHV-H requires a change in its kickstart for including cinderlib packages > by default. it doesn't need to when ovirt-host requires it
Hi Marina, (In reply to Marina Kalinin from comment #6) > How can we make sure that any special subscriptions are needed? Or this is > already handled, since we have the instructions in the appendix? the repos are already part of the RHV SKUs, so no additional SKUs needed. This is "just" about enabling the repo on the Hypervisors.
Can we please provide good release note here explaining that now cinderlib repos are required to be enabled by default and this RFE will try to add them automatically, but if fails, would be on the user to do so manually. On each host.
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.
Check against 4 RHV SKUs which I have access to ( MCT2927, RV00045, RV00046, RV00033 ) and I had access on all 4 to the 16.2 cinderlib repo # subscription-manager repos | grep -E "openstack-16.2-cinderlib-for-rhel-8-x86_64-rpms|rhceph-4-tools-for-rhel-8-x86_64-rpms" Repo ID: rhceph-4-tools-for-rhel-8-x86_64-rpms Repo ID: openstack-16.2-cinderlib-for-rhel-8-x86_64-rpms
marking as verified with comment above, as current QE setup cannot mirror deployment from CDN
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 (Moderate: RHV Manager (ovirt-engine) security update [ovirt-4.4.9]), 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-2021:4626