-
Notifications
You must be signed in to change notification settings - Fork 338
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
Use re.search for more flexibility in selecting a datastore #1793
base: main
Are you sure you want to change the base?
Use re.search for more flexibility in selecting a datastore #1793
Conversation
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 44s |
Hi @jillr @mariolenz I started getting merge conflicts on my other PR as community.vmware had moved on so I ended up closing that PR, refreshed everything, opened up this new PR. Looks like we are still seeing the node failures. I'll drop a note on the main thread where we have been working through this. Jill, thanks very much for continuing to poke the hosting service on getting this cleared up. I'll do occasional rechecks on this in case the node failures are transitory (I think Mario was indicating this may have been the case earlier). |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 9m 01s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 32s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 41s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 41s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 45s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 40s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 34s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 49s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 39s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 42s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 34s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 40s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 35s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 9m 02s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 45s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 9m 11s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 36s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 43s |
recheck |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 9m 32s |
Hi @mariolenz - do you know what the "ansible/gate" check is and why it's waiting for status to be reported? Is this the next hurdle in the CICD pipeline that's a bit "funky"? Or did I miss something dumb that's non-obvious to me. :) Thanks. |
@nikatbu The gate job is Zuul's merge job. When the PR is approved and ready to be merged it will get tagged with |
Hi @mariolenz what's the next step I should be doing here to get this PR approved? Is there some discussion thread I should be bringing this up on? Thanks. |
@nikatbu TBH I'm not sure if we should merge this. Regular expressions are really a nice tool, but I'm afraid this would open a can of worms and might lead to unforeseeable problems. |
Thanks @mariolenz, no worries, fair enough. Feel free to close/cancel if you think the risk of issues is not worth the benefit. |
SUMMARY
When finding the datastore(s) with autoselect_datastore, using re.search() provides more flexibility to match above what .find() substring matching can do.
ISSUE TYPE
COMPONENT NAME
vmware_guest.py autoselect_datastore functionality
ADDITIONAL INFORMATION
Swapped call ds.name.find() over to using re.search() to provide regex searching ability.