Inconsistent Server Updates

[nibb]

All my servers have exactly the same config and software. Nothing changes between then and all of them get updated the same day. Except one of them is giving me an error:
Transaction check error:
file /usr/share/bash-completion/completions/pip3 from install of alt-python36-pip-9.0.1-5.el7.noarch conflicts with file from package python3-pip-9.0.3-5.el7.noarch

How is this even possible? I checked and the config is still the same as the other servers that updated fine.

 

[cPanelLauren]

Hello @nibb

While I can't speak for why it occurred as I don't know enough about the server to do so, I can tell you that this issue is a package conflict due to the fact that the standard version of python3-pip is installed on the server but CloudLinux's alt-python36-pip file is what the system is attempting to install due to the current configuration. If you're using CloudLinux's PHP Selector you will need the alt versions offered by CloudLinux.

 

[nibb]

All my systems have the same python packages, even the ones it tells there is a conflict. I have never touched or installed anything on the server that would affect python. Seems like a cloudlinux bug that did not properly removed or upgraded something before. Its even more strange because this server downloads and tries to update the same packages as all other servers with the yum update command. Others had no issues, this one complaints about that specific python package.

I'm not sure how to solve this, its blocking future updates. I tried removing the package and it still complaints.

 

[CloudLinux Skhristich]

All my systems have the same python packages, even the ones it tells there is a conflict. I have never touched or installed anything on the server that would affect python. Seems like a cloudlinux bug that did not properly removed or upgraded something before. Its even more strange because this server downloads and tries to update the same packages as all other servers with the yum update command. Others had no issues, this one complaints about that specific python package.

I'm not sure how to solve this, its blocking future updates. I tried removing the package and it still complaints.

Hello! To help you with this question we need a little bit more information, please create a ticket here https://cloudlinux.zendesk.com/hc/en-us/requests/new and technical experts will help you asap.
Regards, Sergey Khristich
Marketing coordinator CL OS

 

[cPanelLauren]

Hello @nibb

The response from @skhristich is a CloudLinux official response, to further troubleshoot the issue, I'd suggest opening a ticket using the link they provided.

 

[nibb]

I don't think you both get the issue here. The server is complaining about alt-python36-pip.noarch

That package IS NOT installed, so why does the yum update try to install this on this specific server? I checked, and no other servers have this package installed. This server is trying to install that package when it should not:

Running transaction check
Running transaction test


Transaction check error:
file /usr/share/bash-completion/completions/pip3 from install of alt-python36-pip-9.0.1-5.el7.noarch conflicts with file from package python3-pip-9.0.3-5.el7.noarch

# yum list alt-python36-pip-9.0.1-5.el7.noarch
Loaded plugins: fastestmirror, rhnplugin, universal-hooks
This system is receiving updates from CLN.
Loading mirror speeds from cached hostfile
* EA4: 208.74.123.61
* cpanel-addons-production-feed: 208.74.123.61
* cpanel-plugins: 208.74.123.61
* cloudlinux-x86_64-server-7: cl.banahosting.com
* epel: fedora-epel.mirror.lstn.net
Available Packages
alt-python36-pip.noarch 9.0.1-5.el7 cloudlinux-x86_64-server-7


This server affected and NO cloudlinux server I run has that package installed.

I then checked python3-pip-9.0.3-5.el7.noarch, and its installed, on the servers that are ok and strangely its also installed on this affected server. Yum is trying to install a package on this server it should not install. I think that is the issue.

 

[cPanelLauren]

I then checked python3-pip-9.0.3-5.el7.noarch, and its installed, on the servers that are ok and strangely its also installed on this affected server. Yum is trying to install a package on this server it should not install. I think that is the issue.

Yes, that is the issue, and why CloudLinux asked you to open a ticket. The attempt to install the incorrect package which originates from CloudLinux's repository is what's causing the issue.

If you purchased your license through us you are more than welcome to open a ticket with us and we'd be happy to look into it further, if we're unable to determine the cause of the issue we're able to hand it directly to the folks at CloudLinux.

If you do open a ticket please update this thread with the Ticket ID so that we can update this thread with the outcome.


Thanks!