Description

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-pods

Expected result

A running pod

Actual result

The pod never gets created.  oc get events in the namespace will have errors containing 

The specified AMI does not support a boot mode that is compatible with AMD SEV-SNP

Env

OCP 4.16.3 on AWS

GA OSC 1.6.0

Additional helpful info

This will require doc changes in https://docs.redhat.com/en/documentation/openshift_sandboxed_containers/1.6/html/user_guide/deploying-public-cloud#deploying-workloads-aws

The data: section of the peer-pods-cm yaml will be similar to:
CLOUD_PROVIDER: "aws"VXLAN_PORT: "9000"PODVM_INSTANCE_TYPE: "t3.medium" PODVM_INSTANCE_TYPES: "t2.small,t2.medium,t3.large" PROXY_TIMEOUT: "5m"PODVM_AMI_ID: "<podvm_ami_id>" AWS_REGION: "<aws_region>" AWS_SUBNET_ID: "<aws_subnet_id>" AWS_VPC_ID: "<aws_vpc_id>" AWS_SG_IDS: "<aws_sg_ids>"
DISABLECVM: "true"