Bug 2040637
Summary: | [RFE] Show all assigned Ansible roles in the Host UI | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Stefan Meyer <smeyer> |
Component: | Ansible - Configuration Management | Assignee: | Leos Stejskal <lstejska> |
Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.11.0 | CC: | dsinglet, jsenkyri, lstejska, msviriko, oezr, rlavi, torkil |
Target Milestone: | Unspecified | Keywords: | FutureFeature, MigratedToJIRA, Reopened, Triaged, UserExperience |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-06-06 02:21:26 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Stefan Meyer
2022-01-14 10:40:53 UTC
Hi, I was wondering about this as well, I'm not sure what is the answer, but consider two following points: 1) Host has hostgroup assigned, that already has 15-20 roles assigned to it - if roles are in order in which they are executed, user see only the Hostgroup roles in the page and needs to use pagination to get to the Host assigned roles 2) Fetching all roles from the server is bit slower and thus user will be waitig for that longer - this might not be hard issue, but if 90% of Users want to see only the directly assigned, should we have all the users waiting longer just for the 10% who wants to see more? Please consider these points and let us know if you still think we should show all roles. If you do, I'll take it to our UX experts for further discussion. OTH if you agree with my points, please close this :) Ondřej, that is a valid point. How about making it configurable in settings? Well I do not think that setting for such a small thing make sense. It says "we couldn't make up our mind, so it's up to you" that usually is an antipattern. We were talking about these cases in upstream and we believe that for all users it make sense to be more opinionated and give users less choices for them not to be overwhelmed with choices :) Fair enough. Then I would prefer to have all assigned Roles listed as in Satellite 6. So after a discussion with our UX, we've come up with a check-box on top of the table that would allow you to show/hide inherited roles. Would that be better than what we have now and would that solve this BZ in your opinion? ;) Yes, that is a fine solution and would solve this BZ. :) Created redmine issue https://projects.theforeman.org/issues/34380 from this bug Just a quick comment: If a host has roles inherited from host group but *doesn't* have any roles directly assigned (outside of host group) then the page returns 'No Ansible roles assigned'. There's no way to see roles inherited from the host group. If a host has at least 1 role directly assigned then 'view all assigned roles' hyperlink pops up where you can see roles inherited from host group. The behavior from Comment 9 has been fixed by https://bugzilla.redhat.com/show_bug.cgi?id=2111921 At this point, I believe this functionality is delivered in Satellite 6.12, therefore closing as CURRENTRELEASE. If I missed something, please let me know. Reopening based on the conversation with the reporter. It is still suboptimal that user needs to click on the link to see the roles inherited from the host group. Based on the comment 5 there was an agreement on the implementation. Maria, do we have any mock for this or was this conversation captured somewhere? This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |