Broken infra mapping button

[Yadnyawalkya]

Description
Create Infra Mapping button seems to be broken, not able to open infra map modal.

Appliance
upstream/master.20180529235621_bee8c3b

[AllenBW]

👀

[michaelkro]

I was originally seeing this exact issue after having followed this sequence this morning

1. Pulled ManageIQ and ManageIQ-Classic master
2. Ran bin/update in both repositories

After @AllenBW suggested reinstalling node_modules, I completely wiped my local installation, and rebuilt my environment from scratch, and now the issue is resolved.

Is there any way to rebuild the appliance where this issue is being seen? Perhaps something odd is happening while updating? @Yadnyawalkya

[AllenBW]

So I saw this, thought it was an issue, purged and reupped node_modules.. and we're all good...

a gif of what I seeeeeeeeee (ignore that its a g build, still on v2v master)

[kedark3]

@Yadnyawalkya do we have a BZ for this ?

[priley86]

@Yadnyawalkya @kedark3 can you confirm that this fixes the issue? I don't see this on my side w/ latest code.

[kedark3]

Waiting for it to appear in nightly, not in current nightly of 30th May.

[bthurber]

Verified in latest nightly.

[priley86]

I would try re-running bin/update or bin/setup in manageiq. Unfortunately I don't know how to reproduce this here.

[priley86]

also you can try running yarn install in v2v

[AparnaKarve]

bin/update did not resolve this issue on the appliance.

[AparnaKarve]

So I have narrowed down the issue a little further and have confirmed that this PR in Classic UI - ManageIQ/manageiq-ui-classic#3420 that was recently merged is causing issues with our wizards.

Things to note about this PR -

• This is the very first React PR in the manageiq-ui-classic repo
• It is using "@manageiq/react-ui-components", which is a possible suspect for the issue we are seeing (there could be other problematic packages too, but this one caught my attention)
• It did not fail in Classic UI CI
• It does not cause failures with bin/update and webpack compilation
• No failures are seen in the browser console

So what's troubling is, it's pretty much under the radar with no tell-tale signs of something being wrong until we get to the Migration screen and hit the "Create Infrastructure Mapping" button.

@priley86 I think we will just have to examine all the packages being used in this PR and "@manageiq/react-ui-components" one-by-one and by the process-of-elimination (which is a long and tedious process) find out what is interfering with our wizards and packages used by the wizards.

I really hope there is a better approach to narrowing this down further.

[serenamarie125]

yikes! Thanks for spending so much time on this @AparnaKarve

@ohadlevy fyi