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

race condition smf and manifest-import

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PUP 3.8.6, PUP 4.7.0
    • Fix Version/s: PUP 4.8.0
    • Component/s: Types and Providers
    • Labels:
    • Environment:

      The next release of Solaris and also Solaris >= 11.2

    • Template:

      Description

      by default pkg install/update does not wait for smf actuators to finish before continuing

      Reported Problem:

      I've observed several instances of puppet installing a package and then
      trying to start a service or modify service properties, resulting in failures
      noting that the service doesn't exist.

      For example:

      svcadm enable -rs nova-conductor:default claims that nova-conductor:upgrade
      doesn't exist as s service.

      svccfg -s keystone:default setprop claims that keystone:default doesn't
      exist.

      If you go look at the system later, they do exist.

      I've caught it in action several times and this is the problem:

      root@lilcloud-controller:~# svcs -x
      svc:/system/manifest-import:default (service manifest import)
       State: offline* transitioning to online since Thu Apr 14 13:07:43 2016
      Reason: Start method is running.
         See: http://support.oracle.com/msg/SMF-8000-C4
         See: smf_bootstrap(7)
         See: /var/svc/log/system-manifest-import:default.log
      Impact: This service is not running.
      

      The system is restarting and sometimes it has 15-20 manifests to import, so
      it is taking some time.

      The puppet provider needs to wait for this service to quiesce before it
      considers the package actually installed.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              shawnferry Shawn Ferry
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support