Spun up an alpha channel instance on OpenStack VM. On my first ssh login I see the the output below. I was able to spin up a x86_64 production channel instance and it didn't cause this failure.
The authenticity of host 'x.y.z (x.y.z)' can't be established.
ECDSA key fingerprint is SHA256:5EJ6tTTrX4zFLh25biRCk96MSFH.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'x.y.z' (ECDSA) to the list of known hosts.
Enter passphrase for key '/Users/bob/temp.key':
Flatcar Container Linux by Kinvolk alpha (2513.1.0)
Failed Units: 1
polkit.service
core@test ~ $ systemctl status polkit.service
● polkit.service - Authorization Manager
Loaded: loaded (/usr/lib/systemd/system/polkit.service; static; vendor preset: disabled)
Active: failed (Result: signal) since Thu 2020-07-16 23:38:15 UTC; 2min 0s ago
Docs: man:polkit(8)
Process: 860 ExecStart=/usr/lib/polkit-1/polkitd --no-debug (code=killed, signal=SEGV)
Main PID: 860 (code=killed, signal=SEGV)
Jul 16 23:38:15 localhost systemd[1]: Starting Authorization Manager...
Jul 16 23:38:15 localhost polkitd[860]: Started polkitd version 0.113
Jul 16 23:38:15 localhost systemd[1]: polkit.service: Main process exited, code=killed, status=11/SEGV
Jul 16 23:38:15 localhost systemd[1]: polkit.service: Failed with result 'signal'.
Jul 16 23:38:15 localhost systemd[1]: Failed to start Authorization Manager.
core@test ~ $ systemctl start polkit.service
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
^C
polkit.service is not starting up.
Impact
Not sure.
Environment and steps to reproduce
- Set-up: OpenStack VM, Alpha ARM64 Channel (Flatcar Container Linux by Kinvolk alpha (2513.1.0))
- Task: First ssh login/first boot
- Action(s): NA
- Error: See description above
Expected behavior
polkit.service should start up without failure.
Additional information
NA
Spun up an alpha channel instance on OpenStack VM. On my first ssh login I see the the output below. I was able to spin up a x86_64 production channel instance and it didn't cause this failure.
polkit.service is not starting up.
Impact
Not sure.
Environment and steps to reproduce
Expected behavior
polkit.service should start up without failure.
Additional information
NA