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

UI: The filter feature in the instances listing window doesn't function as expected. #10310

Open
MI-DROZ opened this issue Jan 31, 2025 · 2 comments

Comments

@MI-DROZ
Copy link

MI-DROZ commented Jan 31, 2025

problem

When trying to filter the instance listing by domain or user the filter drop downs don't populate correctly. They initially show the domains names double listed in the drop down menu. For example, selecting the domain drop down displays something like "ROOT/Domain1 ROOT/Domain1". Selecting a domain option does not then populate the selection back into the filter box. Clicking search after selecting a domain (and even an account) does not return a listing and even reports the user as not existing (it references the user not existing in the ROOT domain ID.

versions

Cloudstack 4.20.0.0

The steps to reproduce the bug

  1. Create multiple domains with multiple account / users and instances belonging to users in the domains.
  2. Access the root domain as root admin.
  3. Click on Computer - Instances to view all instances in the system.
  4. Click on the filter icon next to the search bar at the top of the listing.
  5. Attempt to select a domain to view all instances under that domain.
  6. Click search.
    ...

What to do about it?

Would expect to be able to filter the instance listing as root admin by domain (showing all instances in a domain) or by another parameter presented in the filter window. If a user is selected it should search all domains (or the one selected) for that user.

Copy link

boring-cyborg bot commented Jan 31, 2025

Thanks for opening your first issue here! Be sure to follow the issue template!

@DaanHoogland
Copy link
Contributor

@MI-DROZ #10292 solves a similar issue, but I can not reporduce your issue on the qa env . Can you try to reproduce it there?

Did you try 4.19 or the latest of main as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants