Created attachment 1781295 [details] Storage and network mapping fields are empty Description of problem: Plan wizard summary page doesn't reflect ANY mapping info when editing existing plan Version-Release number of selected component (if applicable): 2.0.0-12 How reproducible: 100% Steps to Reproduce: 1. Create a new provider, network and storage mappings and plan that will use all that 2. Edit just created plan 3. Go to summary page Actual results: Storage and network mapping fields will be empty Expected results: Mapping fields should be populated Additional info:
I think this BZ is related to https://bugzilla.redhat.com/show_bug.cgi?id=1958652. My understanding is that the wizard doesn't load the data from the mapping linked to the plan which has (at least) two side effects: 1. The default is again pre-selected when going through all the steps. 2. The review is empty. @mturley @gdubreui can you check and tell me if I'm correct?
That's definitely a regression, we load the data from the linked mapping and it had been working fine recently. Igor, can you share the cluster where you're seeing this?
This is mgn03 on PSI. Do you need connection details or is this enough for you?
Should be fixed by https://github.com/konveyor/forklift-ui/pull/591 (backport: https://github.com/konveyor/forklift-ui/pull/592). See notes in the PR.. I'm not certain this will fix the issue for network mappings, only storage mappings. I was not able to reproduce the issue for network mappings. @ibragins if you can help me reproduce that, either now or when verifying this fix, that would be great. I suspect the network mapping part of the issue may have been caused by either source or target networks being changed/removed in the providers after the plan was created and before it was edited. Opened https://github.com/konveyor/forklift-ui/issues/590 to handle that, but if that's the case I don't think it should be a release blocker.
Reproduced and figure out the issue with the network mappings here, it was related to cache invalidation. Also fixed in the above PR.
The fix is in build 2.0.0-13 / iib:74067.
Verified this on MTV 2.0.0-13, mapping info is on its place and it is correct
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 (MTV 2.0.0 images), 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/RHEA-2021:2381