Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-1378

`puppetserver gem list` emits `The following options to parse-opts are unrecognized: :flag`

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: SERVER 2.4.0
    • Fix Version/s: SERVER 2.5.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Sub-team:
    • Story Points:
      1
    • Sprint:
      Server Emerald 2016-06-15
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      Puppet Server was using a deprecated API for a clojure CLI option-parsing library, and as a result, calls to `puppetserver gem` (either directly, or indirectly by using a `puppetserver_gem` package resource in your puppet catalog) would generate a warning message.
      Show
      Puppet Server was using a deprecated API for a clojure CLI option-parsing library, and as a result, calls to `puppetserver gem` (either directly, or indirectly by using a `puppetserver_gem` package resource in your puppet catalog) would generate a warning message.

      Description

      Update 2016-06-08: Modifying the description to reflect that this ticket is being split into two chunks of work. This ticket should cover the work of upgrading puppetserver to the latest version of kitchensink and validating that that gets rid of the warning message (which is currently reproducible when running from source by running lein gem -c /path/to/conf – list).

      I also split off TK-381 to capture the work of cleaning up the dependency list in tk-auth; I'm not sure whether that will be a prereq to getting rid of the warning message or not, but we should go ahead and get it done anyway just to avoid future issues. And if it turns out that we can't get rid of the warning w/o fixing tk-auth and doing a release of it, then let's keep this ticket open until that has happened.

      ORIGINAL DESCRIPTION:
      ----------------------------------

      Hi

      After upgrading to puppetserver 2.4, my puppet runs on my masters produce the following warning.

      Warning: Could not match Warning: The following options to parse-opts are unrecognized: :flag
      

      We, (thanks Dominic Cleal!) think this happens when the puppetserver_gem package provider does a puppetserver gem list

      [root@master ~]# bash -x /opt/puppetlabs/bin/puppetserver gem list
      + set -a
      + '[' -r /etc/default/puppetserver ']'
      + '[' -r /etc/sysconfig/puppetserver ']'
      + . /etc/sysconfig/puppetserver
      ++ JAVA_BIN=/usr/bin/java
      ++ JAVA_ARGS='-Xms2G -Xmx2G -XX:MaxPermSize=256m'
      ++ USER=puppet
      ++ GROUP=puppet
      ++ INSTALL_DIR=/opt/puppetlabs/server/apps/puppetserver
      ++ CONFIG=/etc/puppetlabs/puppetserver/conf.d
      ++ BOOTSTRAP_CONFIG=/etc/puppetlabs/puppetserver/bootstrap.cfg
      ++ SERVICE_STOP_RETRIES=60
      + set +a
      + CLI_DIR=/opt/puppetlabs/server/apps/puppetserver/cli
      + CLI_APP_DIR=/opt/puppetlabs/server/apps/puppetserver/cli/apps
      ++ ls /opt/puppetlabs/server/apps/puppetserver/cli/apps
      + APPS='foreground
      gem
      irb
      ruby'
      + '[' -z gem ']'
      + '[' gem = --help ']'
      + '[' gem = -h ']'
      + '[' gem = --version ']'
      + '[' gem = -v ']'
      + execsubcommand gem list
      + sub=gem
      + shift
      + cmd=/opt/puppetlabs/server/apps/puppetserver/cli/apps/gem
      + '[' -e /opt/puppetlabs/server/apps/puppetserver/cli/apps/gem ']'
      + exec /opt/puppetlabs/server/apps/puppetserver/cli/apps/gem list
      Warning: The following options to parse-opts are unrecognized: :flag
       
      *** LOCAL GEMS ***
       
      deep_merge (1.0.1)
      hiera-eyaml (2.1.0)
      highline (1.6.21)
      jar-dependencies (0.1.13)
      jruby-openssl (0.9.7 java)
      json (1.8.0 java)
      rake (10.1.0)
      rdoc (4.1.2)
      trollop (2.1.2)
      

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                chris Chris Price
                Reporter:
                alexjfisher Alexander Fisher
                QA Contact:
                Erik Dasher
              • Votes:
                1 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: