Created attachment 1507922 [details] floating_ip_with_manageiq Description of problem: Version-Release number of selected component (if applicable): 5.10.0.24 How reproducible: Always Steps to Reproduce: 1. Add an azure provider 2. Go to detail of Azure Router/Sec Group/Floating IP 3. Type contains ManageIQ/Providers/Azure/Network Manager Actual results: Expected results: Additional info:
https://github.com/ManageIQ/manageiq/pull/18332
Verification failed in 5.11.0.10. For Routers/Security groups are types still displayed with ManageIQ path.
https://github.com/ManageIQ/manageiq/pull/19070
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/7518ff1c0a0f6238e90143d27c6263df93fc6927 commit 7518ff1c0a0f6238e90143d27c6263df93fc6927 Author: Milan Zazrivec <mzazrivec> AuthorDate: Mon Jul 29 08:16:18 2019 -0400 Commit: Milan Zazrivec <mzazrivec> CommitDate: Mon Jul 29 08:16:18 2019 -0400 Add missing display names for some Azure provider models https://bugzilla.redhat.com/show_bug.cgi?id=1652577 locale/en.yml | 3 +- 1 file changed, 2 insertions(+), 1 deletion(-)
New commit detected on ManageIQ/manageiq/ivanchuk: https://github.com/ManageIQ/manageiq/commit/510bcc18895d1545a926164fb7c5c74c740bfb16 commit 510bcc18895d1545a926164fb7c5c74c740bfb16 Author: Brandon Dunne <bdunne> AuthorDate: Tue Jul 30 10:20:28 2019 -0400 Commit: Brandon Dunne <bdunne> CommitDate: Tue Jul 30 10:20:28 2019 -0400 Merge pull request #19070 from mzazrivec/add_missing_display_names_for_azure_models Add missing display names for some Azure provider models (cherry picked from commit 8ec9f1fdea94cdefbed8677c96b24088bd247609) https://bugzilla.redhat.com/show_bug.cgi?id=1652577 locale/en.yml | 3 +- 1 file changed, 2 insertions(+), 1 deletion(-)
Verified in 5.11.0.18. Types are displayed correctly.
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