Uploaded image for project: 'Facter'
  1. Facter
  2. FACT-2960

Facter.conf doesn't accept in ttls singular form of time measure words

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: FACT 4.0.52
    • Component/s: None
    • Labels:
    • Template:
    • Team:
      Ghost
    • Story Points:
      2
    • Sprint:
      ghost-10.03.2021
    • Method Found:
      Needs Assessment
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      Description of the problem: Facter fails if the ttls from config file contains day (instead of days), hour (instead of hours) and so on.
      Ex:

      {
        "facts": {
          "blocklist": null,
          "ttls": [
            {
              "EC2": "1 day"
            }
          ]
        }
      }
      Description of the fix: Accept singular form of time measure words (second, minute, hour, day).
      Show
      Description of the problem: Facter fails if the ttls from config file contains day (instead of days), hour (instead of hours) and so on. Ex: {   "facts": {     "blocklist": null,     "ttls": [       {         "EC2": "1 day"       }     ]   } } Description of the fix: Accept singular form of time measure words (second, minute, hour, day).
    • QA Risk Assessment:
      Needs Assessment

      Description

      Affected version: puppet-agent.x86_64 0:7.4.1-1.el7

      Description of the problem: Puppet run fails because of the presence of a singular form of 'day' in ttls field (facter.conf).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              oana.tanasoiu Oana Tanasoiu
              Reporter:
              oana.tanasoiu Oana Tanasoiu
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support