Red Hat Bugzilla – Bug 1490416
Unexpected error message while adding new Cloud Subnet
Last modified: 2018-02-28 08:04:49 EST
Created attachment 1324468 [details] Error message Description of problem: While attempting to add new cloud subnet, selecting specific network manager and then selecting <Choose> option again causes unexpected error. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Navigate to Networks -> Subnets 2. Choose configuration -> Add a new Cloud Subnet 3. Select specific network manager 4. Select <Choose> option again Actual results: Server error (screenshot as attachment) Expected results: No error Additional info:
Hi! Would it be possible to get a snippet of evm.log with the relevant error?
Created attachment 1325271 [details] evm.log file Adding part of evm.log file, I don't see any error there.
I confirm the issue. This is Javascript related, therefore nothing to appear in the log. Looking forward to provide a patch. Thanks
This issue happens only on Fine branch, the logs actually shows: "FATAL -- : Error caught: [ActiveRecord::RecordNotFound] Couldn't find ExtManag ementSystem with 'id'=undefined" The reason is because the "External Management System ID (ems_id) gets reset to undefined and there fails the following API search" A backport can't be done because the upstream/master branch is too far apart from fine branch because the javascript controller has been re-factored (Using 'this' instead of '$scope') which involve other dependent UI components (buttons). Meanwhile a specific patch for fine branch fixes the issue: https://github.com/ManageIQ/manageiq-ui-classic/pull/2301
PR#2301 merged
Verified fixed in 5.8.3.1 (5.8.3.1.20180115183240_323eabe) since I can no longer see this _specific_ issue but I just opened up 2 other issues related to this 'new cloud subnet' form. The first one might not be that big a deal but the second one still blocks subnet creation: https://bugzilla.redhat.com/show_bug.cgi?id=1535369 https://bugzilla.redhat.com/show_bug.cgi?id=1535376
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-2018:0374