Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-7377

puppet_agent module ignores my configuration on solaris 10 hosts

    Details

    • Type: Bug
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: puppet_agent
    • Labels:
    • Template:
      MODULES Bug Template
    • Team:
      Platform OS
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Basic Info
      Module Version: 1.6.0
      Puppet Version: 5.3.5 (PE 2017.3.5)
      OS Name/Version: RHEL 7 (Server)  Solaris 10 (Agent)

      Describe your issue in as much detail as possible...

      Desired Behavior: Do not start the puppet agent after upgrading, or at least give the option when doing a Solaris 10 agent upgrade.

      Actual Behavior: The /tmp/solaris_install.sh script generated by the puppet_agent class hardcodes the startup/enable of the "puppet" and "mcollective" services regardless of the value of puppet_agent::services or puppet_agent::install_options, or the settings I have in my puppet.conf (most notably  agent:daemonize=false)   
      We do not run puppet as an agent and this unexpected behavior has caused us problems.

      Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                sirinek Bill Sirinek
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Zendesk Support