Re: [ansible-project] Re: VMware VM creation works but on boot the network adapter is disconnected

[N Owens]

Chris,
The only thing I've seen so far is that you want to make sure the template
or image you are cloning has the latest version of vmware tools installed.

Norm

On Fri, May 27, 2022 at 11:16 AM Christopher Bachmeyer <
chris.bachme...@gmail.com> wrote:

> Hi, Norm,
>
> I have read about that issue in the forums regarding Perl and vmware tools
> on RHEL/ CentOS.  As far as I know, Windows does not need Perl ... ?
>
> I read on a forum post that someone found a vDS was somehow at the root of
> this issue which is, of course, what I am using as the network.  That
> gentleman switched over to a simple vswitch which seemed to alleviate this
> issues.
>
> You can read about it here along with a few other leads:
> https://github.com/ansible/ansible/issues/24506
>
> Sure, great!  I've redacted sensitive info.  The content within angle
> brackets indicate redacted or changed content.
>
> I am trying to work with a Windows2019 template.
>
> ---
> # Ansible play to create a virtual vmware within a vSphere environment
> # Extra Variables are declared in the Ansible play but assigned in Template
> # Extra Vars include: "memory", "vm_name", and "template"
>
> - name: Ansible play for the creation of a virtual machine within vSphere
>   hosts: localhost
>   #connection: local
>   gather_facts: no
>
>   vars:
> cluster_name: <"My Test Cluster">
> datacenter_name: 
> vcenter_server: 
> datastore_name: 
>
>   tasks:
>   - name: Create a virtual machine within a particular vSphere cluster.
> vmware_guest:
>   hostname: "{{ vcenter_server }}"
>   validate_certs: false
>   name: "{{ vm_name }}"
>   state: poweredon
>   template: "{{ template }}"
>   datacenter: "{{ datacenter_name }}"
>   folder: /{{ datacenter_name }}/vm
>   cluster: "{{ cluster_name }}"
>   datastore: "{{ datastore_name }}"
>   hardware:
> memory_mb: "{{ memory | int }}"
> num_cpus: 2
> num_cpu_cores_per_socket: 2
>   networks:
>   - name: 
> ip: 
> netmask: 
> type: static
> gateway: 
> connected: true
> start_connected: true
> dns_servers:
> - 
>   wait_for_ip_address: true
>   customization:
> existing_vm: true
> hostname: "{{ vm_name }}"
> dns_servers:
> - 
> - 
> domainadmin: "{{ admin }}"
> domainadminpassword: "{{ admin_pass }}"
> joindomain: 
> #  wait_for_customization: yes
> delegate_to: localhost
>
> I just noticed I am not using the "guest_id" param but according to the
> docs, I do not need this as I am deploying from a template.
>
> Thanks for taking a look, much appreciated!
>
>
> On Friday, May 27, 2022 at 2:45:21 AM UTC-6 owen...@gmail.com wrote:
>
>> Christopher,
>>
>> I had a similar issue with RHEL.  I found that the image/template that I
>> was using to build my VM was missing a perl module.  I’ll have to check my
>> notes for which module.  Once I installed that module in my image template,
>> it worked.
>>
>> I now need to do the same and get windows VMs spun up.  Would you mind
>> sharing your playbook?  I have a test environment and I would be willing to
>> help troubleshoot your issue.
>>
>> Regards,
>>
>> Norm
>>
>> Sent from my iPhone
>>
>> On May 26, 2022, at 11:05 PM, Christopher Bachmeyer 
>> wrote:
>>
>> 
>>
>> We're on Ansible Tower 3.8.3 and Ansible core is 2.9.x.
>>
>> I am trying to use the community.vmware collection and looking to deploy
>> Windows and Linux vms to vSphere.
>> When deploying Windows 2019 vms, the network adapter is always
>> disconnected.
>>
>> It seems like many are having issues with the same issue but there are
>> few if any solutions.
>>
>> Any suggestions?
>>
>> Thanks!
>>
>> On Wednesday, March 31, 2021 at 5:38:32 AM UTC-6 owen...@gmail.com wrote:
>>
>>> I'm using Ansible Tower 3.8.2.
>>> Ansible core is 2.9.15
>>>
>>> I'm using the vmware_rest collection.
>>>
>>> I'm able to get the linux VM created from a template.  And the VM does
>>> poweron.  But when it comes up the network adapter does not.  It is in
>>> disconnected state.
>>>
>>> My linux VM is RHEL 8.2
>>>
>>> I see online that many folks have had this issue but I'm not seeing what
>>> the solution is for it.
>>>
>>> Can anyone offer any tips that may help me solve this problem?
>>>
>>> Thanks,
>>>
>>> Norm
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Ansible Project" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/ansible-project/wsdacUC7Gz4/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> ansible-proje...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ansible-project/37c0545e-9775-42bb-a1d6-7e48668eb123n%40googlegroups.com
>> 

