Closed fmarinelli closed 6 years ago
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
@fmarinelli thanks for creating this issue. Are you using the upgrade-ops-manager pipeline for GCP, if so what version of the pipelines are you using? and where have you obtained it (via PivNet or GitHub (if GitHub, are you using a tag). Thanks.
Hello, yes I'm using upgrade-ops-manager pipeline for GCP and it's the master branch from github.
I've also tried the command directly from the shell.
Hi @fmarinelli the master branch is considered unstable since our engineers iterate on that branch. Could you download v23 from PivNet or use a tag on Github and try your pipeline again. I've added a caveat to the README. Thank you.
Hey again @fmarinelli we are working on a fix for the issue you've described. We hope to release the fix soon. Thanks for reporting the issue.
When launching cliaas with command replace-vm, it doesn't seem to use the disk size parameter and I end up with a new VM with only 5GB disk
To reproduce: cliaas-linux replace-vm \ --config cliaas-config/config.yml \ --identifier "identifier" \ --disk-size-gb "150"
---> cliaas-config/config.yml gcp: credfile: cliaas-config/gcpcreds.json zone: europe-west1-c project: fe-fmarinelli disk_image_url: ops-manager-eu/pcf-gcp-2.0-build.255.tar.gz