You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[root@boron ~]# echo '{"image_uuid": "2d8225e4-11e8-11eb-903a-c7c8880e45de"}' | vmadm reprovision 421330fc-5325-cb18-b42a-ab2c194c479f
Failed to reprovision VM 421330fc-5325-cb18-b42a-ab2c194c479f: cannot support reprovision with non-standard "zones/data/smtest" dataset
This might be the result of some work done to allow datasets to be added to zones for the nfs in zone server. Looks like it blocks reprovision, I don't think it should, external datasets no longer get destroyed when destorying a vm. So repsovision should also leave them intact and just do what it normally does.
The text was updated successfully, but these errors were encountered:
@sjorge So this is basically an enhancement request, since it currently operates as intended. My point of view on this would be that datasets owned by the zone should be under the zone root. That being the case, it's unlikely that we will ever implement this. However, if you or someone else implemented it and could demonstrate it working sufficiently well, I would not be opposed to merging it.
This might be the result of some work done to allow datasets to be added to zones for the nfs in zone server. Looks like it blocks reprovision, I don't think it should, external datasets no longer get destroyed when destorying a vm. So repsovision should also leave them intact and just do what it normally does.
The text was updated successfully, but these errors were encountered: