I'm trying to execute a custom mcollective RPC call via Atlassian Bamboo and have run into a frustrating issue. I've posted this question to the Bamboo community help page but figured I could try asking the same thing here in case anyone's run into this problem as well, even though I suspect it's not actually an Mcollective issue.
Basically, my custom RPC call restarts an instance of Glassfish. It's a simple call to Mcollective's "run()" command and it works fine when I run it from the command line on the bamboo server. However, if I run it as a "script" task from within bamboo, it just hangs indefinitely. I wondered if it's something to do with mco's run command opening subshells and this somehow affecting what bamboo is getting back, but AFAIK it shouldn't be an issue. I've tested the output received on the command line, and the exit code seems to be returned fine. Does anyone have any ideas or suggestions? Anyone using mcollective in this way that has encountered an issue like this? Thanks, Guy -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/93d789dd-8ad8-4327-99da-426f1f1de5fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
