Comments (15)
luischanu
commented on May 29, 2024
Hello @na2626,
I am guessing that you are using outdated VMware vSphere Ansible module versions. When we upgraded to newer modules, I recall that an argument was no longer needed, so it was removed. This should be documented in the CHANGELOG.md file regarding that change. Regardless, I believe if you upgrade you're modules, the issue should resolve. See the README for steps on upgrading all of your modules to the current versions.
from sddc.lab.
commented on May 29, 2024
Hello Luis,
Thanks for your reply. I updated modules
* Install the required software on your Ansible controller:
* ```sudo apt update```
* ```sudo apt install python3 python3-pip python-is-python3 xorriso git```
* ```git clone https://github.com/rutgerblom/SDDC.Lab.git ~/git/SDDC.Lab```
* ```pip3 install --upgrade -r ~/git/SDDC.Lab/pip3_requirements.txt```
* Update your PATH environment variable by doing the following:
* Logout of your Ansible controller
* Login to your Ansible controller
* Install Ansible collections on your Ansible controller:
* ```ansible-galaxy collection install --upgrade -r ~/git/SDDC.Lab/requirements.yml```
On both my ubuntu VM but the result is the same.
Thanks for your help
… On 17 Oct 2022, at 20:18, Luis Chanu ***@***.***> wrote:
Hello @na2626 <https://github.com/na2626>,
I am guessing that you are using outdated VMware vSphere Ansible module versions. When we upgraded to newer modules, I recall that an argument was no longer needed, so it was removed. This should be documented in the CHANGELOG.md file regarding that change. Regardless, I believe if you upgrade you're modules, the issue should resolve. See the README for steps on upgrading all of your modules to the current versions.
—
Reply to this email directly, view it on GitHub <#314 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AU7FYU6DXQGOHQLKN3WM2DLWDWKA5ANCNFSM6AAAAAARHALNRA>.
You are receiving this because you were mentioned.
from sddc.lab.
rutgerblom
commented on May 29, 2024
Hello @na2626,
Could you share the output of the following commands:
pip3 list | grep vSphere-Automation-SDK
ansible --version
ansible-galaxy collection list community.vmware
Thanks.
from sddc.lab.
commented on May 29, 2024
Hello Rutger,
Here’s the output:
➜ ~ pip3 list | grep vSphere-Automation-SDK
vSphere-Automation-SDK 1.79.0
➜ ~ ansible --version
ansible [core 2.13.5]
config file = None
configured module search path = ['/home/labadmin/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/labadmin/.local/lib/python3.10/site-packages/ansible
ansible collection location = /home/labadmin/.ansible/collections:/usr/share/ansible/collections
executable location = /home/labadmin/.local/bin/ansible
python version = 3.10.6 (main, Aug 10 2022, 11:40:04) [GCC 11.3.0]
jinja version = 3.0.3
libyaml = True
➜ ~ ansible-galaxy collection list community.vmware
# /home/labadmin/.ansible/collections/ansible_collections
Collection Version
---------------- -------
community.vmware 3.0.0
# /home/labadmin/.local/lib/python3.10/site-packages/ansible_collections
Collection Version
---------------- -------
community.vmware 2.10.0
Thanks
… On 17 Oct 2022, at 21:51, Rutger Blom ***@***.***> wrote:
Hello @na2626 <https://github.com/na2626>,
Could you share the output of the following commands:
pip3 list | grep vSphere-Automation-SDK
ansible --version
ansible-galaxy collection list community.vmware
Thanks.
—
Reply to this email directly, view it on GitHub <#314 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AU7FYU7DI4GOOJGSWOT2CA3WDWU5NANCNFSM6AAAAAARHALNRA>.
You are receiving this because you were mentioned.
from sddc.lab.
luischanu
commented on May 29, 2024
@na2626 ,
Not related to your issue, but you might want to upgrade your Jinja, as I noticed some slight speed increases with the newer version. Just thought I'd mention that as a FYI.
from sddc.lab.
commented on May 29, 2024
Thanks Luis, latest jinja2 3.1.2 will be ok?
… On 17 Oct 2022, at 22:30, Luis Chanu ***@***.***> wrote:
@na2626 <https://github.com/na2626> ,
Not related to your issue, but you might want to upgrade your Jinja, as I noticed some slight speed increases with the newer version. Just thought I'd mention that as a FYI.
—
Reply to this email directly, view it on GitHub <#314 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AU7FYU5MGXABBEEXJTY4C73WDWZPLANCNFSM6AAAAAARHALNRA>.
You are receiving this because you were mentioned.
from sddc.lab.
luischanu
commented on May 29, 2024
Yes...that's the version of Jinja that I am running.
from sddc.lab.
luischanu
commented on May 29, 2024
@na2626 , when you stated "Also tried to create two "fresh" ubuntu (22.04 and 20.04) VMs but the result is always the same.", I'm assuming that you the two newly built Ubuntu boxes you're referencing are for your Ansible controller, and not Ubuntu workloads (i.e. DNS server) that you're trying to deploy via SDDC.Lab. Can you confirm that is what you mean?
FYI, about a month ago I built a new Ansible controller (v22.04) to test out the installation instructions in the README file, and I didn't have any issues. Everything worked as expected, and I was able to deploy a Pod. I already had my SDDC.Lab DNS server in place and working, and all I provisioned was the Ansible controller.
from sddc.lab.
commented on May 29, 2024
Yes, I’m referencing ansible controller. Also I also have dns server in place from previous deploy Inviato da iPhoneIl giorno 18 ott 2022, alle ore 03:49, Luis Chanu ***@***.***> ha scritto:
@na2626 , when you stated "Also tried to create two "fresh" ubuntu (22.04 and 20.04) VMs but the result is always the same.", I'm assuming that you the two newly built Ubuntu boxes you're referencing are for your Ansible controller, and not Ubuntu workloads (i.e. DNS server) that you're trying to deploy via SDDC.Lab. Can you confirm that is what you mean?
FYI, about a month ago I built a new Ansible controller (v22.04) to test out the installation instructions in the README file, and I didn't have any issues. Everything worked as expected, and I was able to deploy a Pod. I already had my SDDC.Lab DNS server in place and working, and all I provisioned was the Ansible controller.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
from sddc.lab.
rutgerblom
commented on May 29, 2024
Thanks @na2626 for providing the output. There seems to be some kind of issue or change with the latest community.vmware collection (version 3.0.0).
While we investigate how to solve this you can implement a workaround by downgrading the community.vmware collection to version 2.9.1 which we know is working:
ansible-galaxy collection install community.vmware:==2.9.1
Let us know if this solves the problem for you.
from sddc.lab.
commented on May 29, 2024
Thanks Rutger! This seems to solve the issue but now I see that the vyos config isn’t copied and the subsequent phases fail. On vyos only the eth0 (uplink) ip is configured.
… On 18 Oct 2022, at 09:37, Rutger Blom ***@***.***> wrote:
Thanks @na2626 <https://github.com/na2626> for providing the output. There seems to be some kind of issue or change with the latest community.vmware collection (version 3.0.0).
While we investigate how to solve this you can implement a workaround by downgrading the community.vmware collection to version 2.9.1 which we know is working:
ansible-galaxy collection install community.vmware:==2.9.1
Let us know if this solves the problem for you.
—
Reply to this email directly, view it on GitHub <#314 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AU7FYU3QPM7UWI7U3KHCNGTWDZHSHANCNFSM6AAAAAARHALNRA>.
You are receiving this because you were mentioned.
from sddc.lab.
luischanu
commented on May 29, 2024
@na2626, did you read through the "Upgrade Considerations" section in the README file for "v4 to v5", and follow the VyOS instructions listed there?
I just tested the LATEST build of VyOS, and it worked just fine. Please see the "Upgrade Considerations" section mentioned above.
If you have, and are still having issues, please open a new Issue for the VyOS issue. Thanks!
from sddc.lab.
luischanu
commented on May 29, 2024
@na2626, there appears to be something up with the router configuration. When I manually tested it last night, it worked, but in a recent deployment, the configuration doesn't apply. I just wanted to let you know. I'm looking into it. As this thread open issue is about the vDS Port-Group, I will not be responding any more on this here. Keep an eye out in the CHANGELOG, or, open another issue for the VyOS Pod-Router not getting configured, and we can continue the discussion there. Thank you!
from sddc.lab.
luischanu
commented on May 29, 2024
@na2626, found issue with latest VyOS module (v4.0.0) released 5 days ago. Revert back to v3.0.1, and problem is solved. See CHANGELOG.md in 'dev-v6' branch for details. Considering this issue resolved.
from sddc.lab.
commented on May 29, 2024
Thank you very much Rutger & Luis, you're doing a really good job with this project!
from sddc.lab.
Related Issues (20)
- Issue in updateDNS.yml for PTR record creation HOT 1
- nsupdate errors
- BGP to external router instead of OSPF HOT 4
- Update to support vSphere 7.0 U2 HOT 2
- Depoly Ubuntu VM Step for DNS VM fails HOT 3
- Cannot fetch ISO from Directory Structure HOT 2
- Error deploying Ubuntu HOT 3
- Deployment of DNS Server fails HOT 3
- deploy additional hosts HOT 2
- Only version of NSX 4 on VMUG isn't listed in software.yml for dev-v6 HOT 4
- Add check to /playbooks/ValidateConfiguration.yml that verifies a content library with {{ PublishedLibraryName }} exists.
- If deploying pod with vSphere 8 do not create "Pod-XXX TKG Content Library"
- Add reverse DNS zone for 10.204.0.0/16 to SDDC-Lab-DNS
- Investigate if MAC Learning (VDS v8) is something that can be used
- VMs connected to VMNetwork receive IP address from wrong scope
- Test
- ALB will not successfully deploy without content library HOT 7
- Playbook Util_CreateSoftwareDir.yml failing. HOT 2
- DNS Failing HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sddc.lab.