Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-14000

Upgrading opennms ignores RUNAS when setting ownership on logs directory

    XMLWordPrintable

Details

    • Horizon 22 - Mar 2 - 16, Horizon 22 - March 16 - 30
    • Backlog

    Description

      When upgrading OpenNMS, if you have set RUNAS to something other than opennms, the installer prints a warning and leaves directory ownership intact.

      It does not leave directory ownership intact for /opt/opennms/logs (or /var/log/opennms), setting ownership to opennms:opennms even if RUNAS is set to a different user.

      Steps to reproduce:

      1. Install an OpenNMS that's older than the current release.
      2. Configure RUNAS to a user that's not opennms.
      3. Set ownership for all OpenNMS files to that user.
      4. Upgrade OpenNMS.

      Expected results:
      If RUNAS is set to a value other than opennms, the /opt/opennms/logs and /var/log/opennms directory ownership should not be changed, or should be set to the configured RUNAS user.

      Actual results:
      /opt/opennms/logs (or /var/log/opennms) ownership is changed to opennms:opennms regardless of the value of RUNAS.

      Attachments

        Issue Links

          Activity

            People

              cpape Christian Pape
              wkeaney Will Keaney
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: