[OmniOS-discuss] pkg update broken on r151026 for lipkg branded NGZs

Volker A. Brandt vab at bb-c.de
Thu Aug 23 16:51:02 UTC 2018


Hello all!


I have a very strange problem doing a pkg update on a r151026 system.
This machine has 11 NGZs, all are lipkg brand.  The GZ is running

  SunOS radbug 5.11 omnios-r151026-b6848f4455 i86pc i386 i86pc

(before the update).  When I run pkg update with the "-r" flag, it
shows some packages it wants to update, then does it's thing, and
... stops.  No new BE is created:

  # pkg update -v -rC0 --be-name=ooce-026-20180823

  [...]

  Planning linked:  9/11 done; 2 working: zone:kayak zone:omnit3
  Linked image 'zone:omnit3' output:
  |             Packages to update:        11
  |             Services to change:         2
  |      Estimated space available: 426.13 GB
  | Estimated space to be consumed: 173.45 MB
  |           Rebuild boot archive:        No
  |
  | Changed packages:
  | omnios
  |   SUNWcs
  |     0.5.11-0.151026:20180622T094606Z -> 0.5.11-0.151026:20180814T181134Z
  |   developer/debug/mdb
  |     0.5.11-0.151026:20180621T235844Z -> 0.5.11-0.151026:20180814T181141Z
  |   library/security/openssl
  |     1.0.2.15-0.151026 -> 1.0.2.16-0.151026
  |   network/dns/bind
  |     9.11.3-0.151026 -> 9.11.4-0.151026
  |   network/openssh
  |     7.6.1-0.151026:20180420T101453Z -> 7.6.1-0.151026:20180818T202827Z
  |   network/openssh-server
  |     7.6.1-0.151026:20180420T101522Z -> 7.6.1-0.151026:20180818T202943Z
  |   release/name
  |     0.5.11-0.151026:20180622T100612Z -> 0.5.11-0.151026:20180820T120713Z
  |   service/network/ntp
  |     4.2.8.11-0.151026 -> 4.2.8.12-0.151026
  |   system/kernel
  |     0.5.11-0.151026:20180621T235958Z -> 0.5.11-0.151026:20180814T181345Z
  |   system/kernel/platform
  |     0.5.11-0.151026:20180621T235956Z -> 0.5.11-0.151026:20180814T181344Z
  |   web/curl
  |     7.60.0-0.151026 -> 7.61.0-0.151026
  |
  | Services:
  |   restart_fmri:
  |     svc:/network/ntp:default
  |     svc:/network/ssh:default
  |
  | Editable files to change:
  |   Update:
  |     etc/motd

  [...]

  Planning linked: 11/11 done
  DOWNLOAD                                PKGS         FILES    XFER (MB)   SPEED
  Completed                              11/11     2263/2263    46.3/46.3    0B/s

  Downloading linked:  0/11 done; 11 working: zone:kayak zone:omnib0 zone:omnib1 zone:omnib2 zone:omnib3 zone:omnib4 zone:omnit0 zone:omnit1 zone:omnit2 zone:omnit3 zone:omnit4
  Downloading linked:  1/11 done; 10 working: zone:kayak zone:omnib1 zone:omnib2 zone:omnib3 zone:omnib4 zone:omnit0 zone:omnit1 zone:omnit2 zone:omnit3 zone:omnit4
  Downloading linked:  2/11 done; 9 working: zone:omnib1 zone:omnib2 zone:omnib3 zone:omnib4 zone:omnit0 zone:omnit1 zone:omnit2 zone:omnit3 zone:omnit4
  Linked progress: \||||||-|98.540u 11.950s 0:51.57 214.2%        0+0k 0+0io 0pf+0w
  Exit 1

Note that it just returned exit code 1 right in the middle of the
"Linked progress" display.

When I omit the "-r", things change:

  # zonename
  omnib0

  # pkg update -v -C0 --be-name=ooce-026-20180823

  [...]

  Planning linked: 10/11 done; 1 working: zone:omnit4
  Linked image 'zone:omnit4' output:
  |             Packages to update:         1
  |      Estimated space available: 426.01 GB
  | Estimated space to be consumed:  35.03 MB
  |           Rebuild boot archive:        No
  |
  | Changed packages:
  | omnios
  |   SUNWcs
  |     0.5.11-0.151026:20180622T094606Z -> 0.5.11-0.151026:20180814T181134Z
  |
  | Editable files to change:
  |   Update:
  |     etc/motd

A new BE is created.  However, it just updates the SUNWcs package
containing the new motd file.

When I boot into the new BE and retry "pkg update -rC0", I get the
same result: It just stops without a new BE.  The GZ is now on:

  SunOS radbug 5.11 omnios-r151026-51c7d6fd75 i86pc i386 i86pc


Logging into any one zone, I can update that zone individually.  The update
will try to apply all 11 packages that are newer in the repository.
However, that produces an error because bootadm update-archive is
run and subsequently fails:

  # pkg update -v --be-name=deleteme
              Packages to update:        11
  [...]
    system/kernel/platform
      0.5.11-0.151026:20180621T235956Z -> 0.5.11-0.151026:20180814T181344Z
    web/curl
      7.60.0-0.151026 -> 7.61.0-0.151026

  DOWNLOAD                                PKGS         FILES    XFER (MB)   SPEED
  Completed                              11/11     1519/1519    30.0/30.0  3.9M/s

  PHASE                                          ITEMS
  Removing old actions                           28/28
  Installing new actions                         78/78
  Updating modified actions                  1520/1520
  Updating package state database                 Done
  Updating package cache                         11/11
  Updating image state                            Done
  Creating fast lookup database                   Done
  pkg: '/sbin/bootadm update-archive -R /tmp/tmp36Jtli' failed.
  with a return code of 1.
  Updating package cache                           3/3
  pkg: unable to activate deleteme
  Updating package cache                           3/3

  [...]

  # beadm list
  BE       Active Mountpoint     Space Policy Created
  zbe      xb     -              2.45M static 2018-07-11 23:16
  zbe-1    xb     -              204K  static 2018-08-23 17:33
  zbe-2    NR     /              238K  static 2018-08-23 17:59
  deleteme -      /tmp/tmp36Jtli 1.05G static 2018-08-23 18:28

  # beadm unmount deleteme
  Unmounted successfully

  # beadm activate deleteme
  Unable to activate deleteme.
  BE promotion failed.


Before all that, I had to update pkg which worked fine using -r -C0.
I am now running pkg://omnios/package/pkg@0.5.11-0.151026:20180725T094123Z
which is the current version in the repo.

Effectively I cannot pkg update my system including the zones any more.
I have previously updated this system without any problems.

Any ideas?


Thanks -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt        Consulting and Support for Solaris-based Systems
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgröße: 46
Geschäftsführer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"


More information about the OmniOS-discuss mailing list