-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
Description of problem:
MicroShift cluster bot may fail due to partitioning error
Version-Release number of selected component (if applicable):
main
How reproducible:
Depending on the AWS instance type
Steps to Reproduce:
1. Start cluster on t3 instance
Actual results:
+ device=/dev/xvdc + [[ t3 =~ .*g.* ]] + [[ t3 =~ t3.* ]] + device=/dev/nvme1n1 + ssh ec2-user@54.214.96.202 'lsblk ; sudo dnf install -y lvm2 && sudo pvcreate /dev/nvme1n1 && sudo vgcreate rhel /dev/nvme1n1' Warning: Permanently added '54.214.96.202' (ED25519) to the list of known hosts. NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS nvme0n1 259:0 0 10G 0 disk nvme1n1 259:1 0 200G 0 disk ├─nvme1n1p1 259:2 0 1M 0 part ├─nvme1n1p2 259:3 0 200M 0 part /boot/efi ├─nvme1n1p3 259:4 0 600M 0 part /boot └─nvme1n1p4 259:5 0 199.2G 0 part / Updating Subscription Management repositories. ... ... Complete! Cannot use /dev/nvme1n1: device is partitioned {"component":"entrypoint","error":"wrapped process failed: exit status 5","file":"k8s.io/test-infra/prow/entrypoint/run.go:84","func":"k8s.io/test-infra/prow/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2023-12-25T01:26:40Z"}
Additional info: