Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation inaccurate for installing oVirt on RHEL #2709

Closed
rwmjones opened this issue Feb 2, 2022 · 11 comments · Fixed by #2821
Closed

Documentation inaccurate for installing oVirt on RHEL #2709

rwmjones opened this issue Feb 2, 2022 · 11 comments · Fixed by #2821
Assignees
Labels
documentation integration upstream PR or issue that applies only to upstream
Milestone

Comments

@rwmjones
Copy link

rwmjones commented Feb 2, 2022

Type of problem?

Documentation issue

Description of the problem

https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.html#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM

The documentation starts by saying you must enable javapackages-tools module, but this doesn't work on RHEL 8 out of the box. The first step on RHEL is to enable various subscription-manager repos.

Assuming the machine is registered already with RHN, you will need to run these commands first, before proceeding with the dnf commands:

subscription-manager repos --enable=advanced-virt-for-rhel-8-x86_64-rpms
subscription-manager repos --enable=advanced-virt-crb-for-rhel-8-x86_64-rpms 
subscription-manager repos --enable=codeready-builder-for-rhel-8-x86_64-rpms
@Conan-Kudo
Copy link

I'm not sure if advanced-virt is going to be required with RHEL 8.6? I've seen the rebases normally going into AV landing in CentOS Stream 8 proper...

@rwmjones
Copy link
Author

rwmjones commented Feb 2, 2022

Yes that is true. However codeready-builder-for-rhel-8-x86_64-rpms is still needed.

@Conan-Kudo
Copy link

Yup, that's true.

@sandrobonazzola sandrobonazzola changed the title Documentation inaccurate for installing on RHEL Documentation inaccurate for installing oVirt on RHEL Feb 2, 2022
@apinnick
Copy link
Contributor

@sandrobonazzola @rwmjones
Does this issue apply only to oVirt? Or should we open a Bugzilla for RHV?

@sandrobonazzola
Copy link
Member

It's ovirt only.

@sandrobonazzola sandrobonazzola self-assigned this Feb 22, 2022
@sandrobonazzola sandrobonazzola added this to the ovirt-4.5.0 milestone Feb 22, 2022
@apinnick
Copy link
Contributor

It's ovirt only.

In that case, do you object to my creating a label called 'upstream' so that we know that it only applies to upstream docs? Then we can tag the other upstream issue (P&P) guide as well.

@apinnick apinnick added the upstream PR or issue that applies only to upstream label Feb 22, 2022
@sandrobonazzola
Copy link
Member

ok for me using upstream label

@apinnick
Copy link
Contributor

Great. If we ever need a downstream label to indicate that the issue has to have a BZ created for RHV, I can create one. Should make it easier for us to keep the issues separate and to make sure they are triaged.

@rwmjones
Copy link
Author

I only tried oVirt, don't know if it applies to RHV or not.

@apinnick
Copy link
Contributor

I only tried oVirt, don't know if it applies to RHV or not.

Good point. It's worth looking at the installation guides to see whether this documentation is there as well. I will follow up on it.

@apinnick apinnick self-assigned this Feb 24, 2022
@sandrobonazzola
Copy link
Member

Adding instructions with oVirt 4.5.0 beta in pr #2821

@sandrobonazzola sandrobonazzola linked a pull request Mar 31, 2022 that will close this issue
@sandrobonazzola sandrobonazzola added this to To do in oVirt Integration overview via automation Mar 31, 2022
@sandrobonazzola sandrobonazzola moved this from To do to Review in progress in oVirt Integration overview Mar 31, 2022
oVirt Integration overview automation moved this from Review in progress to Done Apr 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation integration upstream PR or issue that applies only to upstream
Projects
Development

Successfully merging a pull request may close this issue.

4 participants