Re: [ansible-project] Exceptions with vmware_deploy_ovf module

[Vichu]

Thanks again for looking into this. Actually, I have hardcoded the values 
in the actual yaml file whereas here I have given the variable to hide the 
actual ip and credential info. With that said, that is not the problem 
here. 

Appreciate your time & help. 

On Wednesday, June 1, 2022 at 1:13:42 AM UTC-7 dnmv...@gmail.com wrote:

> On Wed, 1 Jun 2022 at 02:46, Vichu  wrote:
>
>> hello there,
>>
>> I am trying to automate the cloud director OVA deployment in our local 
>> lab. Built a playbook but caught up with the exception during the 
>> execution. Need your advice to unblock from this. 
>>
>> *Error found:*
>>
>> An exception occurred during task execution. To see the full traceback, 
>> use -vvv. The error was: TypeError: For "valuepected type str, but got int
>> fatal: [localhost -> localhost]: FAILED! => {"changed": false, 
>> "module_stderr": "Traceback (most recent call last):\n e 
>> \"/root/.ansible/tmp/ansible-tmp-1654025411.9694972-30359-230767769553477/AnsiballZ_vmware_deploy_ovf.py\",
>>  
>> line 100 \n_ansiballz_main()\n  File 
>> \"/root/.ansible/tmp/ansible-tmp-1654025411.9694972-30359-230767769553477/AnslZ_vmware_deploy_ovf.py\",
>>  
>> line 92, in _ansiballz_main\ninvoke_module(zipped_mod, temp_path, 
>> ANSIBALLZ_PARAMS)\n   
>> \"/root/.ansible/tmp/ansible-tmp-1654025411.9694972-30359-230767769553477/AnsiballZ_vmware_deploy_ovf.py\",
>>  
>> line 41, nvoke_module\nrun_name='__main__', alter_sys=True)\n  File 
>> \"/usr/lib64/python3.6/runpy.py\", line 205, in run_modnreturn 
>> _run_module_code(code, init_globals, run_name, mod_spec)\n  File 
>> \"/usr/lib64/python3.6/runpy.py\", line 9n _run_module_code\nmod_name, 
>> mod_spec, pkg_name, script_name)\n  File \"/usr/lib64/python3.6/runpy.py\", 
>> line 85,_run_code\nexec(code, run_globals)\n  File 
>> \"/tmp/ansible_vmware_deploy_ovf_payload_r7j_7pzv/ansible_vmware_deploy_payload.zip/ansible_collections/community/vmware/plugins/modules/vmware_deploy_ovf.py\",
>>  
>> line 755, in \n 
>>  
>> Fil/tmp/ansible_vmware_deploy_ovf_payload_r7j_7pzv/ansible_vmware_deploy_ovf_payload.zip/ansible_collections/community/vm/plugins/modules/vmware_deploy_ovf.py\",
>>  
>> line 743, in main\n  File 
>> \"/tmp/ansible_vmware_deploy_ovf_payload_r7j_7pzv/ale_vmware_deploy_ovf_payload.zip/ansible_collections/community/vmware/plugins/modules/vmware_deploy_ovf.py\",
>>  
>> line 530 upload\n  File 
>> \"/tmp/ansible_vmware_deploy_ovf_payload_r7j_7pzv/ansible_vmware_deploy_ovf_payload.zip/ansible_collecs/community/vmware/plugins/modules/vmware_deploy_ovf.py\",
>>  
>> line 443, in get_lease\n  File 
>> \"/usr/local/lib/python3.6/spackages/pyVmomi/VmomiSupport.py\", line 663, 
>> in __setattr__\nCheckField(self._GetPropertyInfo(name), val)\n 
>>  Fileusr/local/lib/python3.6/site-packages/pyVmomi/VmomiSupport.py\", line 
>> 1098, in CheckField\n% (info.name, info.typeame__, 
>> valType.__name__))\nTypeError: For \"value\" expected type str, but got 
>> int\n", "module_stdout": "", "msg": "MO FAILURE\nSee stdout/stderr for the 
>> exact error", "rc": 1}
>>
>> *Environment Detail:*
>> PackageVersion
>> -- --
>> ansible2.9.0
>> asn1crypto 1.3.0
>> certifi2019.11.28
>> cffi   1.13.2
>> chardet3.0.4
>> charset-normalizer 2.0.12
>> cryptography   2.8
>> dnspython  1.16.0
>> idna   2.8
>> Jinja2 2.10.3
>> jmespath   0.9.4
>> lxml   4.4.2
>> MarkupSafe 1.1.1
>> pip21.3.1
>> pycparser  2.19
>> pyvmomi7.0.3
>> PyYAML 5.3
>> requests   2.22.0
>> setuptools 39.2.0
>> six1.13.0
>> urllib31.25.7
>>
>> *Here is my play book:*
>>
>> vmware_deploy_ovf:
>>   hostname: "{{ vcenter_hostname }}"
>>   username: "{{ vcenter_username }}"
>>   password: "{{ vcenter_password }}"
>>   validate_certs: "{{ ova_validate_certs }}"
>>   name: Auto-VCD-10.3.1
>>   datacenter: "{{ vcenter_default_datacenter }}"
>>   cluster: "{{ vcenter_default_cluster }}"
>>   datastore: nfs-ds
>>   disk_provisioning: thin
>>   networks:
>> "Network 1": "VM Network"
>> #"Network 2": "Network78"
>>   ova: /OVA/VMware_Cloud_Director.ova
>>   allow_duplicates: no
>>   power_on: yes
>>   fail_on_spec_warnings: yes
>>   wait: yes
>>   wait_for_ip_address: yes
>>   inject_ovf_env: yes
>>   properties:
>> vami.DNS.VMware_vCloud_Director: "{{ dns_server }}"
>> vami.domain.VMware_vCloud_Director: "{{ domain name"
>>
>
> There are missing brackets here 
>
>
>
>
>> vami.gateway.VMware_vCloud_Director:  "{{ gateway }}"
>> vami.ip0.VMware_vCloud_Director: "{{ ip0address }}"
>> vami.ip1.VMware_vCloud_Director: "{{ ip1address }}"
>> vami.netmask0.VMware_vCloud_Director: "{{ netmask }}"
>> 

