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

Generic Objects are not displayed in the Instances view #9255

Closed
uejo opened this issue Aug 27, 2024 · 0 comments · Fixed by #9266
Closed

Generic Objects are not displayed in the Instances view #9255

uejo opened this issue Aug 27, 2024 · 0 comments · Fixed by #9266
Assignees
Labels

Comments

@uejo
Copy link

uejo commented Aug 27, 2024

  1. Describe the issue you are having and what you expected to happen.
    When clicking on the "Instances" on my Service details page i get redirected to the Service (All Generic Objects) page, but it doesn't show any generic objects, instead a blank page:
    image

image

I expect the generic objects to get listed, same as in the Service UI:
image

  1. Describe the steps to reproduce, including any log snippets and stack traces that will help diagnose.
    Create a service, and add a generic object to it. Click on the "Instances" Link in the Service details page.
    Note: this link is somehow only available as administrator, which is also differing from the Service UI, there you can see the generic object as a user with less privileges, i could also not really find out which permission is the correct one to enable the link.
    No errors in the the manageiq log, nor in the browser.

  2. Describe your environment, including
    Version: container version from docker hub: quinteros-1.20240402225756_f6add08
    and
    radjabov-pre.20240404134108_e4479a1

I also stumbled upon this issue #8675
it might relate, although it doesn't note anything about the also missing permissions.

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

Successfully merging a pull request may close this issue.

2 participants