I am not sure if I am missing a step or if this is a bug, but when I create a unified archive (recovery and clone) of an individual, non-global zone, and that zone has multiple BE's then the archive does not contain the entire zone (size is way too small). I am also not able to install a new zone with the archive due to it failing out with the following message:
_setup_bootenv rename failed too many times
Zone installation log file:
| 2016-06-29 17:59:40,270 InstallationLogger DEBUG | Executing: ['/usr/sbin/zfs', 'rename', 'rpool/template-area/rpool/ROOT/solaris-2', 'rpool/template-area/rpool/ROOT/solaris-1-recovery'] |
| 2016-06-29 17:59:40,291 InstallationLogger DEBUG | cannot open 'rpool/template-area/rpool/ROOT/solaris-2': filesystem does not exist |
| 2016-06-29 17:59:40,292 InstallationLogger.generated-transfer-23738-1 DEBUG | _setup_bootenv: failed: cannot open 'rpool/template-area/rpool/ROOT/solaris-2': filesystem does not exist |
The odd thing is that solaris-2 BE/filesystem would not even exist since this is a brand new zone being installed and solaris-2 isn't even in my unified archive.
Unified archive creation and installing new zones with the archive works great as long as the zone has only ever had a single BE. As soon as I update the zone and a new BE is created and activated then archive creation stops working.
I have tried this on two different Solaris 11 machines with the same results.
Any thoughts?
Thanks,
Will