Required 'compute.images.useReadOnly' permission for 'projects/webpagetest-official/global/images/wpt-linux-20200127'

[chandanpasunoori]

We are facing this issue in GCP instance group setup, instances are stuck from today morning.

Instance 'wpt-agent-xxxxx' creation failed: Required 'compute.images.useReadOnly' permission for 'projects/webpagetest-official/global/images/wpt-linux-20200127' (when acting as '[email protected]')

any directions, to solve this issue?

if we create our own images, where should we configure to use?

[jayaram250]

we are also facing the same issue "creation failed: Required 'compute.images.useReadOnly' permission"

[saurabh4sharma21]

Same issue facing since morning

[Roshithcomeon]

Same here. Has anyone found any work around?

[pmeenan]

Sorry, just saw this. The public GCE images were linked to a disk image that was in a personal account that no longer exists. It's a bit of a pain but you'll need to update your instance templates to point to an agent image that you create in your GCE account:

• Start an n1-standard-2 Ubuntu 18.04 image in your cloud console (SSD disk, 10GB, disk configured to not delete on instance termination)
• Once it is started, ssh to the instance through the cloud console
• At the terminal, paste and execute this command:

WPT_CLOUD=gce WPT_EPIPHANY=n bash <(curl -sL http://tiny.cc/wptagent)

• That will install all of the agent code identically to the original image and configure it to take the configuration settings from metadata
• When the script is done, shut down the instance sudo poweroff
• Delete the instance from the cloud console
• Once the instance delete has completed, go to images in the left nav and click "Create image" at the top. Give it a useful name and in the source, select disk and pick the disk image from your VM
• Refresh and wait for the image to finish being created.
• When the image is complete, go to instance templates and click on the instance template that was being used for your agents then click "create similar" in the header nav.
• Give it a useful name and change the "Boot Disk" section and change it to use the disk image you just created.
• Then select create at the bottom and then refresh the instance template list. It should show the new template name as well as the image it is based on
• Now go to instance groups in the left nav and one at a time, go through each existing instance group.
  • Click on the group
  • Click "Rolling Update" in the top nav menu
  • Select the new instance template in the template dropdown
  • Click the update button
• Go back to the instance template list and delete the old template

This will get you an image that is used for the autoscaling that doesn't have any outside dependencies (other than updating the code from github and the browsers/os from apt).

[chandanpasunoori]

thanks for update @pmeenan, we ended up doing same thing, I followed steps from new documentation, to create agent image in our GCP project itself.

but here we have done completely new setup (server and workers), it got new UI.

what is the option for upgrading existing server to new version? so we can use old server with latest changes.

[pmeenan]

The servers should have been linked to the github repo and auto-updated every few hours. Sounds like that didn't happen.

If you ssh in to the server, go to /var/www/webpagetest and "git pull" it should update to the latest (or tell you why it can't if a local file was edited).

[chandanpasunoori]

@pmeenan some how git is in detached from HEAD, I didn't change anything in local after catchpoint/WebPageTest#1423 issue, and clearly remember that I did reset my changes and applied your fixes, it even got few updates after that, then looks like its stopped

below is git log

git log -2
commit d997e2095c73d0cc5097c71decf2b386ac7dcbf6 (HEAD)
Author: Patrick Meenan <[email protected]>
Date:   Fri Feb 19 16:11:20 2021 +0000

    SAML updates

commit 554510c3ae64bad8f37af9df58c3bf9ca6fddd1f
Author: Patrick Meenan <[email protected]>
Date:   Fri Feb 19 16:11:09 2021 +0000

    Change the git update to pull whatever branch is checked out

after checking out to release branch, latest changes reflected.

probably others may also in same situation.