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

Cannot unselect machine after selecting a group containing it #5512

Open
tjwsl opened this issue Aug 7, 2024 · 0 comments
Open

Cannot unselect machine after selecting a group containing it #5512

tjwsl opened this issue Aug 7, 2024 · 0 comments
Labels

Comments

@tjwsl
Copy link

tjwsl commented Aug 7, 2024

Describe the bug
In the MAAS UI, there are checkboxes allowing the user to select an entire group of machines, whether the default states or the results of a search filter. Selecting such a group selects and disables the subordinate checkboxes for each machine, preventing the user from unselecting individual members of the selected group

maas-ui version
I do not know where to find this, but it is the default UI for each MAAS version I tested.

MAAS version
This goes back to 3.3. 3.2 did not exhibit the behavior.

LP issue
lp#2056157

To Reproduce
Steps to reproduce the behavior:

  1. Go to the main "Machines" page on a MAAS system with multiple machines
  2. Select a group, such as "Ready" by checking the box at the left
  3. Note that all machines in the group are selected and their individual checkboxes are grayed out
  4. Note that you are not able to unselect individual machines

Expected behavior
Particularly for large environments, the grouping mechanism is unlikely to be precise enough, and there is a need to be able to unselect individual machines from a larger group. The workaround -- selecting the desired machines individually -- is tedious at best, and prone to errors of omission or inclusion.

By comparison, MAAS 3.2 does allow this sort of de-selection from a group.

Desktop (please complete the following information):

  • OS: noble 24.04
  • Browser: behavior observed on both Firefox and Chrome
  • Versions: Firefox 128.0.3-1 and Chrome 127.0.6533.88

Additional context
Reported by an Ubuntu Pro customer

@tjwsl tjwsl added the Bug 🐛 label Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant