Jira (PUP-10099) Unable to install zone on solaris 11

[Josh Cooper (JIRA)]

Josh Cooper created an issue

Puppet / PUP-10099 Unable to install zone on solaris 11 Issue Type: Improvement Assignee: Unassigned Created: 2019/10/10 4:04 PM Priority: Normal Reporter: Josh Cooper Trying to create a zone resource on Solaris 11 from vmpooler: zone { 'tstzone': ensure=>running, path=>'/tstzones/mnt', } Applying with puppet results in: Debug: Executing: '/usr/sbin/zoneadm -z tstzone list -p' Debug: Executing: '/usr/sbin/zoneadm -z tstzone list -p' Debug: Executing: 'echo "create -b set ip-type=shared set autoboot=true set zonepath=/tstzones/mnt commit exit" | /usr/sbin/zonecfg -z tstzone -f -' Debug: Executing: '/usr/sbin/zoneadm -z tstzone list -p' Debug: Executing: '/usr/sbin/zonecfg -z tstzone info' Debug: Executing: '/usr/sbin/zoneadm -z tstzone install' Error: Could not install zone: Execution of '/usr/sbin/zoneadm -z tstzone install' returned 1: The following ZFS file system(s) have been created: rpool/tstzones rpool/tstzones/mnt Progress being logged to /var/log/zones/zoneadm.20191010T223551Z.tstzone.install Image: Preparing at /tstzones/mnt/root.   AI Manifest: /tmp/manifest.xml.ZHaabm SC Profile: /usr/share/auto_install/sc_profiles/enable_sci.xml Zonename: tstzone Installation: Starting ...   Creating IPS image Startup: Retrieving catalog 'solarisstudio' ... Done Startup: Retrieving catalog 'solaris' ... Done Startup: Retrieving catalog 'puppetlabs.com' ... Done Startup: Caching catalogs ... Done Startup: Finished processing linked images. Startup: Refreshing catalog 'solarisstudio' ... Done Startup: Refreshing catalog 'solaris' ... Done Startup: Refreshing catalog 'puppetlabs.com' ... Done Installing packages from: solaris origin: http://pkg.oracle.com/solaris/release/ solarisstudio origin: http://pkg.oracle.com/solarisstudio/release/ puppetlabs.com Startup: Refreshing catalog 'solarisstudio' ... Done Startup: Refreshing catalog 'solaris' ... Done Startup: Refreshing catalog 'puppetlabs.com' ... Done Error occurred during execution of 'generated-transfer-6164-1' checkpoint. Failed Checkpoints:   Checkpoint execution error:   The following pattern(s) did not match any allowable packages. Try using a different matching pattern, or refreshing publisher information:   Installation: Failed. See install log at /system/volatile/install.6164/install_log ERROR: auto-install failed. Error: /Stage[main]/Main/Zone[tstzone]/ensure: change from 'absent' to 'running' failed: Could not install zone: Execution of '/usr/sbin/zoneadm -z tstzone install' returned 1: The following ZFS file system(s) have been created: rpool/tstzones rpool/tstzones/mnt Progress being logged to /var/log/zones/zoneadm.20191010T223551Z.tstzone.install Image: Preparing at /tstzones/mnt/root.   AI Manifest: /tmp/manifest.xml.ZHaabm SC Profile: /usr/share/auto_install/sc_profiles/enable_sci.xml Zonename: tstzone Installation: Starting ...   Creating IPS image Startup: Retrieving catalog 'solarisstudio' ... Done Startup: Retrieving catalog 'solaris' ... Done Startup: Retrieving catalog 'puppetlabs.com' ... Done Startup: Caching catalogs ... Done Startup: Finished processing linked images. Startup: Refreshing catalog 'solarisstudio' ... Done Startup: Refreshing catalog 'solaris' ... Done Startup: Refreshing catalog 'puppetlabs.com' ... Done Installing packages from: solaris origin: http://pkg.oracle.com/solaris/release/ solarisstudio origin: http://pkg.oracle.com/solarisstudio/release/ puppetlabs.com Startup: Refreshing catalog 'solarisstudio' ... Done Startup: Refreshing catalog 'solaris' ... Done Startup: Refreshing catalog 'puppetlabs.com' ... Done Error occurred during execution of 'generated-transfer-6164-1' checkpoint. Failed Checkpoints:   Checkpoint execution error:   The following pattern(s) did not match any allowable packages. Try using a different matching pattern, or refreshing publisher information:   Installation: Failed. See install log at /system/volatile/install.6164/install_log ERROR: auto-install failed. The zone install log shows: [Thu Oct 10 15:35:51 PDT 2019] ==== Starting: /usr/lib/brand/solaris/pkgcreatezone -z tstzone -R /tstzones/mnt ==== [Thu Oct 10 15:35:51 PDT 2019] Progress being logged to /var/log/zones/zoneadm.20191010T223551Z.tstzone.install [Thu Oct 10 15:35:51 PDT 2019] Image: Preparing at /tstzones/mnt/root.   [Thu Oct 10 15:35:52 PDT 2019] Running auto-install: '/usr/bin/auto-install -z tstzone -Z rpool/tstzones/mnt/rpool -m /tmp/manifest.xml.ZHaabm -c /usr/share/auto_install/sc_profiles/enable_sci.xml' [Thu Oct 10 15:36:06 PDT 2019] ERROR: auto-install failed. [Thu Oct 10 15:36:06 PDT 2019] Exiting with exit code 255 [Thu Oct 10 15:36:06 PDT 2019] ==== Completed: /usr/lib/brand/solaris/pkgcreatezone -z tstzone -R /tstzones/mnt ==== To reproduce, checkout puppet 5.5.x: $ cd acceptance $ bundle install --path .bundle ... $ bundle exec rake ci:test:aio BEAKER_HOSTS=redhat7-64m-solaris11-64a SHA=7d8748d31620db50dd8e00eabc699c25ab956821 SERVER_VERSION=5.3.10.SNAPSHOT.2019.10.07T1349 TESTS=tests/resource/zone/should_be_created_and_removed.rb OPTIONS='--preserve-hosts=always' The following describes the error I'm seeing: https://docs.oracle.com/cd/E36784_01/html/E36802/tspkginstall.html#AUOSSnomatchingvers: Non-Global Zone Cannot Be Installed Error message: The following pattern(s) did not match any allowable packages. Try using a different matching pattern, or refreshing publisher information   Core operating system packages must be the same version in non-global zones as in the global zone. If the solaris publisher origin in this image is set to a package repository that does not contain the same versions of the system packages that are installed in the global zone, attempting to install a non-global zone results in the following error:   ....     To install a non-global zone, the repository that you set as the solaris publisher origin must contain at least the same system software that is installed in the global zone where you are installing the non-global zone. The repository can also contain older or newer software, but it must contain the same software that is installed in the global zone. The following command shows that the /export/IPSpkgrepos/Solaris repository is a suitable publisher origin for this global zone because this repository contains the same version of the pkg:/entire package that is installed in the global zone: This makes me think the solaris image was updated (or needs to be updated). /cc Mihai Buzgau, Rob Braden, Also FYI it looks like the solarisstudio cert will expire next month: root@bkvtnhki4p28sgn:~# openssl x509 -in /var/pkg/ssl/06916003a24be2e511f75afb0a2eb02923a528d5 -noout -text Certificate: Data: Version: 1 (0x0) Serial Number: 4625 (0x1211) Signature Algorithm: sha256WithRSAEncryption Issuer: C=US/emailAddress=PKG-INQ...@ORACLE.COM, CN=Oracle Software Delivery SHA-256 Validity Not Before: Nov 2 17:32:34 2017 GMT Not After : Nov 10 17:32:34 2019 GMT Subject: C=US, CN=bra...@puppetlabs.com Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)