OsLoginRpcException - Username is not POSIX compliant error - os-login

Hello,

I am trying to learn and use compute engine.

I added a ssh key to os-login, and was able to log in to a newly created debian instance with my owner account.

On the shell command line the "tab" key was very slow.

I dug deeper, eventually sniffing traffic on port 80 with "tcpdump -A port 80"

My typing "tab" triggered the below http request that eventually timed out.

Please let me know if you know what is happening, and what I may have configured wrong.

Thanks very much.

GET /computeMetadata/v1/oslogin/users?username=%2A HTTP/1.1
Host: 169.254.169.254
Accept: */*
Metadata-Flavor: Google

HTTP/1.1 400 Bad Request
Metadata-Flavor: Google
Date: Tue, 14 May 2024 03:23:42 GMT
Content-Type: text/html
Server: Metadata Server for VM
Content-Length: 290
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN

[ReqId=6186187641B96.A9BF166.74045544] Error Details: Username is not POSIX compliant.
com.google.cloud.oslogin.exceptions.OsLoginRpcException: <eye3 title='INVALID_ARGUMENT'/> generic::INVALID_ARGUMENT: [ReqId=6186187641B96.A9BF166.74045544] Error Details: Username is not POSIX compliant.

3 3 73
3 REPLIES 3

A similar issue with a new debian instance and tab being slow (only as user, not as root).

I was running debugging with `strace` and noticed the same call to the metadata server with empty username.   The same metadata call is present on a working debian instance with similar failure but the difference is that the tab-slow debian calls the metadata server multiple times before timeout.

As the deployments are through code with identical configuration, a bit puzzled what is causing it..

Did a bit of testing..

Looks like the latest debian-12-bookworm-v20240515 has it, replaced the VM with debian-12-bookworm-v20240312 and it works just fine.

debian-12-bookworm-v20240415 has the issue as well.