[ansible-project] Ansible 6.0.0b2 (including ansible-core 2.13) is available for testing!

[Ompragash Viswanathan]

Hi all,

We're happy to announce that the second beta release of Ansible 6.0.0 is now
available for testing !

Ansible 6.0.0 will include ansible-core 2.13 as well as a curated set
of Ansible
collections to provide a vast number of modules and plugins.

This is a major version update from Ansible 5.x which included

ansible-core 2.12 and there may be backwards incompatibilities in the core
playbook language.

How to get it

-

This pre-release is available on PyPI and can be installed with pip:

```

$ pip install ansible==6.0.0b2 --user

```

The sources for this release can be found here:

Release tarball:

https://pypi.python.org/packages/source/a/ansible/ansible-6.0.0b2.tar.gz

SHA256: e5656cef9fbc1cebf5bb1c77b2fd34c257846385b57f35b0507bc3c6fd928b5a

Wheel package:
https://files.pythonhosted.org/packages/py3/a/ansible/ansible-6.0.0b2-py3-none-any.whl


SHA256: d989553fde417f2591b9b02a896d9bc81f4aac00d2c4f4581204f53291075c93

What's new in Ansible 6.0.0b2

---

* Python wheels are now available for both Ansible 6 and ansible-core

2.13.x, resulting in significantly improved installation performance.

* In addition, Ansible 6 will no longer install some unnecessary files

from the included Ansible collections such as tests or hidden files &

directories in order to further improve installation performance and

reduce the size on disk. These files are still available in the source

tarball if necessary.

* The changelog for ansible-core 2.13 installed by this release of

ansible is available here:

https://github.com/ansible/ansible/blob/stable-2.13/changelogs/CHANGELOG-v2.13.rst

* Collections which have opted into being a part of the Ansible-6

unified changelog will have an entry on this page:

https://github.com/ansible-community/ansible-build-data/blob/main/6/CHANGELOG-v6.rst

* For collections which have not opted into the unified changelog, you may
find more information on https://galaxy.ansible.com or their

source repository.

For example, the community.crypto collection would be found at

https://galaxy.ansible.com/community/crypto and you can find a link to the
source repository under the "Repo" button at the top right.

What's the schedule for new Ansible releases after 6.0.0b2 ?

-

