hrm.. i know it's not officially supported, and it's been a while since i've done it (so might be forgetting something), but if I want to reprovision a instance, I should just be able to update the config and vmadm reprovision UUID -f cfg.json, right? it's saying that only lx and docker zone types support it

which seems wrong (IIRC, reprovision was used internally to upgrade instances which would be native zones)

as far as I learnt, there is no limitations to lx/docker brand, so your idea should be correct

oh hrm.. i think the json had more bits in it than needed...

it's been 3ish years since I last did this, so my memory is fuzzy :)

I've not used "vmadm reprovision" but intuitively it should do that (per gemelen).

jbk: TritonDataCenter/smartos-live #1132 , another piece is in vmadm.js

Yeah... I'm still deciding if we WANT to document these. I'm leaning toward "yes, but with BIG FLASHING LIGHTS SAYING HOW THIS IS UNSUPPORTED" specifically for reasons like this.

yeah, i know it's unsupported (at least outside of Triton using it internally)

no problem from my side with that

i do wish though that wiki page from joshw on it was public

it was really useful in the past...

basically i'm updating the base lts image on all my zones to 24.4.1 in anticipation of the upcoming release

jbk: DM me which one... it might be now, or able to be made, public in the post-Joyent order.

i don't recall the url

but it basically had the steps reprovision did to help you figure out how to fix or backout if it failed mid-way

jbk -> I do this in-zone. (smartos-build{,-2,-3} have been around since Joyent. :)

Ahhh.

`zfs rollback...` and try again for me. :)

i want to say it was on mo

but not 100% sure

I remember there was a step by step walkthrough on what happens during that action

it's in sources

if i ever get free time, i need to finish writing the zfs tests for zfs alias so it can be RTIed... then could see about trying to add support.. i think it could still be done.. since it wouldn't impact existing instances, and you could control it for a given image if there's things hard coded to look for /zones/<UUID>/data

jbk... I did some changes for BHYVE zones to allow them to migrate easier (not foolproof)...

fenix OS-8518

OS-8518: Receiving a BHYVE VM fails due to premature ZFS dataset creation (Resolved)

↳ smartos.org/bugview/OS-8518

jbk : I only remember this one: gist.github.com/trentm/18520cff2b3634094d020dc425da6a19 <- "recovering from a failed reprovision"

yeah... that's i think the same one as the internal doc

i thought joshw had written it, but maybe it was trent