13:43:25 <nikolam> tsoome_, I had an issue with piadm on SmartOS few weeks ago. I decided to remove piadm from the pool and boot from USB flash. I had latest and some previous snapshots in piadm and then removed it from booting from hard drive. 
13:44:07 <nikolam> Problem arised when USB flash was not easily bootable (SD card in USB reader) and won't boot every time on hardware. 
13:44:30 <nikolam> So I decided to bring back booting from the pool again, after booting from the flash. 
13:45:42 <nikolam> But, installing back and booting from the pool didn't work, because same-named snapshot were still available on disk, since installation on the pool needs to set the snapshot 
13:47:07 <nikolam> So I needed to activate older snapshot and then I could remove latest snapshot and only after that I could bring back pool to bootable state again with the latest snapshot 
13:48:33 <nikolam> So maybe such situation when there is already latest snapshot on the pool and one can't get pool bootable again, could be avoided ? (so that someone less savvy won't end up with inability to boot form pool) 
17:26:25 <natefoo> I'm trying to create an LX zone from the latest Rocky 9 image and am getting these failures during provisioning which (I think?) are causing a provisioning timeout: https://gist.github.com/natefoo/b8b4bf368beda3aad75402b5cc47dfd0
17:26:37 <natefoo> Is this an image problem?
17:27:56 <natefoo> (latest Rocky 9 LX image on images.smartos.org, not one I've built myself)
18:32:18 <natefoo> Well that's not the cause - I created a centos-7 zone, it has the same errors but boots fine.
22:31:04 <bahamat> natefoo: A provision is considered successful when /var/svc/provisioning is renamed to /var/svc/provision_success. If something is delaying or preventing that, you'll end up with provision failures.
22:31:31 <bahamat> You can "cheat" this by moving it yourself early in the user-script.