Actions
Bug #14033
openzonecfg man page example 1 fails without explicit set of ip-type=shared
Status:
New
Priority:
Normal
Assignee:
-
Category:
manpage - manual pages
Start date:
Due date:
% Done:
0%
Estimated time:
Difficulty:
Medium
Tags:
zonecfg
Gerrit CR:
Description
Example 1 in man zonecfg
does not seem to work without explicitly setting ip-type=shared
.
Failure as specified
root@rylu:/home/ry# zonecfg -z myzone3 myzone3: No such zone configured Use 'create' to begin configuring a new zone. zonecfg:myzone3> create zonecfg:myzone3> set zonepath=/tmp/myzone3 zonecfg:myzone3> set autoboot=true zonecfg:myzone3> add net zonecfg:myzone3:net> set address=192.168.0.1/24 zonecfg:myzone3:net> set physical=eri0 zonecfg:myzone3:net> end zonecfg:myzone3> add net zonecfg:myzone3:net> set address=192.168.1.2/24 zonecfg:myzone3:net> set physical=eri0 zonecfg:myzone3:net> end A net resource with the physical 'eri0', and address '192.168.1.2/24' already exists. zonecfg:myzone3:net> exit Resource incomplete; really quit (y/[n])? y net: address cannot be specified for an exclusive IP type resource specification incomplete Zone myzone3 failed to verify myzone3: Invalid argument Configuration not saved; really quit (y/[n])? y
Works inserting ip-type=shared
root@rylu:/home/ry# zonecfg -z myzone3 myzone3: No such zone configured Use 'create' to begin configuring a new zone. zonecfg:myzone3> create zonecfg:myzone3> set ip-type=shared zonecfg:myzone3> set zonepath=/tmp/myzone3 zonecfg:myzone3> set autoboot=true zonecfg:myzone3> add net zonecfg:myzone3:net> set address=192.168.0.1/24 zonecfg:myzone3:net> set physical=eri0 zonecfg:myzone3:net> end zonecfg:myzone3> add net zonecfg:myzone3:net> set address=192.168.1.2/24 zonecfg:myzone3:net> set physical=eri0 zonecfg:myzone3:net> end zonecfg:myzone3> exit
Elsewhere in the zonecfg
man page is the statement
global: ip-type A zone can either share the IP instance with the global zone, which is the default, or have its own exclusive instance of IP. This property takes the values shared and exclusive.
which seems to suggest that the example as specified should work without having to explicitly set ip-type=shared
. But it's not totally clear to me if this is a bug in the example, the description of the default in the man page, or the zonecfg
implementation.
Just to make sure this was not due to some persistent configuration I have on my development machine, I did spin up a fresh OmniOS VM from the omnios-r151038.iso installer to test on a clean install. This behavior happens on a clean install as well.
No data to display
Actions