I'm not really very happy with this throwing an error.
I get it. People need to upgrade. But breaking things that are part of automated processes is a crappy way to get the message across.
As I mentioned, upgrades will take some time still, and now I have more work to deal with our unupgraded systems, so now it will take even longer to upgrade.
Thanks a bunch.
(Sorry for the sarcasm, but this is not a nice way to deal with the situation).
1. I am not happy with this myself. I wasn't happy when it happened in EL5 or EL4 or others. However, it is the way things have been done with EOL releases in CentOS for a very long time and was explained that this would be the way it would happen for a year.
2. Fix 1: Mirror the content from an archive of the site closer to your network. It is only a couple hundred gigabytes. Then either use /etc/hosts or change configs so it is used as the place to get content.
4. Fix 3: Just add enabled=0 to CentOS-Base.repo systems. They aren't going to get updates anymore anyway.
On my CentOS6 systems I have a /etc/yum.repos.d/CentOS-Vault.repo which I added the following to:
```
```
I then edited the CentOS-Base.repo to
```
```
I am now starting a slow copy of the vault for my later use.