Uploaded image for project: 'Puppet Agent'
  1. Puppet Agent
  2. PA-1849

updating puppet-agent from 5.3.3 to 5.3.4 produces a fast_gettext error

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Won't Fix
    • puppet-agent 5.3.4
    • None
    • None
    • The puppetmaster: puppetserver-5.1.4 on RHEL 7.4 x86_64

      All puppet clients: puppet-agent-5.3.3 on RHEL 5, RHEL6, and RHEL 7

    • Platform OS
    • Customer Feedback
    • Reviewed
    • 34786
    • 1
    • Needs Assessment

    Description

      When using puppet-agent-5.3.3 to upgrade itself to puppet-agent-5.3.4, during the upgrade process there's error output from ruby, related to fast_gettext:

       

      $ sudo puppet apply -e "package { 'puppet-agent': ensure => '5.3.4-1.el6' }"
      Notice: Compiled catalog for somehost.somedomain.edu in environment production in 0.03 seconds
      Error: Could not convert change ensure to string: No such file or directory @ rb_sysopen - /opt/puppetlabs/puppet/lib/ruby/gems/2.4.0/gems/fast_gettext-1.1.0/lib/fast_gettext/vendor/empty.mo
      Error: No such file or directory @ rb_sysopen - /opt/puppetlabs/puppet/lib/ruby/gems/2.4.0/gems/fast_gettext-1.1.0/lib/fast_gettext/vendor/empty.mo
       
      $ sudo puppet --version
      5.3.4
      

       

      That only happens on the upgrade itself.  Afterward, the 5.3.4 agent seems to be fine.

      Note, though, that if there are other pending changes during the agent run when 5.3.3 upgrades to 5.3.4, the other changes are not applied (the agent run errors out) until the 5.3.4 agent is run again.

      This is probably a matter for the release notes or documentation more than anything.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              solstice Tim Mooney
              Votes:
              2 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support