New commit detected on ManageIQ/manageiq-ui-service/fine: https://github.com/ManageIQ/manageiq-ui-self_service/commit/dacda2d6b525230c03012da2d64b869e2ca8132b commit dacda2d6b525230c03012da2d64b869e2ca8132b Author: Chris Kacerguis <chriskacerguis.github.com> AuthorDate: Tue Apr 4 16:14:42 2017 -0500 Commit: Satoe Imaishi <simaishi> CommitDate: Wed Apr 5 19:10:14 2017 -0400 Merge pull request #634 from chalettu/bz-1438922 Catalogs viewable with wrong permissions (cherry picked from commit 6d418b2d4eb1c9cf0c2091a8ef0d1cb7b9e0d3d6) https://bugzilla.redhat.com/show_bug.cgi?id=1439309 client/app/core/rbac.service.js | 4 ++-- client/app/states/catalogs/explorer/explorer.state.js | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)
Rest is fixed but Order still says "Error loading Orders" 5.8.0.12-rc1.20170425180304_4f35996
Sooooo I created a user that only had my service product features, not seeing this behavior on latest master, but maybe I'm not troubleshooting this correctly?
https://github.com/ManageIQ/manageiq-ui-service/pull/723
Not sure why this moved from POST -> ON_DEV, moving back.
This isn't backported to Fine branch yet.
ooooo we should totally backport this!! <3
Thinking the status of this shouldn't be on dev....
New commit detected on ManageIQ/manageiq-ui-service/fine: https://github.com/ManageIQ/manageiq-ui-self_service/commit/cf99956573071bdb260e4ed811a17b04e1727d51 commit cf99956573071bdb260e4ed811a17b04e1727d51 Author: Chris Kacerguis <chriskacerguis.github.com> AuthorDate: Fri Apr 28 12:03:13 2017 -0500 Commit: Satoe Imaishi <simaishi> CommitDate: Tue Jun 6 12:01:05 2017 -0400 Merge pull request #723 from AllenBW/BZ/#1439309 BZ#1439309 - Not able to see orders when not enough permission to see catalogs (cherry picked from commit 19664c67bd1ca516f28a32c7eb0b772ff31fc2a1) https://bugzilla.redhat.com/show_bug.cgi?id=1439309 client/app/core/rbac.service.js | 3 +-- client/app/core/session.service.spec.js | 5 ++--- 2 files changed, 3 insertions(+), 5 deletions(-)
Fixed in 5.8.1.0.20170623170756_3ed4411
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/RHSA-2017:1758