On 26.04.2018 12:50, Andy Fiddaman wrote:
I think this is related to permissions since promoting the dataset
would also require access to the source zone dataset..
root@zone2:~# zfs promote rpool/zone/zone2/ROOT/zbe-2
cannot promote 'rpool/zone/zone2/ROOT/zbe-2': dataset does not
exist
It seems that if you go to the GZ and create and activate a BE there,
then
it works from then on.
r151026# beadm create test
Created successfully
r151026# beadm activate test
Activated successfully
r151026# beadm destroy -F test
Destroyed successfully
r151026# zlogin zone2
root@zone2:~# beadm create zbe-2
Created successfully
root@zone2:~# beadm activate zbe-2
Activated successfully
but no longer in the clone source zone...
Did this ever work? It seems that when the zone datasets are related
like
this then you need to stick to managing BEs in the GZ.
Andy
I don't know. Should it be somehow documented or restricted (like - no
BE support in cloned zone)?
Is it worth to open issue about it?
---
System Administrator of Southern Federal University Computer Center
------------------------------------------
illumos: illumos-discuss
Permalink:
https://illumos.topicbox.com/groups/discuss/discussions/T00ccd97df9cb1d97-M437b327bf0674406ac4a18fd
Delivery options: https://illumos.topicbox.com/groups
