Bug 246298 - sysutils/google-compute-engine-oslogin: pw process freezes (cannot add user accounts)
Summary: sysutils/google-compute-engine-oslogin: pw process freezes (cannot add user a...
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: Normal Affects Many People
Assignee: freebsd-ports-bugs (Nobody)
URL: https://twitter.com/Terfex/status/125...
Keywords: needs-qa
Depends on:
Reported: 2020-05-08 03:56 UTC by Tom Foxwell
Modified: 2020-09-19 09:59 UTC (History)
3 users (show)

See Also:
koobs: merge-quarterly?

Pkg not installed in current GCP image but is available as an update after install (186.59 KB, image/png)
2020-05-08 03:56 UTC, Tom Foxwell
no flags Details
patch (9.79 KB, patch)
2020-09-19 09:59 UTC, Kurt Jaeger
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Foxwell 2020-05-08 03:56:34 UTC
Created attachment 214254 [details]
Pkg not installed in current GCP image but is available as an update after install

Deploying FreeBSD 12.1 from the GCP Marketplace on Google Compute Engine works fine with Guest Attributes enabled. Enabling OS login in Metadata causes the process in version 1.5.3_2 to repeatedly crash and subsequently Google OS login is does not allow login. 

Upgrading to 20191018.00 (https://svnweb.freebsd.org/ports?view=revision&revision=516443) resolves this initial issue. However when creating new accounts, after installing 20191018.00, the pw process will freeze and not complete. Further creation of user accounts is no longer possible even after removal of google-compute-engine-oslogin. Reinstallation of FreeBSD is required to resolve.

My last test was on 22/4/2020 using the below configuration:
Image: freebsd-12-1-release-amd64 (GCP)
OS: FreeBSD 12.1-p4
Platform: Google Cloud
Zone: australia-southeast1-b
Series: N1
Custom Meta
   enable-oslogin: TRUE
   enable-guest-attributes: TRUE

Other users have reported similar issues as noted on this Twitter thread https://twitter.com/Terfex/status/1252647247088504833?s=20

Also this package is now reporting it is no longer maintained and is due for removal.
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2020-05-08 08:37:25 UTC
Thank you for the report Tom

@Larry Are you able to help with this?
Comment 2 Kurt Jaeger freebsd_committer 2020-09-19 09:59:55 UTC
Created attachment 218070 [details]

This patch updates 20191018.00 to 20200918.00. Can you run-test if it works better for your use-case ?