Status Update
No update yet.
Comments
dh...@google.com
dh...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Please mention the steps to be followed for reproducing the issue with the given sample apk.
Android full bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory.
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen record of the issue, for clarity
Please capture screen record or video of the issue using the following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4\
Note: Please upload the files to google drive and share the folder to
Description
Regional disks don't support building from images, yet zonal disks do.
1. This resource behaves differently then the google_compute_disk resource. This means we have to special case logic to handle the difference between the two. The only difference could be passing in additional zones, but since we can't pass the image we need an additional step.
2. The additional step requires provisioning after the resource is up. Without an image, we have an unusable disk. We have to then add a step after the VM is up that will format the disk to make it usable.
3. This then means that later steps of the process of bringing up a host means the knowledge of the disk type has to be propagated from Terraform to other systems. Because google_compute_disk already supports image, that ability in our systems doesn't exist, and then has to be created.
What you would like to accomplish:
I would like regional disks to support the same features as zonal disks as much as possible, including starting from an image.
How this might work:
The same way zonal disks already do. Pass an image in via the API, and have the disk initialize with that.
If applicable, reasons why alternative solutions are not sufficient:
See above for pain points.
Other information (workarounds you have tried, documentation consulted, etc):