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

Resource titles ending with square brackets fail

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 3.7.1
    • Component/s: Compiler
    • Labels:
    • Template:
    • Story Points:
      1
    • Sprint:
      Platform 2014-09-17

      Description

      Hi,

      We're trying to install a package but the title has got square brackets which seems to make Puppet blow up, for example:

      package

      { "Windows Server AppFabric v1.1 CU4 [KB 2800726]": ensure => installed, source => $fullInstallerPath, install_options => $install_options, }

      Trying to run this results in error "invalid tag". We've tried escaping the brackets but that doesn't work either.

      Even running puppet resource form the command prompt gives an error:

      C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet resource package
      Error: Could not run: Invalid tag "microsoft sql server 2005 compact edition "

      The actual title in control panel for is "microsoft sql server 2005 compact edition [ENU]". It would seem resource titles with square brackets cause issues.

      Is this is a bug in Puppet? Can anyone suggest a work around as this kind of renders Puppet not very useful for us without being able to install products.

      Puppet agent 3.4.3

      Thanks

      Dan

      https://groups.google.com/forum/#!searchin/puppet-users/gibbons/puppet-users/Lv61sE-rdQU/r8XTRHU9mgAJ

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              ifunky Dan Gibbons
              QA Contact:
              Eric Thompson
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support