# [OmniOS-discuss] ERROR: Could not update attaching zone

Serge Fonville serge.fonville at gmail.com
Tue Nov 21 11:57:45 UTC 2017

- Previous message: [OmniOS-discuss] ERROR: Could not update attaching zone
- Next message: [OmniOS-discuss] ERROR: Could not update attaching zone
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Currently I am no longer able to mount the dataset.
    When I execute the following command, I get the followign error:

    > zoneadm -z web01 attach
    >
    Output:
    ERROR: Failed to locate any dataset mounted at /export/zones/web01/root.
    Attach requires a mounted dataset.
                        Result: Attach Failed.
    Log:
    [Tue Nov 21 12:54:41 CET 2017] Log File: /var/tmp/web01.attach_log.8DaGSG
    [Tue Nov 21 12:54:42 CET 2017] ERROR: Failed to locate any dataset mounted
    at /export/zones/web01/root.  Attach requires a mounted dataset.
    [Tue Nov 21 12:54:42 CET 2017]                     Result: Attach Failed.

    Perhaps I broke something else in the process :-(

    Kind regards/met vriendelijke groet,

    Serge Fonville

    http://www.sergefonville.nl

    2017-11-21 7:54 GMT+01:00 Serge Fonville <serge.fonville at gmail.com>:

    > After having updated the canmount property to noauto of the filesystem,
    > the system now boots again.
    >
    > Kind regards/met vriendelijke groet,
    >
    > Serge Fonville
    >
    > http://www.sergefonville.nl
    >
    > 2017-11-21 7:08 GMT+01:00 Serge Fonville <serge.fonville at gmail.com>:
    >
    >> After having rebooted the server, I am now no longer able to logon to the
    >> server, the console shows messages it cannot mount the filesystem. because
    >> its directory is not empty, since the zone is in configured/detached state,
    >> how do I tell the system not to try to mount it?
    >>
    >> Kind regards/met vriendelijke groet,
    >>
    >> Serge Fonville
    >>
    >> http://www.sergefonville.nl
    >>
    >> 2017-11-21 6:11 GMT+01:00 Serge Fonville <serge.fonville at gmail.com>:
    >>
    >>> Also, since I had to remove it when I upgraded, I was under the
    >>> impression it was gone everywhere, since pkg publisher does not show it on
    >>> any other zone (including the GZ).
    >>>
    >>> Kind regards/met vriendelijke groet,
    >>>
    >>> Serge Fonville
    >>>
    >>> http://www.sergefonville.nl
    >>>
    >>> 2017-11-21 6:10 GMT+01:00 Serge Fonville <serge.fonville at gmail.com>:
    >>>
    >>>> So how do I see it in the GZ, because pkg publisher does not output it
    >>>> when I execute it on the GZ?
    >>>>
    >>>> Kind regards/met vriendelijke groet,
    >>>>
    >>>> Serge Fonville
    >>>>
    >>>> http://www.sergefonville.nl
    >>>>
    >>>> 2017-11-20 19:02 GMT+01:00 Dominik Hassler <hasslerd at gmx.li>:
    >>>>
    >>>>> > Child image publisher configuration must be a superset of the parent
    >>>>> image publisher configuration.
    >>>>>
    >>>>> your NGZ is lacking the ms.omniti.com publisher which you have set for
    >>>>> the GZ.
    >>>>>
    >>>>> after doing a:
    >>>>> # pkg -R /export/zones/web01/root set-publisher -g
    >>>>> http://pkg.omniti.com/omniti-ms/ ms.omniti.com
    >>>>>
    >>>>> attaching the zone should work.
    >>>>>
    >>>>> On 11/20/2017 06:26 PM, Serge Fonville wrote:
    >>>>> > Hi,
    >>>>> >
    >>>>> > When I tried to attach a zone I got the following errors:
    >>>>> >
    >>>>> >     zoneadm -z web01 attach
    >>>>> >
    >>>>> > Log File: /var/tmp/web01.attach_log.olaaFy
    >>>>> >                Attach Path: /export/zones/web01/root
    >>>>> >         Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9
    >>>>> >
    >>>>> >                 Installing: Using pre-existing data in zonepath
    >>>>> >                      Cache: Using /var/pkg/publisher.
    >>>>> >   Updating non-global zone: Output follows
    >>>>> >
    >>>>> >                 Evaluation: Packages in zone web01 are out of sync
    >>>>> with
    >>>>> > the global zone. To proceed, retry with the -u flag.
    >>>>> >                     Result: Attach Failed.
    >>>>> > With the log file containing:
    >>>>> > [Mon Nov 20 18:02:28 CET 2017] Log File:
    >>>>> /var/tmp/web01.attach_log.olaaFy
    >>>>> > [Mon Nov 20 18:02:32 CET 2017]                Attach Path:
    >>>>> > /export/zones/web01/root
    >>>>> > [Mon Nov 20 18:02:32 CET 2017]         Attach ZFS Dataset:
    >>>>> > rpool/export/zones/web01/ROOT/zbe-9
    >>>>> >
    >>>>> > [Mon Nov 20 18:02:32 CET 2017] existing
    >>>>> > [Mon Nov 20 18:02:32 CET 2017]                 Installing: Using
    >>>>> > pre-existing data in zonepath
    >>>>> > [Mon Nov 20 18:02:32 CET 2017]   Sanity Check: Passed.  Looks like an
    >>>>> > OpenSolaris system.
    >>>>> > pkg: Search performance is degraded.
    >>>>> > Run 'pkg rebuild-index' to improve search speed.
    >>>>> > [Mon Nov 20 18:02:39 CET 2017]                      Cache: Using
    >>>>> > /var/pkg/publisher.
    >>>>> > [Mon Nov 20 18:02:39 CET 2017]   Updating non-global zone: Output
    >>>>> follows
    >>>>> >
    >>>>> >
    >>>>> > pkg install: Invalid child image publisher configuration.  Child
    >>>>> image
    >>>>> > publisher
    >>>>> > configuration must be a superset of the parent image publisher
    >>>>> > configuration.
    >>>>> > Please update the child publisher configuration to match the
    >>>>> parent.  If the
    >>>>> > child image is a zone this can be done automatically by detaching and
    >>>>> > attaching the zone.
    >>>>> >
    >>>>> > The parent image has the following enabled publishers:
    >>>>> >     PUBLISHER 0: omnios
    >>>>> >     PUBLISHER 1: ms.omniti.com <http://ms.omniti.com>
    >>>>> >
    >>>>> > The child image has the following enabled publishers:
    >>>>> >     PUBLISHER 0: omnios
    >>>>> > [Mon Nov 20 18:02:42 CET 2017]
    >>>>> >                 Evaluation: Packages in zone web01 are out of sync
    >>>>> with
    >>>>> > the global zone. To proceed, retry with the -u flag.
    >>>>> > [Mon Nov 20 18:02:44 CET 2017]                     Result: Attach
    >>>>> Failed.
    >>>>> >
    >>>>> > So I try to run  it with -u
    >>>>> >
    >>>>> >     zoneadm -z web01 attach -u
    >>>>> >
    >>>>> >  Log File: /var/tmp/web01.attach_log.TNaqaR
    >>>>> >                Attach Path: /export/zones/web01/root
    >>>>> >         Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9
    >>>>> >
    >>>>> >                 Installing: Using pre-existing data in zonepath
    >>>>> >                      Cache: Using /var/pkg/publisher.
    >>>>> >   Updating non-global zone: Output follows
    >>>>> > ERROR: Could not update attaching zone
    >>>>> >                     Result: Attach Failed.
    >>>>> >
    >>>>> > With the log file containing:
    >>>>> > [Mon Nov 20 18:20:23 CET 2017] Log File:
    >>>>> /var/tmp/web01.attach_log.TNaqaR
    >>>>> > [Mon Nov 20 18:20:27 CET 2017]                Attach Path:
    >>>>> > /export/zones/web01/root
    >>>>> > [Mon Nov 20 18:20:27 CET 2017]         Attach ZFS Dataset:
    >>>>> > rpool/export/zones/web01/ROOT/zbe-9
    >>>>> >
    >>>>> > [Mon Nov 20 18:20:27 CET 2017] existing
    >>>>> > [Mon Nov 20 18:20:27 CET 2017]                 Installing: Using
    >>>>> > pre-existing data in zonepath
    >>>>> > [Mon Nov 20 18:20:27 CET 2017]   Sanity Check: Passed.  Looks like an
    >>>>> > OpenSolaris system.
    >>>>> > [Mon Nov 20 18:20:31 CET 2017]                      Cache: Using
    >>>>> > /var/pkg/publisher.
    >>>>> > [Mon Nov 20 18:20:31 CET 2017]   Updating non-global zone: Output
    >>>>> follows
    >>>>> >
    >>>>> >
    >>>>> > pkg install: Invalid child image publisher configuration.  Child
    >>>>> image
    >>>>> > publisher
    >>>>> > configuration must be a superset of the parent image publisher
    >>>>> > configuration.
    >>>>> > Please update the child publisher configuration to match the
    >>>>> parent.  If the
    >>>>> > child image is a zone this can be done automatically by detaching and
    >>>>> > attaching the zone.
    >>>>> >
    >>>>> > The parent image has the following enabled publishers:
    >>>>> >     PUBLISHER 0: omnios
    >>>>> >     PUBLISHER 1: ms.omniti.com <http://ms.omniti.com>
    >>>>> >
    >>>>> > The child image has the following enabled publishers:
    >>>>> >     PUBLISHER 0: omnios
    >>>>> > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching zone
    >>>>> > [Mon Nov 20 18:20:36 CET 2017]                     Result: Attach
    >>>>> Failed.
    >>>>> >
    >>>>> > On global zone:
    >>>>> >
    >>>>> >     pkg publisher
    >>>>> >
    >>>>> > PUBLISHER                   TYPE     STATUS P LOCATION
    >>>>> > omnios                      origin   online F
    >>>>> > https://pkg.omniosce.org/r151022/core/
    >>>>> >
    >>>>> > Any help in resolving this greatly appreciated!!
    >>>>> >
    >>>>> > Thanks in advance!!
    >>>>> >
    >>>>> > Kind regards/met vriendelijke groet,
    >>>>> >
    >>>>> > Serge Fonville
    >>>>> >
    >>>>> > http://www.sergefonville.nl
    >>>>> >
    >>>>> >
    >>>>> > _______________________________________________
    >>>>> > OmniOS-discuss mailing list
    >>>>> > OmniOS-discuss at lists.omniti.com
    >>>>> > http://lists.omniti.com/mailman/listinfo/omnios-discuss
    >>>>> >
    >>>>>
    >>>>
    >>>>
    >>>
    >>
    >
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20171121/eacde540/attachment.html>

- Previous message: [OmniOS-discuss] ERROR: Could not update attaching zone
- Next message: [OmniOS-discuss] ERROR: Could not update attaching zone
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the OmniOS-discuss mailing list