-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
"should become root" saving logic not right on fedora-coreos #20262
Labels
Comments
So digging into the test (TestUser.testExpire) it does:
So we could add a check that the bridge was really closed on def login_and_go(self, path: Optional[str] = None, user: Optional[str] = None, host: Optional[str] = None,
superuser: bool = True, urlroot: Optional[str] = None, tls: bool = False, password: Optional[str] = None,
legacy_authorized: Optional[bool] = None):
self.try_login(user, password, superuser=superuser, legacy_authorized=legacy_authorized) So by default we try to login as
If I change the test to
|
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When investigating an issue that only occurs on ostree-based images we noticed that logging in as admin, logging out, then logging in as a non-privileged user ("scruffy") is enough to trigger the issue, which is caused by a pending sudo operation. Removing the "admin" login part and the problem disappears.
My theory is that the login page is somehow changing its local storage behaviour of remember the "should be root" flag for the case where we are using the -ws container to connect to the host via ssh.
cc @jelly
The text was updated successfully, but these errors were encountered: