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

Bug: unattended_upgrades api test has an unstated dependency of being connected to AC power #3308

Open
orndorffgrant opened this issue Sep 16, 2024 · 1 comment
Assignees
Labels
bug something isn't working P - Low S - Triaged Must have priority label

Comments

@orndorffgrant
Copy link
Collaborator

Description of the bug

At least on noble, when run on a laptop that is not plugged in, features/api/unattended_upgrades.feature will fail when looking for a non-null last_run value. It fails because the unattended-upgrade will refuse to run when not connected to power.

Expected behavior

This test should either pass when not connected to power, or fail loudly with a clear explanation that it requires being connected to power.

Current behavior

The test fails when looking for a non-null value with no indication that it is not due to a bug.

To Reproduce

  1. Unplug your laptop
  2. tox run -e behave -- features/api/unattended_upgrades.feature -D releases=noble -D machine_types=lxd-container
@orndorffgrant orndorffgrant added the bug something isn't working label Sep 16, 2024
@orndorffgrant
Copy link
Collaborator Author

orndorffgrant commented Sep 18, 2024

There should be a configuration to tell unattended-upgrades to run even if not connected. We can hopefully just set that on before triggering it.

Unattended-Upgrade::OnlyOnACPower "false"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working P - Low S - Triaged Must have priority label
Projects
None yet
Development

No branches or pull requests

2 participants