-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
Add support for custom security group Day 1 ROSA classic - worker nodes
-
False
-
-
True
-
To Do
-
XCMSTRAT-46 - ROSA: Additional Security Group(s) during Cluster Creation (Day-1)
-
0% To Do, 0% In Progress, 100% Done
- is cloned by
-
OCMUI-546 UI: Add support for security group Day 1 - control and infra nodes
- Closed
-
OCMUI-547 UI: Add support for custom security group for controlPlane and Infra nodes - ROSA classic
- Closed
-
OCMUI-1039 UI: Add support for custom security group Day 1 OSD - worker nodes
- Closed
- is depended on by
-
OCMUI-1093 [OCM UI][OSD/ROSA] "Edit machine pool" didn't show the security group definition configured for machine pool.
- Closed
-
OCMUI-1121 [OCM UI][OSD/ROSA]Cluster wizard submission fails with an error from backend due to security group references
- Closed
-
OCMUI-1006 [OCM UI][ROSA]Wrong alignment of security group drop-down in case of larger security group names
- Closed
-
OCMUI-1007 [ROSA][Day2] Security group definition overlapped with subnet definition in case of longer SG names
- Closed
-
OCMUI-1063 [ROSA Wizard]Improve the message when no security group found in selected VPC
- Closed
-
OCMUI-1064 [ROSA Wizard]Wizard allowed to choose more than 5 security groups and resulted failure during cluster submissions
- Closed
-
OCMUI-1073 [ROSA wizard]Expand the "Additional security groups" section during step navigation in case already some security groups selected.
- Closed
-
OCMUI-1086 [ROSA Wizard]Wrong indication in security group selection when user switches initially selected VPC
- Closed
-
OCMUI-1087 [ROSA Wizard] previously selected security group definition shown in "Review and create" step after changing the unsupported version.
- Closed
- is related to
-
OCMUI-1066 [ROSA Wizard] ROSA cluster creation failed when max security groups (i.e.5) assigned to all nodes
- Closed
-
OCMUI-1063 [ROSA Wizard]Improve the message when no security group found in selected VPC
- Closed
-
OCMUI-1064 [ROSA Wizard]Wizard allowed to choose more than 5 security groups and resulted failure during cluster submissions
- Closed
-
OCMUI-1065 [ROSA Wizard] Missing refresh/reload the security group list from wizard creates bad usability experience.
- Closed
-
OCMUI-1073 [ROSA wizard]Expand the "Additional security groups" section during step navigation in case already some security groups selected.
- Closed
-
OCMUI-1086 [ROSA Wizard]Wrong indication in security group selection when user switches initially selected VPC
- Closed
-
OCMUI-1087 [ROSA Wizard] previously selected security group definition shown in "Review and create" step after changing the unsupported version.
- Closed
- links to
- mentioned on
1.
|
DOD: Training materials supplied to Support/SRE | To Do | Unassigned | ||
2.
|
DOD: Docs verified by QE | To Do | Unassigned | ||
3.
|
DOD: Docs completed and merged | To Do | Unassigned | ||
4.
|
DOD: All known issues captured and blockers resolved | To Do | Unassigned | ||
5.
|
DOD: All work items belonging to this Epic are complete | Closed | Unassigned | ||
6.
|
DOD: Code merged for regular build/release testing in the HAC Common CI/CD framework | To Do | Unassigned | ||
7.
|
DOD: CI runs successfully with test automation | To Do | Unassigned | ||
8.
|
DOD: Automated/Integrated tests complete | To Do | Unassigned | ||
9.
|
DOD: Architectural artifacts completed, reviewed and stored | To Do | Unassigned | ||
10.
|
DOD: Product Manager and UX signed off on solution | To Do | Unassigned | ||
11.
|
DOD: Acceptance criteria related to this Epic has been identified and met | To Do | Unassigned |