resmo edited a comment on issue #3934: URL: https://github.com/apache/cloudstack/issues/3934#issuecomment-698743047
I see this with in 4.13.1 note the zone that changes from basic to advance from first test to second test. https://github.com/ngine-io/ansible-collection-cloudstack/pull/40/checks?check_run_id=1162936780#step:6:3610 ``` TASK [cs_vmsnapshot : test revert snapshot] ************************************ changed: [testhost] => {"account": "admin", "api_http_method": "get", "api_key": "DL3Be8XtxsrKJOMRIIPR_2LUdknE5n8V33u41NWaetVcnKAQTeQhkDDVKAJCIyHV1I4fY3Phw8B49BpSnfLKtg", "api_region": "cloudstack", "api_timeout": 60, "api_url": "http://cloudstack-sim:8888/client/api";, "api_verify_ssl_cert": null, "changed": true, "created": "2020-09-24T22:12:33+0000", "current": true, "display_name": "ansible-test-fv-az176-89231118_snapshot", "domain": "ROOT", "id": "230bab25-dcd6-4641-97c5-79396730eef6", "name": "i-2-12-QA_VS_20200924221233", "state": "Ready", "tags": [], "type": "DiskAndMemory", "zone": "Sandbox-simulator-basic"} TASK [cs_vmsnapshot : verify test revert snapshot] ***************************** ok: [testhost] => { "changed": false, "msg": "All assertions passed" } TASK [cs_vmsnapshot : test remove snapshot in check mode] ********************** fatal: [testhost]: FAILED! => {"api_http_method": "get", "api_key": "DL3Be8XtxsrKJOMRIIPR_2LUdknE5n8V33u41NWaetVcnKAQTeQhkDDVKAJCIyHV1I4fY3Phw8B49BpSnfLKtg", "api_region": "cloudstack", "api_timeout": 60, "api_url": "http://cloudstack-sim:8888/client/api";, "api_verify_ssl_cert": null, "changed": false, "msg": "Virtual machine 'ansible-test-fv-az176-89231118-vm-snapshot' not found", "zone": "Sandbox-simulator-advanced"} ``` this is the code for the zone selection: https://github.com/ngine-io/ansible-collection-cloudstack/blob/master/plugins/module_utils/cloudstack.py#L467 If this is a wanted behavior, what is the correct way to select the default zone? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
