Assigned
Status Update
No update yet.
Comments
ka...@google.com
ka...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
ma...@sada.com
This is not only useful for IP addresses, but also for many other resources. I understand that names are currently used as identifiers, so this request is probably not trivial to implement. Maybe distinguishing between a (numeric, automatically generated) identifier and a (textual) label is the way to go?
bo...@google.com
Is it any hope? We have migrated our IP address to the server with different role, and now the name of this IP address resource doesn't match its role at all. It seems to be trivial enough to momentary reserve static IP address of the old named resource, drop resource, and immediately recreate it with the new name and the old IP address.
tm...@citystateentertainment.com
This would also improve life when using the Google Deployment Manager (since it otherwise error's out if you've changed a name of an IP)
bo...@google.com
Over 3 years to get something as basic as renaming a static IP address. Any progress here?
sa...@google.com
Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
Our clients have noticed an issue in how ssh-keys are being read. It appears that the method that the ssh-key is being read has changed for example
1) Unsername:ssh-rsa RSA-KEY-GOES-HERE DESKTOP-test-A\test example@DESKTOP-test-A
The format above was working and once the google google-guest-agent was updated it stopped.
`````
It appears that the newer version of google-guest-agent does not allow a space in the ssh key method and it now reads the ssh key as follows :
Username: "username"
RSA key: RSA-KEY-GOES-HERE DESKTOP-test-A\test
Expiration: example@DESKTOP-test-A
As you can see the space between test and example now is added in the expiration column
What you expected to happen:
To be able to keep on using the old ssh key format
Steps to reproduce:
You can create an ssh key and attempt to use a space as reported in the example above and you will notice the error. The google guest-agent versions are :
google-guest-agent=20201217.02-0ubuntu1~20.04.0, the upgraded version
google-guest-agent=20220622.00-0ubuntu2~20.04.2 is what's giving us trouble
Other information (workarounds you have tried, documentation consulted, etc):
A github code fix was published [1] to provide insights on how this issue can be resolved.
[1]