Fixed
Details
Assignee
Christian PapeChristian PapeReporter
Will KeaneyWill KeaneyLabels
HB Grooming Date
Feb 15, 2022HB Backlog Status
BacklogComponents
Sprint
NoneFix versions
Affects versions
Priority
Minor
Details
Details
Assignee
Christian Pape
Christian PapeReporter
Will Keaney
Will KeaneyLabels
HB Grooming Date
Feb 15, 2022
HB Backlog Status
Backlog
Components
Sprint
None
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created February 9, 2022 at 8:54 PM
Updated March 24, 2022 at 2:54 PM
Resolved March 17, 2022 at 6:59 AM
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 toopennms:opennms
even ifRUNAS
is set to a different user.Steps to reproduce:
Install an OpenNMS that's older than the current release.
Configure
RUNAS
to a user that's notopennms
.Set ownership for all OpenNMS files to that user.
Upgrade OpenNMS.
Expected results:
If
RUNAS
is set to a value other thanopennms
, the/opt/opennms/logs
and/var/log/opennms
directory ownership should not be changed, or should be set to the configuredRUNAS
user.Actual results:
/opt/opennms/logs
(or/var/log/opennms
) ownership is changed toopennms:opennms
regardless of the value ofRUNAS
.