Blocker Description of the problem:
In OSD wizard flow, As soon as user chosen a node count value from drop-down under machine pool page, the widget has broken with inline error. This is happening only when user chosen multi-az availability settings in wizard flow
Browser console logs
Uncaught Error: Objects are not valid as a React child (found: object with keys {_reactName, _targetInst, type, nativeEvent, target, currentTarget, eventPhase, bubbles, cancelable, timeStamp, defaultPrevented, isTrusted, isDefaultPrevented, isPropagationStopped}). If you meant to render a collection of children, use an array instead.
at throwOnInvalidObjectType (chrome-root.ef2664ff17126cff.js:35876:9)
at updateSlot (chrome-root.ef2664ff17126cff.js:36191:7)
at reconcileChildrenArray (chrome-root.ef2664ff17126cff.js:36338:22)
at reconcileChildFibers (chrome-root.ef2664ff17126cff.js:36810:16)
at reconcileChildren (chrome-root.ef2664ff17126cff.js:40158:28)
at updateHostComponent (chrome-root.ef2664ff17126cff.js:40908:3)
at beginWork (chrome-root.ef2664ff17126cff.js:42602:14)
at HTMLUnknownElement.callCallback (chrome-root.ef2664ff17126cff.js:25153:14)
at HTMLUnknownElement.o (helpers.js:72:23)
at Object.invokeGuardedCallbackDev (chrome-root.ef2664ff17126cff.js:25202:16)
at invokeGuardedCallback (chrome-root.ef2664ff17126cff.js:25266:31)
at beginWork$1 (chrome-root.ef2664ff17126cff.js:48435:7)
at performUnitOfWork (chrome-root.ef2664ff17126cff.js:47544:12)
at workLoopSync (chrome-root.ef2664ff17126cff.js:47450:5)
at renderRootSync (chrome-root.ef2664ff17126cff.js:47418:7)
at performSyncWorkOnRoot (chrome-root.ef2664ff17126cff.js:47069:20)
at flushSyncCallbacks (chrome-root.ef2664ff17126cff.js:33031:22)
at flushSync (chrome-root.ef2664ff17126cff.js:47185:7)
at finishEventHandler (chrome-root.ef2664ff17126cff.js:24965:5)
at batchedUpdates (chrome-root.ef2664ff17126cff.js:24983:5)
at dispatchEventForPluginEventSystem (chrome-root.ef2664ff17126cff.js:30276:3)
at dispatchEventWithEnableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay (chrome-root.ef2664ff17126cff.js:27454:5)
at dispatchEvent (chrome-root.ef2664ff17126cff.js:27446:5)
at dispatchDiscreteEvent (chrome-root.ef2664ff17126cff.js:27419:5)
The behavior works fine in prod not in staging.
Refer attached recordings OSDNodeCountSelection.mp4
Steps to reproduce:
- Launch OCM Staging UI.
- Open OSD wizard.
- Select subscription as "Annual fixed capacity subscription" and Infrastructure type as "Customer cloud subscription"
- Click "Next" and choose any of the cloud provider.
- Proceed to "Next" step and select the availability to "Multi-zone".
- Click "Next" and choose a compute node count value from the drop-down.
- See the behavior.
Actual results:
As soon as user chosen a node count value from drop-down under machine pool page, the widget has broken with above error
Expected results:
User should be allowed to choose the compute node count value from the drop-down without any issue in above case.
This was happening across all the browsers and tested with chrome, edge and firefox.
- blocks
-
OCMUI-513 PatternFly 5 Adoption
-
- Closed
-
- mentioned on
