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

`puppet agent --test` does not override cached catalog behavior

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.6.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      1
    • Sprint:
      Client 2016-07-13 (HA, 1.5.3), Client 2016-07-27
    • Release Notes:
      New Feature
    • Release Notes Summary:
      Hide
      Now using the
      --test flag with puppet agent overrides the --use_cached_catalog setting. Declaring these flags in combination does not result in the use of a cached catalog.
      Show
      Now using the --test flag with puppet agent overrides the --use_cached_catalog setting. Declaring these flags in combination does not result in the use of a cached catalog.

      Description

      * --test:
        Enable the most common options used for testing. These are 'onetime',
        'verbose', 'ignorecache', 'no-daemonize', 'no-usecacheonfailure',
        'detailed-exitcodes', 'no-splay', and 'show_diff'.
      

      Puppet 4.3.2

      When agents are configured `use_cached_catalog = true`, as they are for application management with the orchestrator, I expect a forced agent run via `puppet agent -t` to imply --no-use_cached_catalog, as a common option I'd use for testing a change to an individual node configured for orchestration in PE.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  qa qa
                  Reporter:
                  ryan Ryan Coleman
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: