-
Bug
-
Resolution: Duplicate
-
High
-
None
-
OSC 1.5.3
-
None
-
False
-
None
-
False
-
-
-
0
-
0
-
High
Description
<What were you trying to do that didn't work?>
In the example in https://access.redhat.com/documentation/en-us/openshift_sandboxed_containers/1.5/html/openshift_sandboxed_containers_user_guide/deploying-sandboxed-container-workloads-peer-pods#sandboxed-containers-create-config-map-peer-pods-azure-web_deploying-sandboxed-containers-peer-pods AZURE_INSTANCE_SIZES list instance sizes for Confidential versions (they have "C" in the name) For this version we don't support CVMs yet so this is wrong. The list of instances that we have tests with is Standard_B2als_v2,Standard_B2as_v2,Standard_D2as_v5,Standard_B4als_v2,Standard_D4as_v5,Standard_D8as_v5
Fixing this would also make the AZURE_INSTANCE_SIZE value make sense as it was referencing an instance that was not in AZURE_INSTANCE_SIZES.
Additionally the pod yaml in https://access.redhat.com/documentation/en-us/openshift_sandboxed_containers/1.5/html/openshift_sandboxed_containers_user_guide/deploying-sandboxed-container-workloads-peer-pods#sandboxed-containers-deploying-workloads-with-kata-peer-pods-web_deploying-sandboxed-containers-peer-pods references Standard_DC4as_v5. This should be Standard_D4as_v5 to make the non confidential instance types in AZURE_INSTANCE_SIZES
Steps to reproduce
<What actions did you take to hit the bug?>
1.
2.
3.
Expected result
<What did you expect to happen?>
Pod would run
Actual result
<What actually happened?>
Pod stuck in CreatingContainer and an event:
"error": { "code": "BadRequest", "message": "The VM size 'Standard_DC4as_v5' is not supported for creation of VMs and Virtual Machine Scale Set with '<NULL>' security type." } } -------------------------------------------------------------------------------- : unknown
Impact
<How badly does this interfere with using the software?>
Inexperiences users would not be able to start a peerpod workload as documented.
Env
<Where was the bug found, i.e. OCP build, operator build, kata-containers build, cluster infra, test case id>
OSC 1.5.3 OCP 4.15.10 Azure
Additional helpful info
<logs, screenshot, doc links, etc.>
- relates to
-
KATA-2735 Any restart of caa-daemon causing all peerpods on the same node to restart
- New