Bug 1312046
Summary: | Adding a duplicate Foreman provider name never redirects to the flash message | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Chris Pelland <cpelland> |
Component: | Providers | Assignee: | Drew Bomhof <dbomhof> |
Status: | CLOSED ERRATA | QA Contact: | Jan Krocil <jkrocil> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.5.0 | CC: | cpelland, dajohnso, dbomhof, jfrey, jhardy, jkrocil, jprause, mfeifer, obarenbo |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.5.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.5.3.2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1310895 | Environment: | |
Last Closed: | 2016-04-13 18:45:13 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: | |||
Bug Depends On: | 1310895 | ||
Bug Blocks: |
Comment 1
CFME Bot
2016-03-01 20:51:34 UTC
Failed QA on 5.5.3.2 - 5.5.3.2.20160318152106_92d2d67. The provider cannot be added twice anymore (this part is fixed) but it spawns 4 flash errors with sort of duplicate and incorrect text. See attachment (left image is for configuration managers) Also see related https://bugzilla.redhat.com/show_bug.cgi?id=1317892 Hi Jan, Configuration Manager providers require additional field validation than infra providers, that being said, the resulting four flash errors are correct for that provider. Seeing that the main bug (system hangs) was solved and is merged, we would like to see a new BZ created to address the UI changes. We would have to revamp how validation errors are returned when the reported event is attempted with this provider type. Ok, closing as verified in 5.5.3.2. There is a separate BZ for the error mentioned above. 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-2016:0616 |