yum update on CentOS 7 OpenVZ container you might get a following error:
--> Processing Conflict: systemd-219-19.el7.x86_64 conflicts initscripts < 9.49.28-1 --> Finished Dependency Resolution Error: systemd conflicts with initscripts-9.49.17-1.el7.x86_64 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
Exact version I was running on this server is CentOS Linux release 7.1.1503 (Core), and updates were failing due to them requiring a newer systemd version, which required a newer version, v9.49.28 at least, of initscripts installed.
Reason why systemd was conflicting with current version of initscripts, instead of just updating them to newer version, was that initscripts were excluded from update in
[ro[email protected] ~]# grep exclude /etc/yum.conf exclude=initscripts*
There are no default exclude packages in default CentOS/RHEL installs, and it wasn’t put there by me, so question is why was initscripts excluded from updates.
Issues with initscripts v9.49.24 in CentOS 7 OpenVZ containers
It turns out there were some issues with initscripts v9.49.24, which seemed to introduce problems with network connectivity on CentOS 7 OpenVZ VPS machines.
I commented out
yum.conf, and checked the currently available version.
[[email protected] ~]# grep exclude /etc/yum.conf #exclude=initscripts* [[email protected] ~]# yum check-updates initscripts Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirrors.greenmountainaccess.net * epel: mirror.nexcess.net * extras: mirrors.lga7.us.voxel.net * updates: mirror.dattobackup.com * webtatic: us-east.repo.webtatic.com initscripts.x86_64 9.49.30-1.el7 base
Current version is v9.49.30, so I presumed issues with v9.49.24 were corrected in this version, and proceeded with the update.
Update has completed successfully, and all packages including initscrips were updated to latest version, as was CentOS.
[[email protected] ~]# cat /etc/redhat-release CentOS Linux release 7.2.1511 (Core)
I haven’t noticed any network or any other issues on the VPS after the upgrade, so it seems any network issues from v9.49.24, don’t exist in v9.49.30.
[[email protected] ~]# rpm -qa | grep initscripts initscripts-9.49.30-1.el7.x86_64