receiving 404 not found
https://repo.saltproject.io/yum/amazon/latest/x86_64/latest/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
This path does not exist anymore. Manually looking, it seems "https://repo.saltproject.io/yum/amazon/" directory only contains the "2" folder. "latest" does not exist.
NAME="Amazon Linux AMI"
VERSION="2018.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2018.03"
PRETTY_NAME="Amazon Linux AMI 2018.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2018.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"
Amazon Linux AMI release 2018.03
sudo curl -fsSL https://bootstrap.saltproject.io -o install_salt.sh
sudo sh install_salt.sh git -P -x python3 -j "`cat /tmp/minion_conf`" -D
(debug logs attached)
bootstrap-salt.log
NAME="Amazon Linux AMI"
VERSION="2018.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2018.03"
PRETTY_NAME="Amazon Linux AMI 2018.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2018.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"
Amazon Linux AMI release 2018.03
amazonlinux 1 is end of life, and the salt packages for it have been moved to https://archive.repo.saltproject.io
You can use -R archive.repo.saltproject.io as an argument to the bootstrap script if you want to use them. They are unsupported and all contain CVEs.
Ah. I understand. Thanks for the quick response! I just tried this with -R archive.repo.saltproject.io , but I receive the same error. Are there additional flags which I must set for this to work properly? I glanced through the documentation, but nothing stood out to me.
sudo sh install_salt.sh -R "archive.repo.saltproject.io" -j "$(cat /tmp/minion_conf)" -D
I don't think salt touches your repo files for salt if they already exist, you might have to rm -i /etc/yum.repos.d/salt* before you try again. it works for me on a fresh docker container.
That was it! Thank you!!
Most helpful comment
I don't think salt touches your repo files for salt if they already exist, you might have to
rm -i /etc/yum.repos.d/salt*before you try again. it works for me on a fresh docker container.