* Maintenance releases of Ansible 5.x will occur approximately every three
weeks (Ansible 5.8.0, Ansible 5.9.0, etc) until the release of Ansible
6.0.0. They will contain bugfixes and new features but no backwards
incompatibilities.

* The stable release of Ansible 6.0.0 is expected on 2022-06-21.

More information can be found in the Ansible 6 roadmap:

https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_6.html

* Please note that the release of ansible-core 2.13 in May 2022

coincides with the end-of-life of ansible 2.9 and ansible-base 2.10:

https://groups.google.com/g/ansible-announce/c/kegIH5_okmg/

Porting Help

-

A unified porting guide for collections which have opted-in is available
here:

https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_6.html

Getting collection updates from Ansible 6 with older releases of
ansible-core

-

Ansible 6 includes ansible-core 2.13.x and users have expressed an interest in
getting collection updates as they ship in the Ansible "batteries included"
package while keeping an older version of ansible-core based on their needs
and requirements.

An ansible-galaxy requirements file based on the collections from

Ansible 6 has been made available for this use case:

https://github.com/ansible-community/ansible-build-data/blob/main/6/galaxy-requirements.yaml

Once the requirements file has been downloaded, the collections can be
installed
by running:

"ansible-galaxy collection install -r galaxy-requirements.yaml"

On behalf of the Ansible community, thank you and happy automating !

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAJm9AsQF8yFbzqt%2BHEVr1Cz-OLCGJ_UejxVb%2BWTov2mU1B_1bQ%40mail.gmail.com.

Re: [ansible-project] How do you keep your ansible collections and roles from the galaxy current ?

[John Petro]

If I am understanding the requirement here.   You want to be able to grab a
specific version of a role or collection for some reason.If that is
what you are asking for, then what about cloning the collection or role to
a personal git repository.

--John

On Wed, Jun 1, 2022 at 3:30 AM Norbert Klamann <
norbert.klam...@klamann-software.de> wrote:

> Hallo all,
> what is the best way to keep the ansible collections and roles current
> which you use ?
>  I think about parsing the output of `ansible-galaxy role list` or
> `ansible-galaxy collection list` but this is not very elegant.
>
> I think I overlook a very simple solution, can somebody point me in the
> right directione, please ?
>
> Many thanks
>
> Norbert
>
>
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/df51ba2e-2900-4de3-ba1f-a4e625296003n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPAjob-Emi%3DTXm6yWragEU40ONyZp5dEw9X9aQWYraZef%2Bma5A%40mail.gmail.com.

Re: [ansible-project] Re: Ansible 2.9 Upstream Life Cycle Announcement

[Nico Kadel-Garcia]

Unfortunately, the update to "ansible 5" or "ansible 6" is a bit
fraught. It's *huge*, filled with roughly 100 modules, very few of
which are of any use whatsoever to most ansible servers. Most
developers will only need ansible-core, with only a very few ansible
galaxy modules if needed, which is much smaller. But getting there is
going to be awkward.

I do find myself wishing hte split of ansible to an
ansible_collections tarball mislabeled as "ansible" and the ansible
tarball with the critical executables and the ansible python modules
as "ansible-core" had been done exactly the other way around, it would
have made these upgrades much simpler.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAOCN9rxaz5r-5NyiMKiM_VNTaxi3wCfE3cN%3DBo2pC8Y6cqPccg%40mail.gmail.com.

Re: [ansible-project] Ansible 6.0.0b1 (including ansible-core 2.13) is available for testing

[Nico Kadel-Garcia]

On Fri, May 27, 2022 at 12:49 PM David Moreau Simard
 wrote:
>
> Hi all,
>
> We're happy to announce that the first beta release of Ansible 6.0 is
> now available for testing !
>
> Ansible 6.0.0 will include ansible-core 2.13 as well as a curated set of
> Ansible collections to provide a vast number of modules and plugins.

This is still not correct. ansible 6 requires ansible-core 2.13, which
is provided separately from the "ansible" package at pypi.org. The
"ansible" package is only a set of curated ansible collections.and
does not contail ansible-core, which is verifiable by looking at the
tarballs, or the relevant git repos, or installing them. There seems
to be some concept of an "ansible" installation that includes both but
it's not reflected in the code. There could easily be one: what is now
"ansible" could be more consistently published as
"ansible_collections", which is what it actually installs in a python
directory, and "ansible" could be a meta package with requirements of
"ansible-core" and the more correctly labeled "ansible_collections".
Please, consider straightening out this confusion in the next major
ansible release.

