Bug Report
Description
I’m trying to run the new v1.12 release using NoCloud ISO metadata.
It looks like Talos does not detect the cidata partition.
I haven’t investigated this deeply yet, but you may already know which recent changes could have affected this behavior.
Logs
# file /var/lib/vz/template/iso/user-data-20000.iso
/var/lib/vz/template/iso/user-data-20000.iso: ISO 9660 CD-ROM filesystem data 'cidata'
# get disks --insecure
NODE NAMESPACE TYPE ID VERSION SIZE READ ONLY TRANSPORT ROTATIONAL WWID MODEL SERIAL
runtime Disk loop0 2 180 kB true
runtime Disk loop1 2 4.1 kB true
runtime Disk loop2 2 111 kB true
runtime Disk loop3 2 75 MB true
runtime Disk sda 2 35 GB false virtio QEMU HARDDISK
runtime Disk sr0 2 53 kB false sata true QEMU DVD-ROM # get discoveredvolumes --insecure
NODE NAMESPACE TYPE ID VERSION TYPE SIZE DISCOVERED LABEL PARTITIONLABEL
runtime DiscoveredVolume loop0 1 disk 180 kB squashfs
runtime DiscoveredVolume loop2 1 disk 111 kB squashfs
runtime DiscoveredVolume loop3 1 disk 75 MB squashfs
runtime DiscoveredVolume sda 1 disk 35 GB gpt
runtime DiscoveredVolume sda2 1 partition 1.0 MB BIOS
runtime DiscoveredVolume sda3 1 partition 2.1 GB xfs BOOT BOOT
runtime DiscoveredVolume sda4 1 partition 1.0 MB talosmeta METAdmesg:
[ 1.847254] scsi host0: ahci
[ 1.847885] scsi host1: ahci
[ 1.852982] scsi host2: ahci
[ 1.853678] scsi host3: ahci
[ 1.854381] scsi host4: ahci
[ 1.855134] scsi host5: ahci
[ 1.855743] ata1: SATA max UDMA/133 abar m4096@0xfea0a000 port 0xfea0a100 irq 28 lpm-pol 1
[ 1.856736] ata2: SATA max UDMA/133 abar m4096@0xfea0a000 port 0xfea0a180 irq 28 lpm-pol 1
[ 1.857732] ata3: SATA max UDMA/133 abar m4096@0xfea0a000 port 0xfea0a200 irq 28 lpm-pol 1
[ 1.858732] ata4: SATA max UDMA/133 abar m4096@0xfea0a000 port 0xfea0a280 irq 28 lpm-pol 1
[ 1.861088] ata5: SATA max UDMA/133 abar m4096@0xfea0a000 port 0xfea0a300 irq 28 lpm-pol 1
[ 1.864156] ata6: SATA max UDMA/133 abar m4096@0xfea0a000 port 0xfea0a380 irq 28 lpm-pol 1
[ 1.870107] ACPI: \_SB_.GSIE: Enabled at IRQ 20
[ 1.921563] virtio_scsi virtio2: 1/0/0 default/read/poll queues
[ 1.923205] scsi host6: Virtio SCSI HBA
[ 1.927662] scsi 6:0:0:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 1.933653] sd 6:0:0:0: Power-on or device reset occurred
[ 1.934462] sd 6:0:0:0: [sda] 69206016 512-byte logical blocks: (35.4 GB/33.0 GiB)
[ 1.935423] sd 6:0:0:0: [sda] Write Protect is off
[ 1.936226] sd 6:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 1.937528] sd 6:0:0:0: Attached scsi generic sg0 type 0
[ 2.163416] sda: sda2 sda3 sda4
[ 2.164293] sd 6:0:0:0: [sda] Attached SCSI disk
[ 2.174506] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.175816] ata2.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100
[ 2.176632] ata2.00: applying bridge limits
[ 2.177254] ata2.00: configured for UDMA/100
[ 2.178011] ata3: SATA link down (SStatus 0 SControl 300)
[ 2.178844] ata1: SATA link down (SStatus 0 SControl 300)
[ 2.179690] scsi 1:0:0:0: CD-ROM QEMU QEMU DVD-ROM 2.5+ PQ: 0 ANSI: 5
[ 2.181450] ata4: SATA link down (SStatus 0 SControl 300)
[ 2.182483] ata5: SATA link down (SStatus 0 SControl 300)
[ 2.183316] ata6: SATA link down (SStatus 0 SControl 300)
[ 2.200070] sr 1:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[ 2.200930] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 2.228889] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 2.230515] iTCO_vendor_support: vendor-support=0
[ 2.233990] iTCO_wdt iTCO_wdt.1.auto: Found a ICH9 TCO device (Version=2, TCOBASE=0x0660)
[ 2.235634] iTCO_wdt iTCO_wdt.1.auto: initialized. heartbeat=30 sec (nowayout=0)
[ 2.472455] [talos] service[containerd](Running): Health check successful
[ 2.473419] [talos] task startContainerd (5/5): done, 1.027683493s
[ 2.486845] [talos] service[machined](Running): Health check successful
[ 2.487721] [talos] task startMachined (2/5): done, 1.034190663s
[ 2.488479] [talos] service[syslogd](Preparing): Running pre state
[ 2.489252] [talos] service[syslogd](Preparing): Creating service runner
[ 2.490117] [talos] service[syslogd](Running): Service started as goroutine
[ 2.507879] [talos] volume status {"component": "controller-runtime", "controller": "block.VolumeManagerController", "volume": "META", "phase": "waiting -> ready", "locati}
[ 2.510153] [talos] service[auditd](Running): Health check successful
[ 3.491283] [talos] service[syslogd](Running): Health check successful
[ 8.095209] [talos] service[udevd](Running): Health check successful
[ 8.096300] [talos] task startUdevd (1/5): done, 6.646747701s
[ 8.097102] [talos] phase earlyServices (2/9): done, 6.652053366s
[ 8.097932] [talos] phase usb (3/9): 1 tasks(s)
[ 8.098591] [talos] task waitForUSB (1/1): starting
[ 8.099346] [talos] task waitForUSB (1/1): waiting 1 second(s) for USB storage
[ 8.108109] 8021q: adding VLAN 0 to HW filter on device eth0
[ 8.109554] 8021q: adding VLAN 0 to HW filter on device eth1
[ 8.125297] [talos] volume status {"component": "controller-runtime", "controller": "block.VolumeManagerController", "volume": "STATE", "phase": "waiting -> missing"}
[ 8.127520] [talos] volume status {"component": "controller-runtime", "controller": "block.VolumeManagerController", "volume": "platform/cidata/config", "phase": "waiting }
[ 8.129519] [talos] volume status {"component": "controller-runtime", "controller": "block.VolumeManagerController", "volume": "platform/cidata/config", "phase": "missing }
[ 8.143192] [talos] setting resolvers {"component": "controller-runtime", "controller": "network.ResolverSpecController", "resolvers": ["172.16.0.128"], "searchDomains": [}
[ 8.147193] [talos] assigned address {"component": "controller-runtime", "controller": "network.AddressSpecController", "address": "172.16.0.64/24", "link": "eth1"}
[ 8.150003] [talos] created route {"component": "controller-runtime", "controller": "network.RouteSpecController", "destination": "default", "gateway": "172.16.0.128", "ta}
[ 9.101292] [talos] task waitForUSB (1/1): done, 1.00266384s
[ 9.102109] [talos] phase usb (3/9): done, 1.004174563s
[ 9.102770] [talos] phase meta (4/9): 1 tasks(s)
[ 9.103396] [talos] task reloadMeta (1/1): starting
[ 9.125168] [talos] adjusting time (slew) by 254.911698ms via 162.159.200.1, state TIME_OK, status STA_PLL | STA_NANO {"component": "controller-runtime", "controller": "ti}
[ 9.204241] [talos] META: loading from /dev/sda4
[ 9.206020] [talos] META: loaded 0 keys
[ 9.206669] [talos] task reloadMeta (1/1): done, 103.270979ms
[ 9.207436] [talos] phase meta (4/9): done, 104.668032ms
[ 9.208127] [talos] phase dashboard (6/9): 1 tasks(s)
[ 9.208795] [talos] task startDashboard (1/1): starting
[ 9.209491] [talos] service[dashboard](Starting): Starting service
[ 9.210269] [talos] service[dashboard](Waiting): Waiting for service "machined" to be "up", file "/system/run/machined/machine.sock" to exist
[ 9.211850] [talos] task startDashboard (1/1): done, 3.055056ms
[ 9.212609] [talos] phase dashboard (6/9): done, 4.481399ms
[ 9.213328] [talos] phase config (9/9): 1 tasks(s)
[ 9.213976] [talos] task loadConfig (1/1): starting
[ 9.214644] [talos] service[dashboard](Preparing): Running pre state
[ 9.216421] [talos] downloading config {"component": "controller-runtime", "controller": "config.AcquireController", "platform": "nocloud"}
[ 9.218051] [talos] volume status {"component": "controller-runtime", "controller": "block.VolumeManagerController", "volume": "platform/cidata/config", "phase": "waiting }
[ 9.220635] [talos] service[dashboard](Preparing): Creating service runner
[ 9.222402] [talos] volume status {"component": "controller-runtime", "controller": "block.VolumeManagerController", "volume": "platform/cidata/config", "phase": "missing }
[ 9.226567] [talos] entering maintenance service {"component": "controller-runtime", "controller": "config.AcquireController"}
[ 9.230294] [talos] this machine is reachable at: {"component": "controller-runtime", "controller": "runtime.MaintenanceServiceController"}
[ 9.234171] [talos] 172.16.0.64 {"component": "controller-runtime", "controller": "runtime.MaintenanceServiceController"}
[ 9.236491] [talos] server certificate issued {"component": "controller-runtime", "controller": "runtime.MaintenanceServiceController", "fingerprint": "bX0nAI6M4JPaydtUgpm}
[ 9.240319] [talos] upload configuration using talosctl: {"component": "controller-runtime", "controller": "runtime.MaintenanceServiceController"}
[ 9.243244] [talos] talosctl apply-config --insecure --nodes 172.16.0.64 --file <config.yaml> {"component": "controller-runtime", "controller": "runtime.MaintenanceServic}
[ 9.246982] [talos] service[dashboard](Running): Process Process(["/sbin/dashboard"]) started with PID 2292Environment
- Talos version: 1.12.0
- Kubernetes version: [
kubectl version]
- Platform: nocloud
Bug Report
Description
I’m trying to run the new v1.12 release using NoCloud ISO metadata.
It looks like Talos does not detect the
cidatapartition.I haven’t investigated this deeply yet, but you may already know which recent changes could have affected this behavior.
Logs
# get discoveredvolumes --insecure NODE NAMESPACE TYPE ID VERSION TYPE SIZE DISCOVERED LABEL PARTITIONLABEL runtime DiscoveredVolume loop0 1 disk 180 kB squashfs runtime DiscoveredVolume loop2 1 disk 111 kB squashfs runtime DiscoveredVolume loop3 1 disk 75 MB squashfs runtime DiscoveredVolume sda 1 disk 35 GB gpt runtime DiscoveredVolume sda2 1 partition 1.0 MB BIOS runtime DiscoveredVolume sda3 1 partition 2.1 GB xfs BOOT BOOT runtime DiscoveredVolume sda4 1 partition 1.0 MB talosmeta METAdmesg:
Environment
kubectl version]