I've seen the similar behaviour. For some reason cloudmonkey try to persist the configs each time your run something.
If i open cloudmonkey in multiple terminals and use different profiles and execute commands in mutliple terminals in parallel - i've seen cloudmonkey mess up the config for one of open profiles. Specifically, the URL of cloudstack in profile1 might be changed with url of cloudstack in profile2. Rohit, is there a reason why cloudmonkey tries to update the settings in config file each time something gets executed? On 5/24/16 1:31 PM, Yiping Zhang wrote: > Hi, > > We have a few scripts that use cloudmonkey to talk to CloudStack server. The > scripts are invoked by Puppet once per hour. > > However, every once a while, the /root/.cloudmonkey/config file would be over > written with default settings. That is, blank apikey/secretkey, default > password, default log file location etc. > > I am wondering by any chance that cloudmonkey would put a default config file > in place for some reason ? > > Thanks, > > Yiping >
