New commit detected on ManageIQ/manageiq/hammer: https://github.com/ManageIQ/manageiq/commit/a6f851e5e8362a577741ec4474dde41cbfe76576 commit a6f851e5e8362a577741ec4474dde41cbfe76576 Author: Harpreet Kataria <hkataria> AuthorDate: Tue Aug 13 09:24:50 2019 -0400 Commit: Harpreet Kataria <hkataria> CommitDate: Tue Aug 13 09:24:50 2019 -0400 Merge pull request #19124 from PanSpagetka/add-keypair-ownership-feature Add Auth KeyPair Ownership feature (cherry picked from commit 25019761510360eebd43844de99129b430122647) https://bugzilla.redhat.com/show_bug.cgi?id=1741634 https://bugzilla.redhat.com/show_bug.cgi?id=1741635 db/fixtures/miq_product_features.yml | 4 + 1 file changed, 4 insertions(+)
Also https://github.com/ManageIQ/manageiq-ui-classic/pull/5967
Created attachment 1607446 [details] screen shot of a group that belongs to a child tenant
Created attachment 1607447 [details] screen shot of key pair with group ownership details
Can you provide the reproducer env?
Sudhir, I have already shared my appliance IP with Libor on Friday through PM on gitter.
New commit detected on ManageIQ/manageiq/hammer: https://github.com/ManageIQ/manageiq/commit/0264849969522f478b3d47202df81063e43d140f commit 0264849969522f478b3d47202df81063e43d140f Author: Gregg Tanzillo <gtanzill> AuthorDate: Mon Aug 26 14:38:05 2019 -0400 Commit: Gregg Tanzillo <gtanzill> CommitDate: Mon Aug 26 14:38:05 2019 -0400 Merge pull request #19202 from lpichler/set_tenant_from_group_for_keypairs Set tenant from group in Authentification(KeyPairs) model (cherry picked from commit f30f40854bcffdd2ccee2231cf0f6c8bc3722fde) https://bugzilla.redhat.com/show_bug.cgi?id=1741635 app/models/authentication.rb | 6 + spec/models/authentication_spec.rb | 13 + 2 files changed, 19 insertions(+)
Verified in 5.10.9.1
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-2019:2587