https://github.com/ManageIQ/manageiq/pull/7903
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/eadc6b2cc3456a20c1e362b4645eb06ac6804ac9 commit eadc6b2cc3456a20c1e362b4645eb06ac6804ac9 Author: Milan Zazrivec <mzazrivec> AuthorDate: Tue Apr 12 18:31:47 2016 +0200 Commit: Milan Zazrivec <mzazrivec> CommitDate: Wed Apr 13 11:18:00 2016 +0200 Show tenant name next to service template name in catalog tree https://bugzilla.redhat.com/show_bug.cgi?id=1305026 app/presenters/tree_node_builder.rb | 7 ++++++- spec/presenters/tree_node_builder_spec.rb | 4 +++- 2 files changed, 9 insertions(+), 2 deletions(-)
Tested in version 5.6.0.4-beta2.3.20160421172650_719e256. In Services -> Catalogs -> Catalogs -> All catalogs I can see column tenant, which identifies tenant, who created that catalog. But in Services -> Catalogs -> Catalog items -> All catalogs I can't identify catalogs with same name, which were created by different tenants (can see that in attachment). So I return it back on dev.
Created attachment 1151291 [details] Catalog items with tenant catalogs
Created attachment 1151297 [details] CatalogItems with tenant catalogs
https://github.com/ManageIQ/manageiq/pull/8284
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/1d5a18c3c1bc429f94ecccd6ccc61615b1828238 commit 1d5a18c3c1bc429f94ecccd6ccc61615b1828238 Author: Milan Zazrivec <mzazrivec> AuthorDate: Wed Apr 27 14:37:16 2016 +0200 Commit: Milan Zazrivec <mzazrivec> CommitDate: Wed Apr 27 17:37:26 2016 +0200 Show tenant name next to service template catalog in catalog tree https://bugzilla.redhat.com/show_bug.cgi?id=1305026 app/controllers/catalog_controller.rb | 7 ++++--- app/presenters/tree_node_builder.rb | 7 ++++++- spec/presenters/tree_node_builder_spec.rb | 4 +++- 3 files changed, 13 insertions(+), 5 deletions(-)
Verified in 5.6.0.5-beta2.4.20160503153816_1fb554f. In Catalog items is catalog creator in brackets.
https://github.com/ManageIQ/manageiq/pull/8473
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:1348