Skip to content

Commit

Permalink
gcp-test: update check to run instance with confidential type
Browse files Browse the repository at this point in the history
`sev_snp`

Based on coreos/coreos-assembler#3871

(cherry picked from commit 0b797dd)
  • Loading branch information
HuijingHei authored and dustymabe committed Sep 13, 2024
1 parent 0342ba4 commit 3d42243
Showing 1 changed file with 4 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,11 @@

# See https://issues.redhat.com/browse/OCPBUGS-7582
# https://github.com/coreos/fedora-coreos-tracker/issues/1457
# https://github.com/coreos/coreos-assembler/issues/3556
#
# Force this test to not run by default unless named specifically
# or `--tag confidential` is passed to `kola run`, also requires
# `--gcp-machinetype n2d-standard-2 --gcp-confidential-vm`
# `--gcp-machinetype n2d-standard-2 --gcp-confidential-type sev_snp`
#
# It will create confidential instance on GCP with 1 nvme persistent disk
# and 1 local ssd disk, then check the new udev rules make effect.
Expand All @@ -26,8 +27,8 @@ NVME_INFO=$(nvme list-subsys -o json)

# verify the instance is Confidential VM
assert_confidential_vm() {
local sevlog=$(dmesg | grep SEV | head)
if [ -n "${sevlog}" ] && echo "${sevlog}" | grep "Memory Encryption Features active: AMD SEV"; then
local sevlog=$(dmesg | grep SEV-SNP | head)
if [ -n "${sevlog}" ] && echo "${sevlog}" | grep "Memory Encryption Features active: AMD SEV SEV-ES SEV-SNP"; then
ok "instance is Confidential VM"
else
fatal "instance should be Confidential VM"
Expand Down

0 comments on commit 3d42243

Please sign in to comment.