In any case, I've updated my https://github.com/nkadel/ansiblerepo
tools to build both packages as RPMs under RHEL 8 and RHEL 9. I've
expressed my concerns about ansible-core 2.13 and the jinja2
dependencies which make it so awkward to bundle for RHEL 8 or RHEL 9
separately: it blocks building the documentation RPMs for either
operating system because of the large dependency chain for the sphinx
needed for jinja2

I'm so far unaware of any feature of ansible 6 that actually requires
ansible-core 2.13 and will not interoperate well with ansible-core
2.12.6, and I've been divorcing ansible from high versioned
ansible-core dependencies. I'm aware that some modules have
imitations, with ansible-core versions, but they generally have
internal logic that handles this, and the ansible_collections
requirement thus seems no compelling reason to refuse compatibility
with a more easily packaged ansible-core 2.12.6, at least until RHEL 8
and RHEL 9 can get updated jinja2.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAOCN9rwTNfp7sVYcvQeO67s1VWZxuqM_b-2nd-kqht_1wWdMmQ%40mail.gmail.com.

Re: [ansible-project] How do you keep your ansible collections and roles from the galaxy current ?

[Nico Kadel-Garcia]

On Wed, Jun 1, 2022 at 3:30 AM Norbert Klamann
 wrote:
>
> Hallo all,
> what is the best way to keep the ansible collections and roles current which 
> you use ?
>  I think about parsing the output of `ansible-galaxy role list` or 
> `ansible-galaxy collection list` but this is not very elegant.
>
> I think I overlook a very simple solution, can somebody point me in the right 
> directione, please ?
>
> Many thanks
>
> Norbert

Why would you want to? Any, and all, of the modules, mostly third
party modules, can have ansible breaking updates without warning. An
annual or semi-annual review, with smoke tests, might work well. What
is wrong with "inelegant", especially when it avoids the half a
Gigabyte of local disk space that the modern and misnamed "ansible"
package provides? It's really "ansible_collections", the name is very
misleading, and the modern "ansible-core" package actually contains
the working ansible code from https://github.com/ansible/ansible/ and
installs the ansible modules.

If you'd like to double check the current bundled list for comparison,
you can compare them to
https://github.com/ansible-community/ansible-build-data/ config files,
which are used to generate the mislabeled "ansible" tarball.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAOCN9rxaaZ7f2r6CDYXbgCkCVuhb0oDi415zON7JNS6zsR4Ftw%40mail.gmail.com.

Re: [ansible-project] Exceptions with vmware_deploy_ovf module

[Dick Visser]

On Wed, 1 Jun 2022 at 02:46, Vichu  wrote:

