-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
4.15
-
None
-
Important
-
No
-
Proposed
-
False
-
Description of problem:
[GCP] [arm] machine stuck in provisioned status when shielded VM option is added on arm64 CPU type on GCP
Version-Release number of selected component (if applicable):
4.15.0-0.nightly-arm64-2023-12-04-194438
How reproducible:
Always
Steps to Reproduce:
Steps -
Use below yaml to create shielded VM machineset
apiVersion: machine.openshift.io/v1beta1
kind: MachineSet
metadata:
.
.
.
.
networkInterfaces:
- network: miyadav-0512v2-bvqv6-network
subnetwork: miyadav-0512v2-bvqv6-worker-subnet
projectID: openshift-qe
region: us-central1
serviceAccounts:
- email: miyadav-0512v2-bvqv6-w@openshift-qe.iam.gserviceaccount.com
scopes:
- https://www.googleapis.com/auth/cloud-platform
shieldedInstanceConfig:
integrityMonitoring: Enabled
secureBoot: Enabled
virtualizedTrustedPlatformModule: Enabled
tags:
- miyadav-0512v2-bvqv6-worker
userDataSecret:
name: worker-user-data
zone: us-central1-b
taints:
- effect: NoSchedule
key: mapi
value: mapi_test
status:
fullyLabeledReplicas: 1
observedGeneration: 2
replicas: 1
[miyadav@miyadav arm64gcpsheilded]$ oc get machines NAME PHASE TYPE REGION ZONE AGE machineset-57438-wgpxm Provisioned t2a-standard-4 us-central1 us-central1-b 57m miyadav-0512v2-bvqv6-master-0 Running t2a-standard-4 us-central1 us-central1-a 103m miyadav-0512v2-bvqv6-master-1 Running t2a-standard-4 us-central1 us-central1-b 103m miyadav-0512v2-bvqv6-master-2 Running t2a-standard-4 us-central1 us-central1-f 103m miyadav-0512v2-bvqv6-worker-a-fwsv4 Running t2a-standard-4 us-central1 us-central1-a 95m miyadav-0512v2-bvqv6-worker-a-gz9dh Provisioned t2a-standard-4 us-central1 us-central1-a 42m miyadav-0512v2-bvqv6-worker-b-7n7sw Running t2a-standard-4 us-central1 us-central1-b 95m miyadav-0512v2-bvqv6-worker-f-w4c2x Running t2a-standard-4 us-central1 us-central1-f 95m
Actual results:
machine stuck in provisioned status
Expected results:
machine in running status with node attached to it
Additional info: No specific errors in logs and no csrs are pending
https://drive.google.com/file/d/1WCemi7YbdyBv_sImQxKtC0nangRf4AU4/view?usp=sharing
- duplicates
-
-
- ASSIGNED
-
