React Warning: Unrecognized isDisabled Prop Passed to DOM Element in Provider Form

[SanthoshRam-03]

Hi @jeffibm @DavidResende0 and @agrare ,

In the ManageIQ developer environment, when I try to add a new cloud provider, the UI is indicative of a common issue in React development.

And I cannot integrate OpenStack in the local environment.

[DavidResende0]

Thanks for pointing this out @SanthoshRam-03. I'll look into this.

[DavidResende0]

Hey @SanthoshRam-03, I see the problem and am in the process of fixing it but this warning shouldn't prevent you from adding an OpenStack provider. What error do you see when you try saving the provider?

[SanthoshRam-03]

Hi @DavidResende0 When I'm filling out the credentials details for OpenStack and clicking the validate button, its not validating, and it's also taking too much time.

And this React Warning could be the reason for it?

Screenshots of Credentials and Logs:

The logs are repeatedly loading on the Rails Local Server.

[agrare]

Hey @SanthoshRam-03 are you running this as an appliance or with rails s in development mode?

[SanthoshRam-03]

Hi, @agrare running the rails server in development mode. The above log screenshot is regarding this.

[agrare]

Thanks so the verify task hanging is likely due to not having a queue worker running like you would on an appliance.
In development we recommend a rails server plus a simulated queue worker typically, you can run this with a rails c then simulate_queue_worker. You can check the developer setup guide towards the end we cover this there https://www.manageiq.org/docs/guides/developer_setup.html

[jeffibm]

Hey @DavidResende0 , this warning gets fired from here - async-credentials/async-credentials.jsx#L83

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.