Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions e2e-tests/tests/authd_disabled.robot
Original file line number Diff line number Diff line change
Expand Up @@ -19,12 +19,12 @@ ${username} %{E2E_USER}
Test that disabling authd prevents remote logins
[Documentation] This test verifies that when authd is disabled, remote users cannot log in, while local users can still access the system.

# Log in with local user
Log In

# Disable authd
Disable Authd Socket And Service

# Check that local user can still log in
Log In

# Ensure local sudo user can still log in
Open Terminal
Enter Sudo Mode In Terminal
Expand Down
6 changes: 3 additions & 3 deletions e2e-tests/tests/broker_disabled.robot
Original file line number Diff line number Diff line change
Expand Up @@ -19,12 +19,12 @@ ${username} %{E2E_USER}
Test that disabling broker prevents remote logins
[Documentation] This test verifies that when the broker is disabled, remote users cannot log in, while local users can still access the system.

# Log in with local user
Log In

# Disable broker
Disable Broker And Purge Config

# Check that local user can still log in
Log In

Comment on lines +25 to +27
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mmh, both "Authd Disabled" and "Broker Disabled" failed in some of the test runs when trying to close the terminal:

I don't recall seeing this failure mode before but I also don't see how it could be caused by this change. Can you make sense of it? If not, let's investigate the failure once we fixed the issue with the logs (https://warthogs.atlassian.net/browse/UDENG-9499).

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed the failures too, but it didn't look related to changes... Maybe it's due to machinectl? But then why the other tests are working? Could be a combination between machinectl and ptyxis

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's investigate once we have the complete logs

# Ensure local sudo user can still log in
Open Terminal
Enter Sudo Mode In Terminal
Expand Down
Loading