jetpack init doesn't check for correct initialization of ZFS dataset

[szakharchenko]

I misread the documentation and thought that if I wanted a custom ZFS dataset location, I should create the dataset manually, enter it into configuration and run jetpack init later. jetpack init responded with 'Host already initialized'. However, jetpack ... run ... results in

cannot create 'mycustompoolname/jetpack/images/...': parent does not exist
cannot open 'mycustompoolname/jetpack/images/...: dataset does not exist
panic: Not found

because mycustompoolname/jetpack/images doesn't exist. zfs destroy/jetpack init solved this, but I think jetpack init should check for the existence of necessary child datasets.