Re: [OmniOS-discuss] LX zone empty error messages

2016-09-23 Thread Dan McDonald 

> On Sep 22, 2016, at 10:08 PM, Michael Talbott  wrote:
> 
> Ah HA! So, I did not have a zfs dataset at /zones. I created one, retried the 
> process and the same ominous message popped up :( Then I rebooted and tried 
> again, and success! Hurray! Now I can carry on with my testing :)

Followup, as much for me as for you,

The failure isn't more verbose because the zones-common function 
get_zonepath_ds() requires a variable be set by the brand script, which our LX 
zone code does not, currently.  We need to fix that, so instead of:

ERROR:

we can instead print something like what the ipkg/lipkg brand does:

ERROR:  the zonepath must be a ZFS dataset.
The parent directory of the zonepath must be a ZFS dataset so that the
zonepath ZFS dataset can be created properly.

Now I'm beginning to understand why the brand scripts of ipkg were brought into 
Oracle's version of illumos-gate for Oracle Solaris.  Some of the ipkg/lipkg 
items can/should be more common across other brands as well.

Until that day, however, I will make sure the lx_install script has a proper 
$f_no_ds variable set.

Thanks again, Michael!
Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] LX zone empty error messages

2016-09-22 Thread Dan McDonald 

> On Sep 22, 2016, at 10:08 PM, Michael Talbott  wrote:
> 
> Ah HA! So, I did not have a zfs dataset at /zones. I created one, retried the 
> process and the same ominous message popped up :( Then I rebooted and tried 
> again, and success! Hurray! Now I can carry on with my testing :)

Sounds like, however, there needs to be better diagnostics somewhere.  Thanks 
for adding that to the tests.  (I suspect the Joyent-originated brand code 
assumes /zones always exists as a ZFS dataset, as it does in all SmartOS 
deployments.)

Thanks!
Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] LX zone empty error messages

2016-09-22 Thread Michael Talbott 
Ah HA! So, I did not have a zfs dataset at /zones. I created one, retried the 
process and the same ominous message popped up :( Then I rebooted and tried 
again, and success! Hurray! Now I can carry on with my testing :)

Thanks!


> On Sep 22, 2016, at 6:42 PM, Dan McDonald  wrote:
> 
> 
>> On Sep 22, 2016, at 9:07 PM, Michael Talbott  wrote:
> 
> 
> 
>> And for giggles, I gunzipped the file and tried it with the unzipped 
>> version. Same deal. Any ideas?.. I'm running this as a VM for testing before 
>> I put it on bare metal. Could that be the issue or did I miss something 
>> critical above? I wish the error message said *something* ;) Any other way 
>> of getting some extra verbose output to see where it's dying?
> 
> Weird.
> 
> One thing you can try is not only to uninstall the zone, but also delete its 
> configuration (after exporting it) and then re-create it.
> 
> I'm trying to reproduce your bug right now.  I got this:
> 
> zonecfg:lx2> export
> create -b
> set zonepath=/zones/lx2
> set brand=lx
> set autoboot=false
> set ip-type=exclusive
> add net
> set physical=lx2
> add property (name=gateway,value="x.y.z.1")
> add property (name=primary,value="true")
> add property (name=ips,value="x.y.z.246/24")
> end
> add attr
> set name=dns-domain
> set type=string
> set value=x.y.z.net
> end
> add attr
> set name=resolvers
> set type=string
> set value=x.y.z.1
> end
> add attr
> set name=kernel-version
> set type=string
> set value=2.6.32
> end
> zonecfg:lx2> exit
> # zoneadm list -cv
>  ID NAME STATUS PATH   BRANDIP
>   0 global   running/  ipkg shared
>   4 lx1  running/zones/lx1 lx   excl  
>   - tz2  installed  /zones/tz2 lipkgexcl  
>   - lx0  installed  /zones/lx0 lx   excl  
>   - lx2  configured /zones/lx2 lx   excl  
> # zoneadm -z lx2 install -s /rpool/lx-stuff/joyent-images/centos6.gz 
> WARNING: skipping network interface 'lx2': object not found
> A ZFS file system has been created for this zone.
> # zoneadm list -cv
>  ID NAME STATUS PATH   BRANDIP
>   0 global   running/  ipkg shared
>   4 lx1  running/zones/lx1 lx   excl  
>   - tz2  installed  /zones/tz2 lipkgexcl  
>   - lx0  installed  /zones/lx0 lx   excl  
>   - lx2  installed  /zones/lx2 lx   excl  
> # 
> 
> 
> Okay... dumb question:  is "/zones" on your box its own ZFS dataset?
> 
> # zfs list | grep /zones
> rpool/zones8.57G  34.6G20K  /zones
> rpool/zones/lx01.33G  34.6G  1.87G  /zones/lx0
> rpool/zones/lx11.86G  34.6G  1.81G  /zones/lx1
> rpool/zones/lx2 787M  34.6G   787M  /zones/lx2
> rpool/zones/tz24.62G  34.6G  20.5K  /zones/tz2
> rpool/zones/tz2/ROOT   4.62G  34.6G19K  legacy
> rpool/zones/tz2/ROOT/zbe-142.32M  34.6G  1.31G  legacy
> rpool/zones/tz2/ROOT/zbe-152.50M  34.6G  1.24G  legacy
> rpool/zones/tz2/ROOT/zbe-16 100K  34.6G  1.11G  legacy
> rpool/zones/tz2/ROOT/zbe-171.89M  34.6G  1.25G  legacy
> rpool/zones/tz2/ROOT/zbe-211.89M  34.6G  1.26G  legacy
> rpool/zones/tz2/ROOT/zbe-222.55M  34.6G  1.26G  legacy
> rpool/zones/tz2/ROOT/zbe-2510.4M  34.6G  1.12G  legacy
> rpool/zones/tz2/ROOT/zbe-29  73K  34.6G  1.12G  legacy
> rpool/zones/tz2/ROOT/zbe-3028.8M  34.6G  1.12G  legacy
> rpool/zones/tz2/ROOT/zbe-3118.5M  34.6G  1.11G  legacy
> rpool/zones/tz2/ROOT/zbe-324.55G  34.6G  1.13G  legacy
> rpool/zones/tz2/ROOT/zbe-3368.5K  34.6G  1.13G  legacy
> # 
> 
> 
> It should be, and MAYBE that's causing your problem?
> 
> Dan
> 

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] LX zone empty error messages

