Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Centos 6 support broken #198

Closed
oniGino opened this issue Mar 24, 2021 · 5 comments
Closed

Centos 6 support broken #198

oniGino opened this issue Mar 24, 2021 · 5 comments

Comments

@oniGino
Copy link

oniGino commented Mar 24, 2021

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: all
  • Ruby:
  • Distribution: centos 6
  • Module version: latest

Replace mirrorlist for centos6 with
baseurl=http://vault.centos.org/6.10/os/$basearch/
to fix issue

see
https://www.getpagespeed.com/server-setup/how-to-fix-yum-after-centos-6-went-eol

@TheMeier
Copy link

TheMeier commented Jun 8, 2021

CentOS 6 is EOL.

@oniGino
Copy link
Author

oniGino commented Jun 8, 2021

CentOS 6 is EOL.

thats correct, exactly why you need to update your project code to point to the repo archive.

just because a distro is EOL doesnt mean environments magically stop running it.

@TheMeier
Copy link

TheMeier commented Jun 8, 2021

Actually it is quite common to simply remove support for EOL platforms. I was just about to work on a PR for that...

@TJM
Copy link

TJM commented Jun 8, 2021

@oniGino You can supply alternate repo URLs in hieradata if you need to support an EOL platform (or, in my case, if you can't reach the Internet and have to supply an internal server), but support for CentOS6 should be removed from this module, and definitely should not be re-pointed to archive. Stuff breaking may be the only way some admins know they have an EOL OS running and they are not actually receiving updates for it. :)

Technically, the removal should have been done over 6 months ago, oops.

@oniGino
Copy link
Author

oniGino commented Jun 8, 2021

Your choice.
Thanks, we already have overloaded the hieradata for this.

But I would say, as someone managing a 500+ node puppet environment, where I do not always have control over distro versions, formally dropping support in your docs or referencing vault for older distros might prove helpful for others as well.

@oniGino oniGino closed this as completed Aug 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants