vagrant up rundeck fails

turnopil commented 6 years ago

 rundeck: # 10 ACL Policy items for project anvils
    rundeck: anyone-node-allow.aclpolicy
    rundeck: anyone-resource-allow-read.aclpolicy
    rundeck: dev-jobs-allow-web_Restart.aclpolicy
    rundeck: dev-jobs-allow-web_Status.aclpolicy
    rundeck: dev-node-allow-www.aclpolicy
    rundeck: ops-jobs-allow-anvils.aclpolicy
    rundeck: ops-jobs-allow-db.aclpolicy
    rundeck: ops-jobs-deny-releng_Promote.aclpolicy
    rundeck: ops-node-allow-all.aclpolicy
    rundeck: releng-jobs-allow-release_Promote.aclpolicy
    rundeck: Running a adhoc command across the nodes tagged for anvils ...
    rundeck: /bin/rd: line 179:  -- ${node.description}: bad substitution
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.

I just comment part of 170 line in add-project.sh and now its works fine rd adhoc -p $PROJECT --follow --filter 'tags: anvils' -- whoami #\&\& echo " -- \${node.description}"

camservo commented 6 years ago

Having the same issue. Running on Mac.

mikeferrari8 commented 6 years ago

Had the same issue.

I had to make a couple changes to make things work for me. I am running Centos 7, Vagrant 2.1.5

install-rundeck.sh I had to change line 144 to match the output of a successful rundeck start, i think the message changed in newer versions of rundeck. Line 144 should looks like this. if ! grep "Grails application running" /var/log/rundeck/service.log

add -project.sh Line 170. I couldn't figure out the correct way to execute this command, it seems like the rd command options/syntax has changed over time. Because it's just a test, i figured it wouldn't hurt too much to skip it. As turnopil said above, i commented it out. #rd adhoc -p $PROJECT --follow --filter 'tags: anvils' -- whoami \&\& echo " -- \${node.description}"

After that i ran vagrant up and everything seems fine.

Hope that helps.

Also: To help troubleshoot i figured out that the login to the vm is root:vagrant

rundeck / anvils-demo

vagrant up rundeck fails #31