Maybe it’s a new feature of GCP, but it seems not possible to edit an instance inside a group anymore as suggested in the video (minute 7.24)
Hello, Stefano, and welcome to our forums! Thanks for reaching out.
I just tried doing this again, myself, and I am still able to edit the instances, so I’m trying to figure out what might be different for you.
One possibility is that the Google account that the console has somehow "latched onto" is different from the one that has access to the resources–that might make the console disable. To ensure that’s not happening, you can log into GCP in a brand new Incognito session. That’ll make sure that it only knows about the one Google account that you want to use.
Another thing you can do is to try to affect the instances via the command line, in Cloud Shell. If you go to Cloud Shell and run
gcloud compute instances delete xyz123instance, does it work? (Prompt or flag for zone notwithstanding.) The managed instance group should bring the instance right back, shortly, and it may even have the same name–but the
creationTimestamp visible in
gcloud compute instances describe xyz123instance will have changed. And then if you run
gcloud compute instances add-tags xyz123instance --tags=open-ssh-tag, (Thanks for the correction, Mathew!) does that add the network tag to the instance? I just tried these things and they worked for me.
Please let me know what you find, either way–whether this solves it or you’re still stuck!
Came against same issue as you guys, I didn’t know there was a discussion going on about this at first. Cheekily I removed the vm out of the group and edited the Tag. As it happens good old autoscaling was trying to add an instance into the group and everything went haywire. At the end I deleted the vm and let autoscaling add it. Finally resorted to follow your instructions on used gcloud and voila!!
I created a new using "Create similar" and added the tag there. This worked beautifully to illustrate the enabling of ssh. Editing of existing vm seems to be blocked/broken in the Console.
This shell command did work well and I greatly prefer that to the method I used, but just to post the alternate work around. I duplicated the Instance Template using the COPY, added the tag to the new template and then updated the Instance Group by doing a ROLLING UPDATE selecting the alternate template to re-provision the VMs.
I managed to get this working by deleting the VM through the console. Once it regenerated, I was then able to Edit. You could of course also do this through the CLI as described above.
I was able to fix the issue with the line
gcloud compute instances add-tags xyz123instance --tags=open-ssh-tag obviously just change "xyz123instance" for the name of your instance and it will work.
It is working fine if you use ZONE:
gcloud compute instances add-tags xxxxinstancenamexxx–zone=us-west1-b –tags=open-ssh-tag
Does anyone find out the reason why we cant edit the instance directly from the instance group? yes, of course, the command line would work but wondering the reason why it cannot be done through console…