Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Databases other than /etc/{passwd,group} not considered when searching for etcd user/group #7655

Closed
bachorp opened this issue Feb 3, 2025 · 1 comment
Labels
kind/upstream-issue This issue appears to be caused by an upstream bug

Comments

@bachorp
Copy link

bachorp commented Feb 3, 2025

Environmental Info:
RKE2 Version: 2.31.5+rke2r1

Node(s) CPU architecture, OS, and Version: x86_64 EL9.4

Cluster Configuration: single node

Describe the bug:

RKE2

Steps To Reproduce:

  • Installed RKE2: Installation on a rhel-bootc node. Using RKE2 with profile: cis

Expected behavior:

User and group etcd are found.

Actual behavior:

rke2-server fails and reports missing etcd user and group.

Additional context / logs:

The library used here

etcdUser, err := user.Lookup("etcd")
will search only /etc/passwd and /etc/group (see https://go.dev/src/os/user/lookup.go). However, other user databases might be used (in my case /usr/lib/{passwd,group}. golang/go#38810 might be related.

@brandond
Copy link
Member

brandond commented Feb 3, 2025

Since this is an issue with the golang stdlib, not this project, I'm going to close it.

If the go stdlib ever changes the functionality of their user/group lookup functions it should be fixed - but this is not something we are looking to hand-roll at the moment.

We can update our documentation to mention that we inherit go's support for only traditional user/group lookups.

@brandond brandond closed this as completed Feb 3, 2025
@brandond brandond added the kind/upstream-issue This issue appears to be caused by an upstream bug label Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/upstream-issue This issue appears to be caused by an upstream bug
Projects
None yet
Development

No branches or pull requests

2 participants