[ansible-project] vmware_guest_snapshot module unable to find VM with Ansible 2.4.2

I have recently updated to Ansible 2.4.2 I have plays that will remove old snapshots from specific VMs and will create new snapshots for those VMs. The remove playbook is as follows: --- - hosts: localhost vars_prompt: - name: username prompt: "VCenter username" private: no

[ansible-project] Re: vmware_guest_snapshot module unable to find VM with Ansible 2.4.2

I was able to use another module to solve this issue. I setup a play using the module vmware_guest_find . The play I used is: - hosts: localhost vars_prompt: - name: username prompt: "VCenter username"

[ansible-project] Restart server playbook fails on one set of targets, but not on another.

I have the following playbook snippet --- - hosts: collector become: true become_method: su become_user: root tasks: - name: restart server, if kernel updated command: reboot async: 1 poll: 0 ignore_errors: true notify: - wait for server to restart

[ansible-project] Starting AppDynamics with play

I have a play that is fairly simple, to start AppDynamics. I am able to start/stop each part as needed, except a portion called EUM (End User Monitoring). My test play looks like: --- - hosts: collector become: true become_method: su become_user: root tasks: - name: stop eum

Re: [ansible-project] Default shell behavior: Where are scripts executed? No such file or directory.

Your subject line has a question in it, but the body does not. Is your question "Where are scripts executed?" If that is your question then yes, you're correct, it should be the home directory of the user you logged into the remote server with. You can see by doing something like ansible

[ansible-project] Re: Starting AppDynamics with play

d print it, it still only displays the "EUM Processor started..." line, but the EUM process is actually, as opposed to previously where it would not be fully started before the play ended. Hope this helps someone else out! On Tuesday, March 13, 2018 at 8:10:49 AM UTC-4, Patrick

[ansible-project] Re: git checkout to new branch and change back to local user

> > I can help to address #2 at least for now. > Ansible does not allow you to chain "Become" statements. In other words you cannot log in as user1, become root, and then become user2 (or even user1) in the same play. You could address this in a few different ways that I know of: - split

[ansible-project] Re: git checkout to new branch and change back to local user

Good catch. You're correct, it is possible, I was mistaken. Practically is it possible to be able to provide multiple sets of credentials for your example? I've always done a work around, such as I listed in the other comment, since I can pass my current logon (-k) username/password, and can

Re: [ansible-project] Starting AppDynamics with play

Good idea Kai, thank you. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to