Zones goes to unavailable state when the server is rebooted after upgrade from 11.3 to 11.4
(Doc ID 2550313.1)
Last updated on JULY 05, 2023
Applies to:
Solaris Operating System - Version 11.4 and laterInformation in this document applies to any platform.
Server updated from 11.3 to 11.4.
After each reboot differnet zones are affected (see below).
root@global:~# zoneadm list
ID NAME STATUS PATH BRAND IP
0 global running / solaris shared
1 zone3 running /zones/zone3 solaris excl
2 zone5 running /zones/zone5 solaris excl
- zone2 installed /zones/zone2 solaris excl
- zone4 installed /zones/zone4 solaris excl
- zone1 installed /zones/zone1 solaris excl
Did the following for all zone with status "installed":
root@global:~# zoneadm -z zone2 detach
Exported zpool: zone2_rpool
Unconfigured storage resource(s) from:
lu:luname.naa.600601603b304800deadb35a4d273409
lu:luname.naa.600601606a21480067adb35adabbc959
root@global:~# zoneadm -z zone2 attach
Configured storage resource(s) from:
lu:luname.naa.600601603b304800deadb35a4d273409
lu:luname.naa.600601606a21480067adb35adabbc959
Imported zpool: zone2_rpool
Progress being logged to /var/log/zones/zoneadm.20190131T131544Z.zone2.attach
Zone BE root dataset: zone2_rpool/rpool/ROOT/solaris-4
Updating non-global zone: Linking to image /.
Updating non-global zone: Auditing packages.
No updates necessary for this image. (zone:zone2)
Updating non-global zone: Zone updated.
Result: Attach Succeeded.
Log saved in non-global zone as /zones/zone2/root/var/log/zones/zoneadm.20190131T131544Z.zone2.attach
root@global:~# init 6
global:~ $ zoneadm list
ID NAME STATUS PATH BRAND IP
0 global running / solaris shared
1 zone5 running /zones/zone5 solaris excl
2 zone2 running /zones/zone2 solaris excl
3 zone4 running /zones/zone4 solaris excl
- zone3 unavailable /zones/zone3 solaris excl
- zone1 unavailable /zones/zone1 solaris excl
Next reboot:
root@global:~# zoneadm list
ID NAME STATUS PATH BRAND IP
0 global running / solaris shared
1 zone3 running /zones/zone3 solaris excl
2 zone1 running /zones/zone1 solaris excl
- zone2 unavailable /zones/zone2 solaris excl
- zone4 unavailable /zones/zone4 solaris excl
- zone5 unavailable /zones/zone5 solaris excl
Symptoms
Server updated from 11.3 to 11.4.5
When the server is rebooted, 3 of 5 zones goes to "unavailable" state.
root@global:~# zoneadm list
ID NAME STATUS PATH BRAND IP
0 global running / solaris shared
1 zone3 running /zones/zone3 solaris excl
2 zone5 running /zones/zone5 solaris excl
- zone2 unavailable /zones/zone2 solaris excl
- zone4 unavailable /zones/zone4 solaris excl
- zone1 unavailable /zones/zone1 solaris excl
The zones could be successfully attached but after the next reboot, the zones are "unavailable" again.
After each reboot different zones are affected.
Changes
The server was updated from 11.3 to 11.4 SRU 5
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |