We are having an issue that seems to have appeared since last week with building OOD on our centos platform and using the rhel-server-rhscl-7-rpms repo. In fact it appears to have emerged just over the past day. Yesterday I could work around it by forcing a specific baseurl for this repo. Today, even the base url I used yesterday is not working.
The yum install ondemand results in a bunch of 404 errors looking for packages:
Hereâs an example of the error we saw on teklinks (this frequently resolves as our closest mirror via mirrorlist). Itâs the same error as for gtlib just a different package. In the full output itâs all the sclo packages.
Given this is what I saw yesterday afternoon and was then able to use gtlib successfully, I suspect whatever the change was it occurred with yesterdayâs mirror updates and teklinks just updated sooner than gtlib.
Because of the release of CentOS 7.7 they EOL SCL packages are now not included in the CentOS SCL repos as they didnât build those RPMs as they are EOL.
As a temporary work around you will have to install the CentOS SCLo Vault.
If/when the CentOS 7.6 vault gets populated, you could update the baseurl in the work around. As far as I could tell the CentOS 7.6 vault repos are still empty.
It depends on how your repo files are defined. If your repo files are pointed to SCL repos that are pinned to what was available when CentOS 7.6 was the latest OS , then you should be fine. If your repos are not pinned then this issue will manifest itself on a fresh install. If you installed OnDemand on CentOS 7.6 then do âyum updateâ, youâll be fine but fresh installs wonât be able to access the EOL SCL packages if your just install âCentOS 7â.
If your doing a fresh install on CentOS 7.6 or 7.7 using stock CentOS repo files, the work around is necessary. If your upgrading existing CentOS 7.6 to 7.7 then this issue shouldnât occur.
Our build environment was built using CentOS 7.6 a few months ago and all the packages were available then.
We install fresh all the time in dev. We are using packer to build OOD images for our dev deployments and using the CentOS7 cloud images as the base. Current is v1905 which appears to be CentOS7.6. Iâm gonna try out 1907 which might be 7.7.
So just to be clear, you are saying that regardless of 7.6 or 7.7 a fresh install will suffer this error unless we use the work around above?
I believe the workaround is needed regardless of 7.6 or 7.7 if you are doing a fresh install. Normally CentOS repos will just install CentOS 7 (latest) which now doesnât include several SCL packages needed by OnDemand. Usually the only way to install non-latest is to use the Vault repos or use local copies that are points-in-time. Normally if you install CentOS 7.6 with stock repos then do âyum updateâ youâll be at CentOS 7.7. Also installing packages with stock repos from CentOS 7.6 will pull in packages built for CentOS 7.7 as CentOS is a rolling upgrade type OS. If your using 7.6 specific repos this may not be the case but only ones I know of are the vault repos.
Upon further investigation the SCL repos from CentOS are minor version specific. The mirror URL generates 7.7 URLs so replacing the mirrorlist with a baseurl should be sufficient:
@jpr I just happen to recall this. Sounds like you have a really advanced CD pipeline, do you have any documentation on that? Blogs or anything? Weâd really like to hear what youâre up to and what benefits youâve gotten out of such a workflow.
We are using packer to build OOD images for our dev deployments and using the CentOS7 cloud images as the base. Current is v1905 which appears to be CentOS7.6. Iâm gonna try out 1907 which might be 7.7.