IssueTracker

Thanks for your report. Can you share your deployment config file to reproduce and investigate this issue further?

These are the steps to recreate the issue:

Create a deployment config file:
pddisk.yml:

resources:
  - name: my-persistent-disk
    type: compute.v1.disk
    properties:
      zone: europe-west1-b
      sizeGb: "10"

Create a deployment:
gcloud deployment-manager deployments create pddisk --config pdisk.yml

It completes successfully.

Change sizeGb in pddisk.yml from 10 to 20 and update the deployment:

gcloud deployment-manager deployments update pddisk --config pdisk.yml

It fails with:

- code: NO_METHOD_TO_UPDATE_FIELD
  message: No method found to update field 'sizeGb' on resource 'my-persistent-disk'
    of type 'compute.v1.disk'. The resource may need to be recreated with the new
    field.

Note that increasing disk size from cloud console or via gcloud works correctly.

Thanks for providing additional information.

We currently have an existing feature request to support disk resize using deployment manager. The engineering team is already working to push the updates and this feature should be available soon. We will update this thread with any progress updates and a resolution.

This feature is available now, you will be able to change the disk size using deployment manager.

I can confirm it works now - thank you!

I'm glad to know this works, thanks for the confirmation.

Are there situations when this doesn't work?  I still get the message:

- code: NO_METHOD_TO_UPDATE_FIELD
  message: No method found to update field 'sizeGb' on resource 'instance-secondary-ssd'
    of type 'compute.v1.disks'. The resource may need to be recreated with the new
    field.

I have to abandon the resources, resize the disk manually and reacquire the resources to get the new disk sizes at present.

I just abandoned the instance and associated disk, resized manually, reacquired the instance and unchanged and resized disks.  Then I tried to run deployment manager again with a change of disk size only to get the same issue as above.  My reasoning was that if it was somehow that the configuration of the disk was old and predated the change in API then maybe when on acquiring it again it would have the ability to resize.  Nope, so I have no idea what the issue is.