2016-09-22 Thread Dan McDonald 

> On Sep 22, 2016, at 9:07 PM, Michael Talbott  wrote:



> And for giggles, I gunzipped the file and tried it with the unzipped version. 
> Same deal. Any ideas?.. I'm running this as a VM for testing before I put it 
> on bare metal. Could that be the issue or did I miss something critical 
> above? I wish the error message said *something* ;) Any other way of getting 
> some extra verbose output to see where it's dying?

Weird.

One thing you can try is not only to uninstall the zone, but also delete its 
configuration (after exporting it) and then re-create it.

I'm trying to reproduce your bug right now.  I got this:

zonecfg:lx2> export
create -b
set zonepath=/zones/lx2
set brand=lx
set autoboot=false
set ip-type=exclusive
add net
set physical=lx2
add property (name=gateway,value="x.y.z.1")
add property (name=primary,value="true")
add property (name=ips,value="x.y.z.246/24")
end
add attr
set name=dns-domain
set type=string
set value=x.y.z.net
end
add attr
set name=resolvers
set type=string
set value=x.y.z.1
end
add attr
set name=kernel-version
set type=string
set value=2.6.32
end
zonecfg:lx2> exit
# zoneadm list -cv
  ID NAME STATUS PATH   BRANDIP
   0 global   running/  ipkg shared
   4 lx1  running/zones/lx1 lx   excl  
   - tz2  installed  /zones/tz2 lipkgexcl  
   - lx0  installed  /zones/lx0 lx   excl  
   - lx2  configured /zones/lx2 lx   excl  
# zoneadm -z lx2 install -s /rpool/lx-stuff/joyent-images/centos6.gz 
WARNING: skipping network interface 'lx2': object not found
A ZFS file system has been created for this zone.
# zoneadm list -cv
  ID NAME STATUS PATH   BRANDIP
   0 global   running/  ipkg shared
   4 lx1  running/zones/lx1 lx   excl  
   - tz2  installed  /zones/tz2 lipkgexcl  
   - lx0  installed  /zones/lx0 lx   excl  
   - lx2  installed  /zones/lx2 lx   excl  
# 


Okay... dumb question:  is "/zones" on your box its own ZFS dataset?

# zfs list | grep /zones
rpool/zones8.57G  34.6G20K  /zones
rpool/zones/lx01.33G  34.6G  1.87G  /zones/lx0
rpool/zones/lx11.86G  34.6G  1.81G  /zones/lx1
rpool/zones/lx2 787M  34.6G   787M  /zones/lx2
rpool/zones/tz24.62G  34.6G  20.5K  /zones/tz2
rpool/zones/tz2/ROOT   4.62G  34.6G19K  legacy
rpool/zones/tz2/ROOT/zbe-142.32M  34.6G  1.31G  legacy
rpool/zones/tz2/ROOT/zbe-152.50M  34.6G  1.24G  legacy
rpool/zones/tz2/ROOT/zbe-16 100K  34.6G  1.11G  legacy
rpool/zones/tz2/ROOT/zbe-171.89M  34.6G  1.25G  legacy
rpool/zones/tz2/ROOT/zbe-211.89M  34.6G  1.26G  legacy
rpool/zones/tz2/ROOT/zbe-222.55M  34.6G  1.26G  legacy
rpool/zones/tz2/ROOT/zbe-2510.4M  34.6G  1.12G  legacy
rpool/zones/tz2/ROOT/zbe-29  73K  34.6G  1.12G  legacy
rpool/zones/tz2/ROOT/zbe-3028.8M  34.6G  1.12G  legacy
rpool/zones/tz2/ROOT/zbe-3118.5M  34.6G  1.11G  legacy
rpool/zones/tz2/ROOT/zbe-324.55G  34.6G  1.13G  legacy
rpool/zones/tz2/ROOT/zbe-3368.5K  34.6G  1.13G  legacy
# 


It should be, and MAYBE that's causing your problem?

Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss