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