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
vmware_guest: Cloning with disk customization fails #57817
Comments
Current workaround is changing the template's disk from non-persistent to persistent THEN cloning it. Edit: mentioned that it used to work on 2.7 |
I'll try to reproduce this issue in my env if there is no one else working on it. Thanks. |
getting similar behavior, though without specifying persistent disk_mode for cloned vm. with the below it fails with:
|
removing the fileOperation seems to do the trick under Asnible 2.8.1 vmware_guest.py:
|
resolved_by_pr #58737 |
Closing this issue as PR #58737 is merged. If issue persists, please feel free to open a new issue. |
SUMMARY
Cloning from a template that has disk set to non-persistent fails when the disk for the new machine is set to persistent.
ISSUE TYPE
COMPONENT NAME
vmware_guest
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
Target:
debian 7,8,9
centos 6,7
Controlled:
debian 9
STEPS TO REPRODUCE
Step 1:
Set a machine/template's disk to non-persistent
Step 2:
Create machine wish disk set to persistent
EXPECTED RESULTS
Machine created without issues
ACTUAL RESULTS
task fails with the following message below
This used to work perfectly fine before 2.8.0.
I didn't see any major changes as per the changelog concerning vmware_guest/disk but I did find these commits: 8eff4ca and 7c8b5a4
These are the only commits I found regarding disks/2.8 that might be causing this.
The text was updated successfully, but these errors were encountered: