cloud engineer
Here’s how to move a VM to another network.
Stop the VM.
gcloud compute instances stop server-name \ --zone=us-central1-c \ --project project-id |
gcloud compute instances stop server-name \ --zone=us-central1-c \ --project project-id
Migrate the VM. Use self link for network and subnetwork.
gcloud compute instances network-interfaces update server-name \ --zone=us-central1-c \ --network-interface=nic0 \ --network=your-network \ --subnetwork=your-sub-network \ --project project-id |
gcloud compute instances network-interfaces update server-name \ --zone=us-central1-c \ --network-interface=nic0 \ --network=your-network \ --subnetwork=your-sub-network \ --project project-id
Start the VM.
gcloud compute instances start server-name \ --zone=us-central1-c \ --project project-id |
gcloud compute instances start server-name \ --zone=us-central1-c \ --project project-id
There are a few issues that prop up every once in a while with gcloud compute ssh. gcloud compute ssh creates local user at first login. The account password has a default expiration of 90 days. If unable to login, you can try logging in as a different name (even a fictitious name) e.g. superheroes, etc. something unique.
gcloud compute ssh username@servername --zone us-central1-c --project project-id --internal-ip |
gcloud compute ssh username@servername --zone us-central1-c --project project-id --internal-ip
Once logged in, you can delete local users with expired passwords or perform other admin tasks.
userdel -r username |
userdel -r username
You can also try to run chage to adjust the password expiration.
chage -M 180 username (extends expiration from 90 to 180 days) |
chage -M 180 username (extends expiration from 90 to 180 days)
If you continue to have login issues, you can also delete Metadata SSH keys in both the instance and project levels.
Last resort you can use force key overwrite which will regenerate a new key and overwrite broken ssh keys.
gcloud compute ssh username@servername \ --force-key-file-overwrite \ --zone us-central1-c \ --project project-id \ --internal-ip |
gcloud compute ssh username@servername \ --force-key-file-overwrite \ --zone us-central1-c \ --project project-id \ --internal-ip
There’s a new beta command to rename a GCP VM.
You must stop instance first.
gcloud compute instances stop server-name \ --zone us-central1-c \ --project your-project-id |
gcloud compute instances stop server-name \ --zone us-central1-c \ --project your-project-id
Rename the instance.
gcloud beta compute instances set-name old-server-name \ --new-name=new-server-name \ --zone us-central1-c \ --project your-project-id |
gcloud beta compute instances set-name old-server-name \ --new-name=new-server-name \ --zone us-central1-c \ --project your-project-id
Start the instance.
gcloud compute instances start server-name \ --zone us-central1-c \ --project your-project-id |
gcloud compute instances start server-name \ --zone us-central1-c \ --project your-project-id
Login.
gcloud compute ssh server-name \ --zone us-central1-c \ --project your-project-id \ --internal-ip & |
gcloud compute ssh server-name \ --zone us-central1-c \ --project your-project-id \ --internal-ip &