Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-11054

Place rpm_gpg_import_check.sh in a more sensible location

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: puppet_agent
    • Labels:
    • Template:
      MODULES Bug Template
    • Team:
      Night's Watch
    • Sprint:
      ready for triage
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      puppet_agent v 4.6 places a permanent file rpm_gpg_import_check.sh into /tmp. Seems questionable choice to me. Since /tmp is most often tmpfs and getting cleaned periodically, file will be recreated again and again. Why don't put it into /usr/local/bin or something like that instead ?

      Context: https://puppetcommunity.slack.com/archives/C11LCKKQ9/p1619183089100600 and https://github.com/puppetlabs/puppetlabs-puppet_agent/commit/c793fd0d0be363a42f9d23aa11cd1687fdcfae74#commitcomment-49907770

        Attachments

          Issue Links

          is caused by

          Task - A task that needs to be done. MODULES-10996 Update puppet_agent module to install sles11 packages directly from the rpm

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

          Bug - A problem which impairs or prevents the functions of the product. MODULES-11057 {puppetlabs-puppet_agent} : {Version 4.6.0 fails on Red Hat}

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

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              gabriel.nagy Gabriel Nagy
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support