Hi All,

my scope: update the cluster of my chair from centos 7.2 to centos 7.6 (and all dependencies) and not to the last available version (8).

reason: I have to install a specific version of ANSYS 19R2(multiphysics simulation software), which only works under 7.6.

I wanted to use the following command:

yum update doc

but I am not sure if the release would be updated autmatically from 7.2 to 8. Do you hav any experience with?

Already tried without success:

downloaded the Everything.iso image from here . After validation of the image file using the following procedure (see following 3 links: link1 , link2 and link3 ), the next issue appears: I cannot mount the .iso file (using the following procedure), when I use:
$mount -o -loop CentOS-7-x86_64-Everything-1810.iso /media/7_6_centos/

mount: /dev/loop0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.

Any idea will be wellcome because I have the cluster completely stopped.

Thanks in advance.

Luis

yum update should bring you to the current version of 7, which is CentOS Linux 7.7.1908.
You should be running updates periodically.

Hi scasey,

I would prefer to update to the last one as you recommend but as we simulate in another bigger cluster, in which centos 7.6 is installed, we have to replicate the same conditions in our cluster to avoid issues with different OS, softwares, etc...

is not the current release the 8 one?

Check this page for methods to lock the OS at a given version (inc subversion) eg 7.6 https://avinetworks.com/docs/18.2/ho...ecific-update/

1 members found this post helpful.

You can only update to the latest available 7.x version, as previous point updates are deleted from the servers when the next one gets released.
The 7.6 directory ON those servers now only contain a 'readme' file:
So when you use /7/ in your repo list you will get updated to the current latest 7.x release.

The current (and latest) release of CentOS 7 is 7.7.1908 (which means it is based on the 2019/08 sources from RHEL). But there probably will be a 7.8 one later this year.

8.1.1911 for the 8 series,
7.7.1908 for the 7 series
and even the 6 series of CentOS is still supported:
6.10 is the latest (and probably the last) point update for that.
It was released in 2018 (july).

BTW: the 6 series was the last one to still support a 32-bit kernel and iso images:

CentOS 7.6 repo URL's
os/x86_64/ : http://vault.centos.org/7.6.1810/os/x86_64/
updates/x86_64/ : http://vault.centos.org/7.6.1810/updates/x86_64/

Replace the repo files in /etc/yum.repos.d/ wih this file

Note that this vault site is an archive:
So even all updates in this tree are more than half a year out of date:
Packages/ 2019-09-20 01:58

The OP would be best advised to update all of the CentOS systems, both the clients and servers, to 7.7 (and 7.8 as soon as it will be released).
Note that CentOS (following RHEL) will only issue bugfixes and security patches in point releases, NOT newer versions.So everything should stay working after updating to 7.7

Hi chrism01,


thanks for the link. I have not yet checked this way, but I have found my mistake when I mounted the .iso image (see my first thread).

$mount -o -loop CentOS-7-x86_64-Everything-1810.iso /media/7_6_centos/

mount: /dev/loop0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.

The first line is actually not an error but a warning "mount: /dev/loop0 is write-protected, mounting read-only". In my case I wanted to read only the -iso file, so I can use "mount -r" -r= read-only or live with this warning. That´s all.

For the second line"mount: wrong fs type, bad option, bad superblock on /dev/loop0,... " I can avoid that using "-t auto", allowing linux to detect automatically the type:
mount -t auto CentOS-7-x86_64-Everything-1810.iso

After that I followed the instructions 2-7 (see here) and the update from CentOS 7.2 to 7.6 worked.
If you want to update other packages, which are not dependent of the centos-release 7.6, I have used the famous:
yum update < names of packages to be installed>

or better, create a new file: new_repo.repo with the information you suggested maintaining a back-up of the .repo files in the folder /etc/yum.repos.d/.
What I don´t understand is: when I add the new file new_repo.repo in the folder yum.repos.d, how does linux know that it has to take the new one instead of the older files??

actually this is not completely correct. In my case I have found the deprecated repositories (see my first thread) and could download the 7.6 release from the CERN repository (not only the readme) You are right that to find the deprecated repositories is quite difficult... but possible

And I deliberately didn't mention them as they are not being maintained anymore, so bugfixes and/or security problems will not be fixed IN them, they're a pure (and static) archive of old releases.
The 7.7 point update is just that: 7.6 with newer bugfixes and security updates (just as all 7.x updates are the 7 release with all - at that point - available fixes).

RHEL is very conservative with that, all 7.x releases should be the same, with only necessary updates applied, so a point update should never break existing software.
There are no version updates to kernel or supplied applications, unless really unavoidable (mozilla firefox/thunderbird is one as even the esr versions are only maintained for a year).

Hey there! I understand your frustration with trying to update your cluster from Centos 7.2 to 7.6. I've had a similar experience in the past. I would recommend trying the command "yum update --skip-broken" instead of just "yum update doc." This will only update packages that are not causing conflicts or errors.

Oh? Since this is a two year old thread and you had the same issue, why don't you post your solution??

::EDIT:: And surprising no one, you came back to add your spam link...which has been reported, and will be deleted.