Clearly I'm missing something about lipkg zones and pkg update. I have some recently built boxes that appear to behave, but on older (as in still 151014 but a few months back) systems the zones don't seem to follow the global zone when I run pkg update.
I utter: $ pfexec pkg update ntp openssl Packages to update: 2 Services to change: 1 Create boot environment: No Create backup boot environment: Yes Planning linked: 0/2 done; 1 working: zone:ns1 Planning linked: 1/2 done; 1 working: zone:backup2 Planning linked: 2/2 done DOWNLOAD PKGS FILES XFER (MB) SPEED Completed 2/2 442/442 7.9/7.9 1.4M/s Downloading linked: 0/2 done; 1 working: zone:ns1 Downloading linked: 1/2 done; 1 working: zone:backup2 Downloading linked: 2/2 done PHASE ITEMS Removing old actions 4/4 Installing new actions 48/48 Updating modified actions 442/442 Updating package state database Done Updating package cache 2/2 Updating image state Done Creating fast lookup database Done Executing linked: 0/2 done; 1 working: zone:ns1 Executing linked: 1/2 done; 1 working: zone:backup2 Executing linked: 2/2 done So, that *should* have updated the global and 2 lipkg zones. Let's check: $ openssl version global : OpenSSL 1.0.2h 3 May 2016 backup2 : OpenSSL 1.0.2e 3 Dec 2015 ns1 : OpenSSL 1.0.2e 3 Dec 2015 That's odd. It hasn't updated the zones at all. So, are the zones up to date or not? $ pfexec pkg update -nv ntp openssl No updates available for this image. Planning linked: 0/2 done; 1 working: zone:ns1 Linked image 'zone:ns1' output: | No updates necessary for this image. (zone:ns1) ` Planning linked: 1/2 done; 1 working: zone:backup2 Linked image 'zone:backup2' output: | No updates necessary for this image. (zone:backup2) ` Planning linked: 2/2 done So, pkg in the global zone thinks they're up to date when the output from the openssl command clearly indicates that they aren't. What if I go into the zone? # pkg update -nv ntp openssl Packages to update: 2 Services to change: 1 Estimated space available: 230.63 GB Estimated space to be consumed: 57.67 MB Create boot environment: No Create backup boot environment: Yes Rebuild boot archive: No Changed packages: omnios library/security/openssl 1.0.2.5-0.151014:20151203T201953Z -> 1.0.2.8-0.151014:20160503T143327Z service/network/ntp 4.2.8.4-0.151014:20151022T170026Z -> 4.2.8.7-0.151014:20160503T142738Z Services: restart_fmri: svc:/network/ntp:default So, inside the zone, pkg update will do the right thing. But why isn't pkg update from the global zone traversing into lipkg zones? -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
_______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss