-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
2
-
True
-
False
-
None
-
HAC Infra OCM - Sprint 237, HAC Infra OCM - Sprint 238
User story:
So that I can be confident that all the correct information was entered, as a user, I want a page just before creating a cluster that lists all values that will be used to create the cluster.
Acceptance criteria:
- All the information entered in the wizard is displayed on the review page. This includes the addition of a "Control plane" section for both standalone and hosted control plane clusters.
- When finally submitting the form, all the information about the cluster is submitted to the back-end and a cluster is successfully created
- Once submitted, the user will be taken to a cluster detail page for the new cluster
- Visual confirmation that the "Installing..." progress stepper progresses through to installing cluster.
Mockups:
Mockups | PD 1434
--------------------------------------------------------------------------------------
Summary
This story is to work out any bugs that might have been introduced on the review page and submission while adding hypershift-specific items.
Major tasks:
- Ensure that the review page contains all data entered when going through the wizard
- Ensure that submission works and creates a cluster
Â
- depends on
-
HAC-2405 [Hypershift ROSA][Wizard] Cluster settings / Machine pool -Add private subnet
- Closed
-
HAC-2406 [Hypershift ROSA][Wizard] Networking / Configuration - Install into a VPC Cloud
- Closed
-
HAC-2410 [Hypershift ROSA] Cluster updates - hide individual vs recurring choice
- Closed
-
HAC-2416 [Hypershift ROSA][Wizard] Select control plane type (step 2)
- Closed
-
HAC-2886 [Hypershift ROSA Wizard] Cluster updates - maintenance schedule control plane only
- Closed
-
HAC-2888 [Hypershift ROSA Wizard][MVP] Cluster updates - change update strategy ordering
- Closed
-
HAC-3134 [Hypershift ROSA][Wizard] Networking / Configuration - Network Configuration (private/public)
- Closed
-
PD-1434 [ROSA] HyperShift Cluster Creation for ROSA (Part 2)
- Closed
- is related to
-
HAC-4349 [ROSA Wizard]Unable to create ROSA cluster when autoscaling enabled via UI
- Closed
-
HAC-3979 [Hypershift ROSA][Wizard] Modify cluster updates step for Hypershift
- Closed
-
HAC-4052 [Hypershift ROSA] User allowed to proceed to next steps in wizard with an empty public subnet ID from Networking > configuration step.
- Closed
-
HAC-4118 [Hypershift ROSA] Unable to create ROSA Hypershift cluster as wizard throws the error that node compute labels are not supported.
- Closed
-
HAC-4120 [Hypershift ROSA] Wrong compute node calculation or definition from wizard during cluster creation
- Closed
-
HAC-4149 [Hypershift ROSA] User unable to create a HCP cluster when availability zone of a machine pool's private subnet different from the selected public subnet's AZ.
- Closed
-
HAC-4273 [ROSA Hypershift] "OIDC and operator roles" cluster installation step is waiting state when no operator roles created prior to installation.
- Closed
-
HAC-4346 [Hypershift ROSA]Compute node count definition is wrong from both "machine pool" and "review and create" step when user previously used a ROSA wizard for classic multi-az cluster creation.
- Closed
-
HAC-4119 [Hypershift ROSA] Upgrade strategy didn't respect the wizard configuration definition.
- Closed
-
HAC-4122 [Hypershift ROSA] an irrelevant error related to upgrade shown for a hypershift cluster under installation
- Closed
- relates to
-
HAC-4028 [Hypershift ROSA] Machine pool definitions (like AZ and selected private subnets) are wrongly mentioned under "Networking" step from "Review and create" page.
- Closed
-
HAC-4348 [Hypershift ROSA] Minimum and maximum node count per machine pool maximum limit validation seems broken when it exceed the cluster node count limit
- Closed
- mentioned on