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

User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • PUP 3.5.0, PUP 3.5.1, PUP 3.6.2
    • PUP 3.7.0
    • Types and Providers
    • Solaris 10

    • 2
    • 2014-08-06

    Description

      Summary

      https://github.com/puppetlabs/puppet/commit/73b0c2b0f59db920a14d4d0951b1f1c40d603cb4. Seems to have broken the shell parameter for the user type in Solaris.

      One is now unable to specify a user's shell after the user has been created. This currently affects all users utilizing Puppet 3.6.2.

      Test Code:

      user { 'jay':
        ensure => present,
        managehome => true,
        shell => '/bin/sh',
      }
      

      Expected behavior

      Upon first run with /bin/bash:

      Info: Applying configuration version '1406730137'
      Notice: /Stage[main]/Main/Node[pe-33-agent-solaris.puppetdebug.vlan]/User[jay]/ensure: created
      Notice: Finished catalog run in 2.10 seconds
      

      Verifying it's /bin/bash:

      # cat /etc/passwd | grep jay
      jay:x:102:1::/home/jay:/bin/bash
      

      Run after changing the shell to /bin/sh:

      Info: Applying configuration version '1406730348'
      Notice: /Stage[main]/Main/Node[pe-33-agent-solaris.puppetdebug.vlan]/User[jay]/shell: shell changed '/bin/bash' to '/bin/sh'
      Notice: Finished catalog run in 3.12 seconds
      

      Verifying it's /bin/sh:

      # cat /etc/passwd | grep jay
      jay:x:102:1::/home/jay:/bin/sh
      

      Current behavior(PE 3.3/Puppet 3.6.2):

      Upon changing the shell once more, no changes are made.

      Attachments

        Issue Links

          Activity

            People

              john.duarte John Duarte
              jay Jay Wallace
              Narmadha Perumal Narmadha Perumal
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support