Bug 1954106
| Summary: | The "Next" button is disabled after any change. Need to click on "Back"to re-enable it. | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Alexander Chuzhoy <sasha> |
| Component: | assisted-installer | Assignee: | Jiri Tomasek <jtomasek> |
| assisted-installer sub component: | assisted-ui | QA Contact: | Udi Kalifon <ukalifon> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | CC: | aos-bugs, cvultur, iovadia, jtomasek, lalon, mchernyk, mlibra, ohochman, tjelinek, ukalifon |
| Version: | 4.8 | Keywords: | TestBlocker |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-28 08:45:59 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Alexander Chuzhoy
2021-04-27 15:26:44 UTC
What happens is that after every change the "Next" button becomes disabled. You need to click on the "back" button and the "Next" button becomes enabled. Can you please confirm that there was no error message next to the 'Next' button in the wizard? Can you please elaborate on exact steps you did in networking step which lead to Next button not getting enabled? Went through the issue with Sasha, the problem occurs with SNO, on networking step, do any field change in the form, the form gets autosaved but form remains dirty and the next button won't get highlighted. Quick repro step: When the user arrives to the networking step the next button is enabled. however, if the user changes for example the cluster network CIDR field in the advanced networking section then the next button gets disabled. Observing the React context I see there is a discrepancy in the field that changed; the initialValues still hold the old value event after the field was validated the form was autosaved and we patched the cluster with the new value. *** Bug 1954697 has been marked as a duplicate of this bug. *** impact also multi-node cluster .. see dup: https://bugzilla.redhat.com/show_bug.cgi?id=1954697 *** Bug 1939134 has been marked as a duplicate of this bug. *** I was facing the same issue when fixing MGMT-5433. Should be fixed by the MGMT-5433 patch on the Networking step but adding the same workaround for the Host Discovery step as well. Failed QA ========= v1.0.19.3 mark / unmark operator and Next button disabled. (I waited ~5 and its status didn't changed) Verified on Staging v1.0.19.3 According to Jiri, fix applied on OCM. |