Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added module for managing password expiration for root user #1833

Conversation

valentinJonev
Copy link
Contributor

SUMMARY

Added a new module for managing password expiration for root user of vCSA appliance

ISSUE TYPE
  • New Module Pull Request
COMPONENT NAME

vcenter_root_password_expiration

ADDITIONAL INFORMATION

@ihumster
Copy link
Collaborator

@valentinJonev Hello, Valentin. For work with vcenter rest api community.vmware modules use module_utils.vmware_rest_client. It would be nice to stick to common patterns when building the modules of this collection. See how vmware_content_library_manager.py is built for an example.

@mariolenz
Copy link
Collaborator

I'm not sure if vmware.vmware_rest is a good place to to implement new features:

We have no one on the team today who has any significant VMware knowledge or experience. In part because of this and also just generally given the team's current roadmap priorities we've paused feature development on the vmware.vmware_rest collection.

#1746

Actually, I was thinking about taking over this collection- that is moving the modules to community.vmware... but those modules are generated and I don't understand how they do it (yet).

BTW I think some modules already use the REST API because they provide features the SOAP API doesn't support.

cc @jillr

@ihumster
Copy link
Collaborator

@mariolenz Mario, I did not mean the vmware.vmware_rest collection (by the way, it is built using another project - ansible_content_builder). I'm talking about the fact that in this collection, work with rest methods is implemented by the general VmwareRestClient class from module_utils/vmware_rest_client.py

@mariolenz
Copy link
Collaborator

@ihumster Sorry, you're right. Of course, using module_utils.vmware_rest_client would be better!

@jillr
Copy link
Contributor

jillr commented Aug 30, 2023

Actually, I was thinking about taking over this collection- that is moving the modules to community.vmware... but those modules are generated and I don't understand how they do it (yet).

@mariolenz Can we help you with understanding or better documenting what the generator is doing, or how it's designed? We would be happy to take contributions to that collection. (You can certainly fork the modules, but it would be nice to have any fixes or new features for the modules all in one place.)

@valentinJonev
Copy link
Contributor Author

@ihumster I updated the module to use the API client from the module_utils.vmware_rest_client. If you have further suggestions, please let me know

@mariolenz
Copy link
Collaborator

recheck

@mariolenz
Copy link
Collaborator

Actually, I was thinking about taking over this collection- that is moving the modules to community.vmware... but those modules are generated and I don't understand how they do it (yet).

@mariolenz Can we help you with understanding or better documenting what the generator is doing, or how it's designed? We would be happy to take contributions to that collection. (You can certainly fork the modules, but it would be nice to have any fixes or new features for the modules all in one place.)

I think this is a bit off-topic here. I've created ansible-collections/vmware.vmware_rest#423 to discuss this.

cc @ihumster in case you're interested

@valentinJonev
Copy link
Contributor Author

valentinJonev commented Sep 2, 2023

Any idea why the build is failing?

@valentinJonev
Copy link
Contributor Author

Checks pass, so should be ready for merging?

@valentinJonev
Copy link
Contributor Author

Ok, but why are the checks failing without a useful message?

@mariolenz
Copy link
Collaborator

Ok, but why are the checks failing without a useful message?

I'm not sure what you mean "without a useful message". Do you know that the build results link to the job outcome? For example, the last (failed) run of ansible-test-cloud-integration-vcenter7_1esxi-stable215_2_of_2 states:

Failed to fetch logbundle from https://esxi1.test/cgi-bin/vm-support.cgi?manifests=System:Base&System:CoreDumps&System:EsxImage&System:IOFilter&System:LoadESX&System:Modules&System:RDMA&System:ResourceGroups&System:TPM&System:VFlash&System:VMTools&System:VmiofPlugins&System:ntp&System:uwstats&Fcd:Catalog&VirtualMachines:CoreDumps&VirtualMachines:VirtualMachineStats&VirtualMachines:base&VirtualMachines:base&VirtualMachines:diskinfo&VirtualMachines:logs&Storage:FCoE&Storage:Multipathing&Storage:NAS&Storage:VSAN&Storage:VSANHealth&Storage:VSANIscsiTarget&Storage:VSANPerfStats&Storage:VSANPerfSvc&Storage:VSANTraces&Storage:VVOL&Storage:base&Storage:iodm&Storage:iscsi&FeatureStateSwitch:FeatureStateSwitch&Userworld:HostAgent&Userworld:ProcessInformation&Configuration:System&Logs:System&hostProfiles:SystemImageCacheHostProfile&hostProfiles:hostProfiles&FileSystem:VMFSDiskDump&FileSystem:base&ActiveDirectory:base&CIM:base&Hardware:base&Hardware:usb&Installer:base&Network:base&Network:dvs&Network:lacp&Network:nscd&Network:tcpip&IntegrityChecks:md5sums: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:2546)

In the run before, ansible-test-cloud-integration-vcenter7_1esxi-stable215_1_of_2 fails with:

Failed to add host to vCenter 'vcenter.test' : ('An error occurred while communicating with the remote host.', None)

At least, it's a message... not sure if you consider it useful 🤷

This looks like a problem inside the CI pipeline itself to me, not anything to do with your code.

@valentinJonev
Copy link
Contributor Author

@mariolenz the build is failing because there is a problem in the code (or so I think) Last time the build failed and then the GitHub checks were ran I saw a couple of things the sanity check was complaining, I fixed them and then he build succeeded.
So my thought was that the build was failing due to some sanity checks failing and then the messages say nothing about the code?

@mariolenz
Copy link
Collaborator

recheck

@mariolenz
Copy link
Collaborator

@valentinJonev It looks like the sanity tests succeed now 😄

The integration tests still have a problem. But there are no integration tests using your code (yet), so this has to be some problem in the CI pipeline and not with your code.

@mariolenz
Copy link
Collaborator

recheck

Copy link
Collaborator

@mariolenz mariolenz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really sure about everything, but let's merge it now that the CI succeeded.

Thanks @valentinJonev and also thanks for your patience!

@softwarefactory-project-zuul
Copy link

Build succeeded (gate pipeline).
https://ansible.softwarefactory-project.io/zuul/buildset/94d771f21e83451b82c33638b7a474da

✔️ ansible-tox-linters SUCCESS in 8m 27s
✔️ build-ansible-collection SUCCESS in 7m 33s
✔️ ansible-galaxy-importer SUCCESS in 11m 56s

@softwarefactory-project-zuul softwarefactory-project-zuul bot merged commit c7b1f59 into ansible-collections:main Sep 12, 2023
10 checks passed
softwarefactory-project-zuul bot pushed a commit that referenced this pull request Sep 13, 2023
meta/runtime.yml: Add missing modules

SUMMARY
Add missing modules to meta/runtime.yml.
ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME
runtime.yml
ADDITIONAL INFORMATION
#1806
#1833
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants