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

sensitive_data_type test errantly testing beaker log instead of syslog output

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.7.1, PUP 4.8.1
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Systems Engineering
    • Story Points:
      1
    • Sprint:
      SE 2016-11-16
    • Release Notes:
      Not Needed

      Description

      The sensitive_data_type test attempts to make some assertions that sensitive data is absent from the syslog file but instead makes those assertions agains the beaker log itself. This causes the assertions to fail when the test matrix includes more than one agent node since the sensitive data is present in the beaker log itself after the first agent run is performed.

      This is causing the sensitive_data_type test to fail in the puppetserver CI pipeline, where both an agent on the master and an agent in a separate node are run together - see https://jenkins.puppetlabs.com/job/platform_puppetserver_integration-system_no-conditional_full-stable/255/LAYOUT=debian8-64ma-32a,LDAP_TYPE=default,label=beaker/testReport/junit/(root)/ruby_puppet_acceptance_tests_language/sensitive_data_type_rb/. The test is failing during the "assert no redacted data in syslog" step for the second agent.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jeremy.barlow Jeremy Barlow
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support