for the containers and I could spin
up a test lab.
Kind Regards,
Robert Williams
On Mon, Jul 8, 2019 at 1:59 PM Claudio Rivas wrote:
> Ok the thing now is running, seems it needs to store on a temporal
> repository, mine was pointing to /var/jenkins/.ansible, so y generated a
> an
I understand and do not disagree.
I would try the process noted on that link. Keep in mind that because you
are in a container, you will need to add those to your dockerfile and
reaping the container.
I'm presently using a main Jenkins container that starts ephemeral
ansible/jnlp containers as
I do not currently have an example of this or an environment to test it in,
but a quick search turned up:
https://www.calazan.com/using-ssh-agent-forwarding-with-ansible/
You could also regenerate the key without a passphrase or fallback to UN/PW
auth.
Out of curiosity are you running Jenkins
Is your ssh key password protected and if so did you configured forwarding
in the ssh-agent or a similar work around?
On Sat, Jul 6, 2019, 3:07 PM Indian Velumani wrote:
> Hi,
>
> When want to start a docker image as container means you have run a
> command like
> docker run -d (image:
{"changed": false, "msg": "Destination /etc/yum.repos.d not writable"}"
>>
>
> This basically proves that your privilege elevating logic isn’t working.
> Fix that and your yum command will work as well.
>
>
>
>> On Wednesday, June 1
Have you validated that the user in question has the rights to make the
change and that your become is valid?
You could add a task before the repo change using `shell: whoami` to make
sure the become is working properly.
Also not sure if you need the single quotes on the ansible_become_user
Ansible 2.8.0
Python 3.6.8
azure-mgmt-devtestlabs 3.0.0
https://docs.ansible.com/ansible/latest/modules/azure_rm_devtestlabvirtualmachine_module.html
I am seeing behavior for azure_rm_devtestlabvirtualmachine where a VMs tags
never get updated/appended or removed - the tags specified
What version of Ansible and Python are you running?
I have seen odd errors like your
KeyError: 'diskSizeGB'
with the azure_rm_devtestlabvirtualmachine - seems almost like it isnt
properly determining what fields are required and whats not. I was seeing
things like the virtual network being a
I am trying to figure out the same issue. Please let me know if you have it
resolved.
Thanks,
On Monday, August 22, 2016 at 7:34:59 AM UTC-5, James Lovato wrote:
>
> The test to the loadbalancer itself never fails, and serves the same
> content as the websites (although host and metadata are a
All , i have searched many sites but i am able to get this playbook to
work. I am trying to build a vm via ansible and i get the following error
message below. I have also posted my playbook. Any help would be greatly
appreciated.
Thanks in advance,
___PLAYBOOK
---
- hosts: 127.0.0.1
n connect\nself.timeout, self.source_address)\n File
\"/usr/lib64/python2.7/socket.py\", line 571, in create_connection\n
raise err\nsocket.error: [Errno 111] Connection refused\n",
"module_stdout": "",
"msg": "MODULE FAILURE"
}
to r
I tried adding local but that did not help. Here is the output:
Using /etc/ansible/ansible.cfg as config file
PLAYBOOK: create_appVCLOUD.yml
*
1 plays in create_appVCLOUD.yml
PLAY RECAP
Hello, I am new to Ansible and am having trouble spinning up a vm from a
template using Ansible. I am unsure on what to put for "hosts" in my
playbook. Should this be the vcenter hostname , vsphere hostname or
something else? Any help is appreciated. Thanks in advance.
*PlayBook*
---
- hosts:
13 matches
Mail list logo
