-
Bug
-
Resolution: Done
-
Medium
-
None
-
OSC 1.6.0, OSC 1.7.0
-
None
-
1
-
False
-
None
-
False
-
-
-
Kata Sprint #256
-
0
-
0.000
Launching a pod with peer-pods on AWS will fail with
4m2s Warning FailedCreatePodSandBox Pod/u62vhmtj-example-41566 Failed to create pod sandbox: rpc error: code = Unknown desc = CreateContainer failed: remote hypervisor call failed: rpc error: code = Unknown desc = creating an instance : Creating instance (<nil>) returned error: operation error EC2: RunInstances, https response error StatusCode: 400, RequestID: 86ae9879-8020-4fab-b1a9-b1c0675c7060, api error InvalidParameterCombination: The specified AMI does not support a boot mode that is compatible with AMD SEV-SNP. Specify a compatible AMI and try again.:
Automation and CI tickets will need to be created
A docs ticket will need to be created
Steps to reproduce
Subscribe to kata
Create peer-pods-cm without
DISABLECVM: "true"
create kataconfig
enablePeerPods: true
Create a namespace & launch a pod with peer-podste
Workaround:
add to peer-pods-cm data section:
DISABLECVM: "true"
if kataconfig was already created
oc set env ds/peerpodconfig-ctrl-caa-daemon -n openshift-sandboxed-containers-operator REBOOT="$(date)"
