Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: Unable to remove an Insights Advisor action plan after one is created, because the left hand menu is covering the response buttons. This is the case both then the menu is minimized as well.
Version-Release number of selected component (if applicable): 6.8.4 & 6.9
How reproducible:
Steps to Reproduce:
1. Login to Sat UI
2. Advisor > Planner
3. Create Plan > Save
4. Click on the trash can on the plan
Actual results:
Response buttons on the left hand bottom of the screen are hidden by the main menu
Expected results:
Should be able to delete the plan that was created
Additional info:
Also the edit icon and delete icon overlap on the plan boxes.
Closing this bugzilla as a duplicate of bug 1897213. If there are any concerns, please feel free to open and include appropriate comment. Thanks!
*** This bug has been marked as a duplicate of bug 1897213 ***