Bug 1656722
Summary: | Inconsistent options in `Show at Login` drop-down of Visual tab on My Settings page. | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Parthvi Vala <pvala> |
Component: | UI - OPS | Assignee: | Greg Piatigorski <gpiatigo> |
Status: | CLOSED ERRATA | QA Contact: | Parthvi Vala <pvala> |
Severity: | medium | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
Priority: | medium | ||
Version: | 5.9.6 | CC: | bmidwood, dmetzger, gpiatigo, hkataria, lavenel, mpovolny, obarenbo, simaishi |
Target Milestone: | GA | ||
Target Release: | 5.11.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.11.0.10 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-12-12 13:34:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | Bug | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | CFME Core | Target Upstream Version: | |
Embargoed: |
Description
Parthvi Vala
2018-12-06 07:44:52 UTC
What is the update on this BZ? I see these inconsistencies on 5.11 as well, and in some cases in our automation, if the non-existent option was selected, it results in the Exception page on re-login and there is perhaps no way to revert that, it will be nice if this can be fixed ASAP. I see that a PR for the fix has already been opened, how long before we can merge it? New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/6a7e63d452700384a39a1578e6762ec3a7903605 commit 6a7e63d452700384a39a1578e6762ec3a7903605 Author: Greg Piatigorski <gpiatigo> AuthorDate: Wed Jan 30 17:47:16 2019 -0500 Commit: Greg Piatigorski <gpiatigo> CommitDate: Wed Jan 30 17:47:16 2019 -0500 Updated MiqShortcuts for MySettings Start At Login dropdown https://bugzilla.redhat.com/show_bug.cgi?id=1656722 db/fixtures/miq_shortcuts.yml | 72 +- 1 file changed, 56 insertions(+), 16 deletions(-) Selecting GraphQL / Explorer ends in the Exception page. Is there any pre-requisite to selecting that option? Also, there are still 2 more options - Cloud Intel / Timelines, Cloud Intel / RSS which needs to be removed. Moving this back to Assigned. This is a 2 part code fix/refactoring. Related PR, to go with the one above: https://github.com/ManageIQ/manageiq-ui-classic/pull/5697 New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/2436d8da8978cd81292211b7c30f161a63436973 commit 2436d8da8978cd81292211b7c30f161a63436973 Author: Greg Piatigorski <gpiatigo> AuthorDate: Wed Jun 12 17:38:37 2019 -0400 Commit: Greg Piatigorski <gpiatigo> CommitDate: Wed Jun 12 17:38:37 2019 -0400 Remove GraphQL, Cloud Timeline and RSS from StartAt shortcut dropdown. https://bugzilla.redhat.com/show_bug.cgi?id=1656722 db/fixtures/miq_shortcuts.yml | 15 - 1 file changed, 15 deletions(-) Scaling back some of the changes. Refactoring selections for the Start At Login dropdown selections, so that GraphQL is not longer available, as well as the 2 other deprecated menus/options. This code fix goes back to just 1 PR, merged above and ready to re-test. FIXED. Verified on 5.11.0.10.20190619171116_239686f. I recently discovered that there are still a few options amiss from the list. Options such as - Cloud Intel > Utilization Migration > Migration Plans Migration > Infrastructure Mappings Migration > Migration Settings Can we add these as well? Parthvi, may open another BZ at this point since at the time of prior Verified update these were not yet defined. Not sure we want to reset status from Verified to ON_DEV at this point. Opened a new BZ for this: https://bugzilla.redhat.com/show_bug.cgi?id=1729136 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:4199 |