Missing dependency for

[bkuhl]

Thanks for putting together something like this. I ran into a small issue when running vagrant up... both minions and the master threw the following error:

==> minion2: /usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/provider/service/bsd.rb:12: warning: class variable access from toplevel
==> minion2: notice: /Stage[pre]/Mirrors::Yum/File[epel-salt.repo]/ensure: defined content as '{md5}b88d8d90898d073fd35c57623dbbc21c'
==> minion2: notice: /Stage[pre]/Mirrors::Yum/Exec[yum_makecache]: Triggered 'refresh' from 1 events
==> minion2: notice: /Stage[pre]/Vagrant/Group[puppet]/ensure: created
==> minion2: notice: /Stage[pre]/Networking/File[/etc/hosts]/content: content changed '{md5}571c763e747cd16d8b9352fac8be5012' to '{md5}4145ec6fe7d8fea21c5aec18d26366a6'
==> minion2: err: /Stage[main]/Salt/Package[salt-minion]/ensure: change from absent to latest failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install salt-minion' returned 1: salt-0.9.7-1.el5.noarch from epel-salt has depsolving problems
==> minion2:   --> Missing Dependency: python26-jinja2 is needed by package salt-0.9.7-1.el5.noarch (epel-salt)
==> minion2: Error: Missing Dependency: python26-jinja2 is needed by package salt-0.9.7-1.el5.noarch (epel-salt)
==> minion2:  You could try using --skip-broken to work around the problem
==> minion2:  You could try running: package-cleanup --problems
==> minion2:                         package-cleanup --dupes
==> minion2:                         rpm -Va --nofiles --nodigest
==> minion2: The program package-cleanup is found in the yum-utils package.
==> minion2:  at /tmp/vagrant-puppet-7/modules-0/salt/manifests/init.pp:22
==> minion2: notice: /Stage[main]/Salt/Service[salt-minion]: Dependency Package[salt-minion] has failures: true
==> minion2: warning: /Stage[main]/Salt/Service[salt-minion]: Skipping because of failed dependencies
==> minion2: notice: Finished catalog run in 45.56 seconds
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

[elasticdog]

Hrm, it's been a few years since I've touched this, but I'm guessing that the epel-salt repo is either unmaintained or they've just moved on from supporting CentOS 5.7. I honestly don't have time right now to fire things up and take a look to fix this.

If 5.7 is the environment you definitely need to test with (rather than a newer OS release), you'll probably have to track down all of the dependencies and make adjustments to salt-sandbox. If you're not stuck with 5.7, I'd try using a newer release and see if things are fixed without making any changes. If that doesn't work, then you'll probably have to adjust the provisioning scripts based on whatever the current recommended method is for installing Salt. I hope that helps.

[bkuhl]

Thanks for the feedback. I may come back and revisit this, but for the time being I've moved on to another portion of my project.