Page 1 of 1

version conflict urllib3 after upgrade to 2024R1.1.3

Posted: Thu May 30, 2024 6:20 am
by CBoekhuis
After latest update we ran into yum/dnf issues reguarding the version of the urllib3 installed though pip3 from the upgrade page/script.
We run Nagiosxi on a subscribed rhel8 system which means ( as far i understand ) the OS should be in the lead of the installed packages.
This way package compatibility is garanteed and supported by redhat.
Removing and reinstalling the urllib3 through pip3 will install 1.24.2 instead of the one provided by the nagiosxi installer (1.26.18) and fixed the yum/dnf warnings. However this means that the update we are getting are not tested against a real rhel8 (in this case ) version.

How can we fix this before running this update on production server?

Regards,
Christian

Re: version conflict urllib3 after upgrade to 2024R1.1.3

Posted: Thu May 30, 2024 11:49 am
by ajcoil
Hello @CBoekhuis,

Thank you for reaching out!

I am sorry to hear that you are having issues with the XI 2024R1.1.3 upgrade, what version of XI are you upgrading from?

Re: version conflict urllib3 after upgrade to 2024R1.1.3

Posted: Thu May 30, 2024 12:07 pm
by oliviergautreau
This worked for me:

## SOLUTION https://access.redhat.com/solutions/6971428
#Remove the requests and urllib3 installed from pip:
pip uninstall requests urllib3
#Reinstall the python libraries on the system using:
yum reinstall python-urllib3 python-requests

#Verify package in the system with rpm -Va, there will be some issue like below:
rpm -Va
Unsatisfied dependencies for python-requests-2.6.0-10.el7.noarch:
python-urllib3 >= 1.10.2-1 is needed by (installed) python-requests-2.6.0-10.el7.noarch

Re: version conflict urllib3 after upgrade to 2024R1.1.3

Posted: Thu May 30, 2024 12:12 pm
by CBoekhuis
ajcoil wrote: Thu May 30, 2024 11:49 am Hello @CBoekhuis,

Thank you for reaching out!

I am sorry to hear that you are having issues with the XI 2024R1.1.3 upgrade, what version of XI are you upgrading from?
from 2024R1.1.2

Re: version conflict urllib3 after upgrade to 2024R1.1.3

Posted: Wed Jun 26, 2024 8:42 pm
by lorde123
oliviergautreau wrote: Thu May 30, 2024 12:07 pm This worked for me: Emoji Kitchen

## SOLUTION https://access.redhat.com/solutions/6971428
#Remove the requests and urllib3 installed from pip:
pip uninstall requests urllib3
#Reinstall the python libraries on the system using:
yum reinstall python-urllib3 python-requests

#Verify package in the system with rpm -Va, there will be some issue like below:
rpm -Va
Unsatisfied dependencies for python-requests-2.6.0-10.el7.noarch:
python-urllib3 >= 1.10.2-1 is needed by (installed) python-requests-2.6.0-10.el7.noarch
i tried it and it worked. Thank you

Re: version conflict urllib3 after upgrade to 2024R1.1.3

Posted: Thu Jun 27, 2024 9:13 am
by sgardil
oliviergautreau wrote: Thu May 30, 2024 12:07 pm This worked for me:

## SOLUTION https://access.redhat.com/solutions/6971428
#Remove the requests and urllib3 installed from pip:
pip uninstall requests urllib3
#Reinstall the python libraries on the system using:
yum reinstall python-urllib3 python-requests

#Verify package in the system with rpm -Va, there will be some issue like below:
rpm -Va
Unsatisfied dependencies for python-requests-2.6.0-10.el7.noarch:
python-urllib3 >= 1.10.2-1 is needed by (installed) python-requests-2.6.0-10.el7.noarch
Thanks for sharing the solution you found for this issue. It's always nice to see members of the community helping each other out. Do you recall if you ran any additional installations or commands that would have caused the strange difference? I'll attempt an upgrade on rhel8 from R1.1.2 to R1.1.3 and see if I can get the same issue to see since if it is happening for most users then this is something that should be addressed.

Re: version conflict urllib3 after upgrade to 2024R1.1.3

Posted: Fri Jun 28, 2024 9:23 am
by sgardil
I was unable to replicate the issue on a fresh install of 2024R1.1.2 on a minimal rhel 8.9 and upgrading to 2024R1.1.3. I ran a few wizards togather information and let it sit a little bit before upgrading. For anyone that was having this issue do you recall if there was any other steps that were taken outside of the normal install process?