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

Do not use system_uptime fact as a source of randomness in acceptance test

          Details

          • Type: CI Blocker
          • Status: Closed
          • Priority: Normal
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: PUP 5.3.4
          • Component/s: None
          • Labels:
            None
          • CI Pipeline/s:
            platform puppetserver
          • Team:
            Froyo
          • Story Points:
            1
          • Sprint:
            Platform Core KANBAN
          • Release Notes:
            Not Needed
          • QA Risk Assessment:
            Needs Assessment

            Description

            To ensure variables are refreshed each catalog compilation we use the facter's system_uptime fact (see variables_refreshed_each_compilation test). Unfortunately there's an issue with facter that may cause that fact not to be present on Windows systems (See FACT-1504). We should update this test to use a different, constantly changing variable - at least on windows.

              Attachments

                Issue Links

                relates to

                Bug - A problem which impairs or prevents the functions of the product. IMAGES-722 Windows VMs' bootuptimes are routinely ahead of current localtime

                • Normal - Regular issue, some loss of functionality under specific circumstances.
                • Resolved

                Bug - A problem which impairs or prevents the functions of the product. FACT-1504 Uptime resolver fact for Windows uses unreliable metric for uptime

                • Normal - Regular issue, some loss of functionality under specific circumstances.
                • Closed

                  Activity

                    People

                    • Assignee:
                      justin Justin Stoller
                      Reporter:
                      justin Justin Stoller
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      2 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved:

                        Zendesk Support