Closed shaneholloman closed 2 years ago
Do you have the list of RPMs installed prior to the attempt? Can you add -x
to the set -e
line so we can get a more verbose output too?
@Djelibeybi
Avi set -x
was the ticket to find the issue! Awesome mate.
Turns out in my case
[root@zabbix-proxy1 ansible]# rpm -q --whatprovides /etc/redhat-release
centos-linux-release-8.3-1.2011.el8.noarch
centos-linux-release-8.4-1.2105.el8.noarch
So I dnf remove centos-linux-release-8.3-1.2011.el8.noarch
And the script happily went on it's merry way
Huzzah! It's weird that you managed to get two centos-linux-release
packages installed, but given one was from 2011, I guess the reason is lost to history. I'm going to close this issue, but feel free to open a new one if anything else occurs.
BTW, since centos8 repos have move to vault
I also
Change to following line to each respective file:
[root@etp-monitor1 ansible]# vi /etc/yum.repos.d/CentOS-Linux-BaseOS.repo
[root@etp-monitor1 ansible]# vi /etc/yum.repos.d/CentOS-Linux-AppStream.repo
CentOS-Linux-BaseOS.repo
baseurl=http://vault.centos.org/$contentdir/$releasever/BaseOS/$basearch/os/
\ CentOS-Linux-AppStream.repobaseurl=http://vault.centos.org/$contentdir/$releasever/AppStream/$basearch/os/
Comment the mirrors
Oh, good point. Let me fix that up.
Looking inside the script I made an attempt to understand at which point the script wanted to exit, but I failed.
I was hoping this info & log would be helpful to the devs here to share some possibilities as to what "An error occurred..." that would cause this break at this point in the script.
I have run this wonderful script successfully on many very different VMs
about vm
/boot
for more kernelsscript run