Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-2817

Solaris Zone properties ip, dataset and inherit are not set upon zone creation

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: PUP 3.6.2
    • Fix Version/s: PUP 3.7.0
    • Component/s: None
    • Environment:

      Solaris 10u11
      Puppet 3.4.3 (PE 3.2.3)

    • Template:
    • Story Points:
      2
    • Sprint:
      2014-08-20, 2014-09-03

      Description

      The ip, dataset and inherit properties of the Zone type each have insync methods that respond with true when passed a nil property value. When a zone resource is first created, the property hash looks like:

      {
        ensure => :absent
      }
      

      This means that every property value aside from ensure is nil which causes ip, dataset and inherit to be skipped during zone creation. After creation, :absent is used in the hash instead of nil.

      However, in the case of inherit, the inherited directories of a Solaris 10 zone cannot be changed after creation:

      echo "add inherit-pkg-dir
      set dir=/opt/puppet
      end
      commit" | /usr/sbin/zonecfg -z test -f -
       
      On line 1:
      Zone test already installed; add inherit-pkg-dir not allowed.
      On line 2:
      Cannot set a resource-specific property from the global scope.
      On line 3:
      The end command only makes sense in the resource scope.
      

      To quote the official Solaris 10 documentation:

      These resources cannot be modified or removed after the zone has been installed using zoneadm.

      So, eventual consistency does no good for the inherit property.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  michael.smith Michael Smith
                  Reporter:
                  chuck Charlie Sharpsteen
                  QA Contact:
                  Eric Thompson
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support