Closed mikewiebe closed 6 years ago
garethgreenaway
commented
6 years ago @mikewiebe Thanks for the report. Unfortunately I haven't been able to duplicate this issue. It also appears to be a git issue, not something specific to Salt. This might help: https://stackoverflow.com/questions/4826639/repack-of-git-repository-fails
mikewiebe
commented
6 years ago @garethgreenaway Thanks for the quick response.
Note sure I understand how this is a git issue. The only difference between the command that succeeds and the command that fails is the repo that I am specifying develop vs v2018.3.2.
sh bootstrap-salt.sh -D -G -H "$PROXY" git v2018.3.2sh bootstrap-salt.sh -D -G -H "$PROXY" git developIs there a different syntax I need to use to install from the develop branch?
mikewiebe
commented
6 years ago Not sure if this is relevant, but this is the method I used to download the boostrap-salt.sh script.
curl -o bootstrap-salt.sh -L -x "$PROXY" https://bootstrap.saltstack.com
mikewiebe
commented
6 years ago @garethgreenaway It appears that the problem was transient. I literally just tried the same command again and now it works. Not sure why but I do remember earlier today that it attempted to reach multiple mirrors before giving up. This time it still failed in for the first few attempts but eventually found one that worked.
* INFO: Found function install_centos_check_services
* INFO: Running install_centos_git_deps()
warning: /var/tmp/rpm-tmp.OmLnvT: Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY
Retrieving https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
Preparing... ########################################
Updating / installing...
epel-release-7-11 ########################################
Loaded plugins: fastestmirror
Cleaning repos: base epel extras saltstack updates
10 metadata files removed
6 sqlite files removed
0 metadata files removed
Loaded plugins: fastestmirror
https://mirrors.rit.edu/fedora/epel/7/x86_64/repodata/01ebe8e678104d63a96b35d914e338ad5f21c3158d56dbd078f1837a41581e36-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://sjc.edge.kernel.org/fedora-buffet/epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.nodesdirect.com/epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://ewr.edge.kernel.org/fedora-buffet/epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.pnl.gov/epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.us.leaseweb.net/epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://fedora.mirrors.pair.com/epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.rnet.missouri.edu/epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://download-ib01.fedoraproject.org/pub/epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirrors.develooper.com/epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.compevo.com/epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.lug.mtu.edu/epel/7/x86_64/repodata/5c4c30f8f0dbdae567993fcd4f8327ca51a1559b1d55fa36c376d992ba6baa35-primary.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
Loading mirror speeds from cached hostfile
* base: mirror.wdc1.us.leaseweb.net
* epel: mirror.team-cymru.com
* extras: repos.forethought.net
* updates: repos.lax.quadranet.com
Resolving Dependencies
--> Running transaction check
---> Package PyYAML.x86_64 0:3.11-1.el7 will be installed
--> Processing Dependency: libyaml-0.so.2()(64bit) for package: PyYAML-3.11-1.el7.x86_64
---> Package chkconfig.x86_64 0:1.3.61-4.el7 will be updated@mikewiebe One of the last errors reported by the bootstrap script:
error: index-pack died of signal 9
When I search for that, the results that are returned are people reporting issues with Git when attempting to clone various repositories.
mikewiebe
commented
6 years ago @garethgreenaway Looks like I spoke too soon. It got further in the process but then still failed again here:
Dependency Installed:
groff-base.x86_64 0:1.22.2-8.el7
less.x86_64 0:458-9.el7
libgnome-keyring.x86_64 0:3.12.0-1.el7
perl.x86_64 4:5.16.3-292.el7
perl-Carp.noarch 0:1.26-244.el7
perl-Encode.x86_64 0:2.51-7.el7
perl-Error.noarch 1:0.17020-2.el7
perl-Exporter.noarch 0:5.68-3.el7
perl-File-Path.noarch 0:2.09-2.el7
perl-File-Temp.noarch 0:0.23.01-3.el7
perl-Filter.x86_64 0:1.49-3.el7
perl-Getopt-Long.noarch 0:2.40-3.el7
perl-Git.noarch 0:1.8.3.1-14.el7_5
perl-HTTP-Tiny.noarch 0:0.033-3.el7
perl-PathTools.x86_64 0:3.40-5.el7
perl-Pod-Escapes.noarch 1:1.04-292.el7
perl-Pod-Perldoc.noarch 0:3.20-4.el7
perl-Pod-Simple.noarch 1:3.28-4.el7
perl-Pod-Usage.noarch 0:1.63-3.el7
perl-Scalar-List-Utils.x86_64 0:1.27-248.el7
perl-Socket.x86_64 0:2.010-4.el7
perl-Storable.x86_64 0:2.45-3.el7
perl-TermReadKey.x86_64 0:2.30-20.el7
perl-Text-ParseWords.noarch 0:3.29-4.el7
perl-Time-HiRes.x86_64 4:1.9725-3.el7
perl-Time-Local.noarch 0:1.2300-2.el7
perl-constant.noarch 0:1.27-2.el7
perl-libs.x86_64 4:5.16.3-292.el7
perl-macros.x86_64 4:5.16.3-292.el7
perl-parent.noarch 1:0.225-244.el7
perl-podlators.noarch 0:2.5.1-3.el7
perl-threads.x86_64 0:1.87-4.el7
perl-threads-shared.x86_64 0:1.43-6.el7
rsync.x86_64 0:3.1.2-4.el7
Complete!
* WARN: The git revision being installed does not match a Salt version tag. Shallow cloning disabled
Cloning into 'salt'...
error: index-pack died of signal 9
fatal: index-pack failed
* ERROR: Failed to run install_centos_git_deps()!!!
[root@guestshell ~]# salt --version
bash: salt: command not found
[root@guestshell ~]# This same step run install_centos_git_deps() succeeds with v2018.3.2
garethgreenaway
commented
6 years ago @mikewiebe Are you able to run a Git clone manually?
mikewiebe
commented
6 years ago @garethgreenaway Using the following command, I can clone both develop and v2018.3.2
[root@guestshell ~]# git clone https://github.com/saltstack/salt.git --branch v2018.3.2 --single-branch --depth 1
Cloning into 'salt'...
remote: Counting objects: 5343, done.
remote: Compressing objects: 100% (4812/4812), done.
remote: Total 5343 (delta 382), reused 4271 (delta 339), pack-reused 0
Receiving objects: 100% (5343/5343), 13.59 MiB | 6.76 MiB/s, done.
Resolving deltas: 100% (382/382), done.
Note: checking out 'e7893aedcf53a7761f8f30e9efb9f7129620a5d7'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name[root@guestshell ~]# git clone https://github.com/saltstack/salt.git --branch develop --single-branch --depth 1
Cloning into 'salt'...
remote: Counting objects: 5497, done.
remote: Compressing objects: 100% (5013/5013), done.
remote: Total 5497 (delta 399), reused 3611 (delta 284), pack-reused 0
Receiving objects: 100% (5497/5497), 14.53 MiB | 6.95 MiB/s, done.
Resolving deltas: 100% (399/399), done.
[root@guestshell ~]#
[root@guestshell ~]# cd salt/
[root@guestshell salt]# git status
# On branch develop
nothing to commit, working directory clean
[root@guestshell salt]# Do you know the exact git command that gets called by the bootstrap script so I can try that?
mikewiebe
commented
6 years ago @garethgreenaway It appears the problem is the amount of storage space I allocated to my hosting environment and the fact that for develop the script does not use a shallow clone. When I install v2018.3.2 it appears to require less storage space then develop. Once I allocated more storage I was able to install develop.
Writing /usr/lib/python2.7/site-packages/salt-2018.3.2_3878_g7f7bfb1-py2.7.egg-info
* INFO: Running install_centos_git_post()
* INFO: Running install_centos_check_services()
* INFO: Running install_centos_restart_daemons()
* INFO: Running daemons_running()
* INFO: Salt installed!
[root@guestshell ~]# salt --version
salt 2018.3.2-3878-g7f7bfb1 (Oxygen)
[root@guestshell ~]# The interesting thing is that when I look back through the success and failure logs I see the following:
For v2018.3.2:
* DEBUG: Installed git version: 1.8.3.1
* INFO: Git revision matches a Salt version tag, shallow cloning enabled.
* INFO: Attempting to shallow clone v2018.3.2 from Salt's repository https://github.com/saltstack/salt.git
Cloning into 'salt'...But for develop:
Nothing to do
* DEBUG: Installed git version: 1.8.3.1
* WARN: The git revision being installed does not match a Salt version tag. Shallow cloning disabled
Cloning into 'salt'...The fact that shallow cloaning is disabled for develop in this case would explain the storage resource problem.
garethgreenaway
commented
6 years ago @mikewiebe This makes sense. develop is our "master" branch so ideally you would want access to the other branches and tags. There is the -f option that will force shallow cloning.
mikewiebe
commented
6 years ago @garethgreenaway Thanks for your help on this! We can consider this case closed.
garethgreenaway
commented
6 years ago Awesome! Thanks!
Description of Issue/Question
I am attempting to install the salt minion from the latest github
developbranch but running into the following problem.NOTE: If I use the latest release tag
v2018.3.2, I don't see the same problem.Steps to Reproduce Issue
Failed install example using the
developbranchSuccessful install example using release tag
v2018.3.2Versions Report
Latest
developbranch.