Yes the plan is to go to 11.2 - I got the 11.1 update to work on both global and non global 11.0 system. The thing is I did so much stuff I'm still not clear on the procedure - mainly on how to get the repository to be seen by the zone - when I got the update to finally work the zone had a pkg publisher of an http localhost:1008/sorlairs/version (I assume) it was a long string of numbers... well I did get it to work but not sure how I did it... Next step is to update to 11.2 tomorrow. I will post output of what you requested if I have trouble with that. I did have to download a pre-update iso and combine it with 11.0 repo to do the first part of update - then I had to run pkg install pkg/package after that with 11.1 repo configured and that's when it wouldn't connect to the zone... kept failing with https connection errors... I went back and looked at 11.1 docs and I configured a sharenfs for the repo and also configured application/pkg/server. After I did all that I got pkg install package/pkg to run. Here is the application/pkg/server steps I followed:
This service was in maintenance when I checjed it after configuration.. i rebooted system and it came back disabled.. I enabled it and it went online - after that I was able to install package/pkg and update both global and non global zone.
$ svccfg -s application/pkg/server setprop pkg/inst_root=/export/11.1repo
$ svccfg -s application/pkg/server setprop pkg/readonly=true
Check your work:
$ svcprop -p pkg/inst_root application/pkg/server
/export/repoSolaris11
Use pkg.depotd to serve the repository to clients. By default, pkg.depotd listens for connections on port 80. You can change the port by resetting the pkg/port property.
$ svccfg -s application/pkg/server setprop pkg/port=port_number
Start the Repository Service
Restart the pkg.depotd repository service.
$ svcadm refresh application/pkg/server
$ svcadm enable application/pkg/server
Here are the NFS share steps I followed:
root@suntest:/var/tmp/11.1repo# zfs create -o mountpoint=/export/11-1repo rpool/export/11-1repo
cannot create 'rpool/export/11-1repo': dataset already exists
root@suntest:/var/tmp/11.1repo# zfs set share=name=s11-1repo,path=/export/11-1repo,prot=nfs rpool/export/11-1repo
name=s11-1repo,path=/export/11-1repo,prot=nfs
root@suntest:/var/tmp/11.1repo# zfs set sharenfs=on rpool/export/11-1repo
root@suntest:/var/tmp/11.1repo# grep repo /etc/dfs/sharetab
/export/11-1repo s11-1repo nfs sec=sys,rw
root@usphlsuntest:/var/tmp/11.1repo#
Make sure sharenfs is on:
root@suntest:/var/tmp/11.1repo# zfs get sharenfs rpool/export/11-1repo
NAME PROPERTY VALUE SOURCE
rpool/export/11-1repo sharenfs on local
root@suntest:/var/tmp/11.1repo#
Here is the error I was getting before I performed the above...
root@suntest:/var/tmp/pre-upgrade# pkg install /package/pkg
Recursing into linked image: zone:testzone
Returning from linked image: zone:testzone
Packages to remove: 1
Create boot environment: No
Create backup boot environment: No
Recursing into linked image: zone:testzone
Returning from linked image: zone:testzone
pkg: install failed (linked image exception(s)):
A 'sync-linked' operation failed for child 'zone:testzone' with an unexpected
return value of 1 and the following error message:
pkg: 0/1 catalogs successfully updated:
Unable to contact valid package repository
Encountered the following error(s):
Unable to contact any configured publishers.
This is likely a network configuration problem.
1: Framework error: code: 7 reason: couldn't connect to host
I can't put URLs in my message the the error is unable to connect to localhost 1008 etc...
Any Idea what I did to get it to work?
---------- Post updated at 12:01 PM ---------- Previous update was at 11:55 AM ----------
PS - after all this and getting the systems to 11.1 I was able to install a new 11.1 zone using the 11-1repo - so it looks like the repo is working OK now - my worries are when I unset that repo and configure the 11.2 repo I will have the same issues. I'd like to know what I'm doing with this stuff but docs online are barbaric... haha
By the way thanks a lot for taking an interest and trying to help me out...
Here is the info you asked for..
root@suntest:~# pkg info entire
Name: entire
Summary: Incorporation to lock all system packages to the same build
Description: This package constrains system package versions to the same
build. WARNING: Proper system update and correct package
selection depend on the presence of this incorporation.
Removing this package will result in an unsupported system.
Category: Meta Packages/Incorporations
State: Installed
Publisher: solaris
Version: 0.5.11
Build Release: 5.11
Branch: 0.175.1.0.0.24.2
Packaging Date: September 19, 2012 07:01:35 PM
Size: 5.46 kB
FMRI: pkg://solaris/entire@0.5.11,5.11-0.175.1.0.0.24.2:20120919T190135Z
root@usphlsuntest:~# pkg publisher
PUBLISHER TYPE STATUS P LOCATION
solaris origin online F file:///export/11-1repo/
root@suntest:~# pkg list -af entire
NAME (PUBLISHER) VERSION IFO
entire 0.5.11-0.175.1.0.0.24.2 i--
root@suntest:~# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / solaris shared
1 bob running /rpool/bob solaris10 excl
2 testzone running /zones/testzone solaris excl
3 testzone11-1 running /zones/testzone11-1 solaris excl
- usphlvis01 configured /zones/usphlvis01 solaris10 excl
root@suntest:~#