> hello there,
>
> I am trying to automate the cloud director OVA deployment in our local
> lab. Built a playbook but caught up with the exception during the
> execution. Need your advice to unblock from this.
>
> *Error found:*
>
> An exception occurred during task execution. To see the full traceback,
> use -vvv. The error was: TypeError: For "valuepected type str, but got int
> fatal: [localhost -> localhost]: FAILED! => {"changed": false,
> "module_stderr": "Traceback (most recent call last):\n e
> \"/root/.ansible/tmp/ansible-tmp-1654025411.9694972-30359-230767769553477/AnsiballZ_vmware_deploy_ovf.py\",
> line 100 \n_ansiballz_main()\n  File
> \"/root/.ansible/tmp/ansible-tmp-1654025411.9694972-30359-230767769553477/AnslZ_vmware_deploy_ovf.py\",
> line 92, in _ansiballz_main\ninvoke_module(zipped_mod, temp_path,
> ANSIBALLZ_PARAMS)\n
> \"/root/.ansible/tmp/ansible-tmp-1654025411.9694972-30359-230767769553477/AnsiballZ_vmware_deploy_ovf.py\",
> line 41, nvoke_module\nrun_name='__main__', alter_sys=True)\n  File
> \"/usr/lib64/python3.6/runpy.py\", line 205, in run_modnreturn
> _run_module_code(code, init_globals, run_name, mod_spec)\n  File
> \"/usr/lib64/python3.6/runpy.py\", line 9n _run_module_code\nmod_name,
> mod_spec, pkg_name, script_name)\n  File \"/usr/lib64/python3.6/runpy.py\",
> line 85,_run_code\nexec(code, run_globals)\n  File
> \"/tmp/ansible_vmware_deploy_ovf_payload_r7j_7pzv/ansible_vmware_deploy_payload.zip/ansible_collections/community/vmware/plugins/modules/vmware_deploy_ovf.py\",
> line 755, in \n
>  
> Fil/tmp/ansible_vmware_deploy_ovf_payload_r7j_7pzv/ansible_vmware_deploy_ovf_payload.zip/ansible_collections/community/vm/plugins/modules/vmware_deploy_ovf.py\",
> line 743, in main\n  File
> \"/tmp/ansible_vmware_deploy_ovf_payload_r7j_7pzv/ale_vmware_deploy_ovf_payload.zip/ansible_collections/community/vmware/plugins/modules/vmware_deploy_ovf.py\",
> line 530 upload\n  File
> \"/tmp/ansible_vmware_deploy_ovf_payload_r7j_7pzv/ansible_vmware_deploy_ovf_payload.zip/ansible_collecs/community/vmware/plugins/modules/vmware_deploy_ovf.py\",
> line 443, in get_lease\n  File
> \"/usr/local/lib/python3.6/spackages/pyVmomi/VmomiSupport.py\", line 663,
> in __setattr__\nCheckField(self._GetPropertyInfo(name), val)\n
>  Fileusr/local/lib/python3.6/site-packages/pyVmomi/VmomiSupport.py\", line
> 1098, in CheckField\n% (info.name, info.typeame__,
> valType.__name__))\nTypeError: For \"value\" expected type str, but got
> int\n", "module_stdout": "", "msg": "MO FAILURE\nSee stdout/stderr for the
> exact error", "rc": 1}
>
> *Environment Detail:*
> PackageVersion
> -- --
> ansible2.9.0
> asn1crypto 1.3.0
> certifi2019.11.28
> cffi   1.13.2
> chardet3.0.4
> charset-normalizer 2.0.12
> cryptography   2.8
> dnspython  1.16.0
> idna   2.8
> Jinja2 2.10.3
> jmespath   0.9.4
> lxml   4.4.2
> MarkupSafe 1.1.1
> pip21.3.1
> pycparser  2.19
> pyvmomi7.0.3
> PyYAML 5.3
> requests   2.22.0
> setuptools 39.2.0
> six1.13.0
> urllib31.25.7
>
> *Here is my play book:*
>
> vmware_deploy_ovf:
>   hostname: "{{ vcenter_hostname }}"
>   username: "{{ vcenter_username }}"
>   password: "{{ vcenter_password }}"
>   validate_certs: "{{ ova_validate_certs }}"
>   name: Auto-VCD-10.3.1
>   datacenter: "{{ vcenter_default_datacenter }}"
>   cluster: "{{ vcenter_default_cluster }}"
>   datastore: nfs-ds
>   disk_provisioning: thin
>   networks:
> "Network 1": "VM Network"
> #"Network 2": "Network78"
>   ova: /OVA/VMware_Cloud_Director.ova
>   allow_duplicates: no
>   power_on: yes
>   fail_on_spec_warnings: yes
>   wait: yes
>   wait_for_ip_address: yes
>   inject_ovf_env: yes
>   properties:
> vami.DNS.VMware_vCloud_Director: "{{ dns_server }}"
> vami.domain.VMware_vCloud_Director: "{{ domain name"
>

There are missing brackets here




> vami.gateway.VMware_vCloud_Director:  "{{ gateway }}"
> vami.ip0.VMware_vCloud_Director: "{{ ip0address }}"
> vami.ip1.VMware_vCloud_Director: "{{ ip1address }}"
> vami.netmask0.VMware_vCloud_Director: "{{ netmask }}"
> vami.netmask1.VMware_vCloud_Director: "{{ netmask }}"
> vami.searchpath.VMware_vCloud_Director: "{{ default_domain }}"
> vcloudapp.varoot-password.VMware_vCloud_Director: "{{ root-passwd
> }}"
> vcloudconf.admin_fname.VMware_vCloud_Director: admin
> vcloudconf.admin_pwd.VMware_vCloud_Director: "{{ passwd }}"
> vcloudconf.admin_uname.VMware_vCloud_Director: administrator
> vcloudconf.ceip_enabled.VMware_vCloud_Director: True
> 

[ansible-project] How do you keep your ansible collections and roles from the galaxy current ?

[Norbert Klamann]

Hallo all,
what is the best way to keep the ansible collections and roles current 
which you use ?
 I think about parsing the output of `ansible-galaxy role list` or 
`ansible-galaxy collection list` but this is not very elegant.

I think I overlook a very simple solution, can somebody point me in the 
right directione, please ?

Many thanks

Norbert



-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/df51ba2e-2900-4de3-ba1f-a4e625296003n%40googlegroups.com.