beadm trips over 'installed' zones
beadm's support for zones is broken in the face of zones in the 'installed' state, it tries to open their vfstab and fails, I think because the zone root isn't mounted. zones which are running, and zones which are 'configured' seem fine.
I'm unsure whether libbe should mount the zone root, or skip non-running zones (I suspect it needs to mount the zone root, since their root dataset will change to the new ZBE)
Updated by Rich Lowe over 9 years ago
- Priority changed from High to Low
Alexander asked about reproducing this, because he couldn't, and it turns out that I can't manage it either.
Things I have tried:
- A pre-existing zone, halted
- A freshly created zone, before ever booting
- A freshly created zone, waiting at sysidcfg
- A freshly created zone, booted until sysidcfg, then halted.
All of which worked. Yet last night my attempts to create a new BE to put some test bits in were failing, after creating a zone in the obvious way. I'm deeply confused.
I've dropped the priority because obviously it's non-trivial to encounter this, but I'm leaving it open because I definitely did encounter it.
Updated by Alexander Eremin over 9 years ago
I tried to reproduce this using the latest illumos build - beadm works for me in all cases.
alex@indy:$ zfs create rpool/export/zones alex@indy:$ zonecfg -z zone1 create set zonepath=/export/zones/zone1 exit alex@indy:$ zoneadm -z zone1 install alex@indy:$ zoneadm list -cv ... - zone1 installed /export/zones/zone1 ipkg shared alex@indy:$ pfexec beadm create foo Created successfully
Same for other zone states