Description of problem: When installing the rhv manager dnf wants to install nodejs 10 appstream which went out of support in april of this year. Version-Release number of selected component (if applicable): 4.4.7.7-0.1.el8ev How reproducible: Follow https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/installing_red_hat_virtualization_as_a_standalone_manager_with_local_databases/index#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM additionally enable ansible 2.9 repository (otherwise dnf will error with a dependency issue) addtiontally run $ dnf module -y enable maven otherwise dnf runs into another dependency issue $ dnf install rhvm Updating Subscription Management repositories. Last metadata expiration check: 0:33:06 ago on Wed 28 Jul 2021 07:15:15 AM UTC. Dependencies resolved. ===================================================================================================================================================================================================================================================================== Package Architecture Version Repository Size ===================================================================================================================================================================================================================================================================== Installing: rhvm noarch 4.4.7.7-0.1.el8ev rhv-4.4-manager-for-rhel-8-x86_64-rpms 8.7 k [...] Enabling module streams: httpd 2.4 javapackages-runtime 201801 nodejs 10 perl 5.26 perl-IO-Socket-SSL 2.066 perl-libwww-perl 6.34 python36 3.6 Observe it's trying to install nodejs 10, that appstream went out of support in april 2021 ( source https://access.redhat.com/support/policy/updates/rhel8-app-streams-life-cycle ) Actual results: nodejs 10 is used Expected results: no out of support appstream is used Additional info: Support Case: 02998085 that includes a sos report
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.
seems it's novnc pulling it in
oVirt 4.5 / RHV 4.4SP1 is using nodejs16
standalone engine still wants nodejs:10 ovirt-engine-4.5.0.5-0.7.el8ev Enabling module streams: httpd 2.4 javapackages-runtime 201801 maven 3.5 nodejs 10
no it doesn't
I'd guess you need to manually enable the right nodejs stream, 10 is just the default that dnf goes to. If it is a wise choise for dnf to select an out of support stream as default is a different question :D
Also notice that maven 3.5 went out of support yesterday (or well maybe end of the month, lifecycle page just says May 2022) whats the procedure for upgrading node Michal? Just change the module and run an update? engine-setup does not seem to do that on it's own (at least in my ovirt 4.5)
this need to be reflected in docs
we do not require nodejs or maven at all, it's required by novnc that actually doesn't need that anyway, but since that's coming from RHOS we can't do much about that without rebuilding. Similarly for maven module it's probably coming from EAP, bt not really used anywhere. There's no concrete version required, so you can easily just switch the stream versions and upgrade yourself. It should be good enough to mention this in docs for installations - "enable latest nodejs and maven module streams" somewhere in in https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/installing_red_hat_virtualization_as_a_standalone_manager_with_local_databases/index#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM moving to docs
We have similar bug related to nodejs being enabled in appliance. Let's be consistent here.
(In reply to Michal Skrivanek from comment #13) > we do not require nodejs or maven at all, it's required by novnc that > actually doesn't need that anyway, but since that's coming from RHOS we > can't do much about that without rebuilding. Similarly for maven module it's > probably coming from EAP, bt not really used anywhere. > There's no concrete version required, so you can easily just switch the > stream versions and upgrade yourself. so should this bug be changed to novnc so that it no longer requires node/maven?
tracking and handling documentation for the nodejs issue with this bug: https://bugzilla.redhat.com/show_bug.cgi?id=2080505
Hi Klaas, do you think we can close this as a duplicate, and work from BZ#2080505?
(In reply to Eli Marcus from comment #17) > Hi Klaas, > do you think we can close this as a duplicate, and work from BZ#2080505? I think this bug should be changed into an RFE for the novnc packages. If node/maven are not needed they should not be pulled in by novnc and then it won't be pulled by ovirt-engine/rhvm.
Please give me the exact commands that I need to add to the document for the user to activate the nodejs:14 and maven modules
new PR for the update - this doc section is shared by the Installation Guides and the Upgrade Guide so the instructions will show up in both guides: https://github.com/oVirt/ovirt-site/pull/2922
merged PR with only the nodejs instructions visible at this time
I can verify, looks like this is done, the maven module dependency should maybe get it's own BZ.
I just upgraded a RHV Manager to 4.4SP1 from 4.4, the upgrade docs do not mention the nodejs module switch. What you have to do: "yum distro-sync; yum module reset nodejs; dnf module -y enable nodejs:14; yum distro-sync" manually after running the yum update --nobest I'd say
(In reply to Klaas Demter from comment #26) > I just upgraded a RHV Manager to 4.4SP1 from 4.4, the upgrade docs do not > mention the nodejs module switch. What you have to do: > > "yum distro-sync; yum module reset nodejs; dnf module -y enable nodejs:14; > yum distro-sync" manually after running the yum update --nobest I'd say Hi Klaas, today we release the batch 1 update to the RHV 4.4 SP1, the documentation contains the instructions for updating nodejs in the Administration guide and the Installation guides under the section "Enabling the Red Hat Virtualization Manager Repositories" which is also referenced by a link in the Upgrade Guide to the Installation chapter for Enabling the Red Hat Virtualization Manager Repositories. does this cover what is needed?
example of the reference - https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/installing_red_hat_virtualization_as_a_standalone_manager_with_local_databases/index#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM
(In reply to Eli Marcus from comment #27) > (In reply to Klaas Demter from comment #26) > > I just upgraded a RHV Manager to 4.4SP1 from 4.4, the upgrade docs do not > > mention the nodejs module switch. What you have to do: > > > > "yum distro-sync; yum module reset nodejs; dnf module -y enable nodejs:14; > > yum distro-sync" manually after running the yum update --nobest I'd say > > Hi Klaas, today we release the batch 1 update to the RHV 4.4 SP1, > the documentation contains the instructions for updating nodejs in the > Administration guide and the Installation guides under the section > "Enabling the Red Hat Virtualization Manager Repositories" > which is also referenced by a link in the Upgrade Guide to the Installation > chapter for Enabling the Red Hat Virtualization Manager Repositories. > > does this cover what is needed? I think so, yes