Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Issues

Select view

Select search mode

 
1 of 1

Allow fix-permissions and update-package-permissions scripts to set ownership for customized users

Fixed

Description

The fix-permissions and update-package-permissions scripts check whether the $RUNAS user is opennms. If it is not, they print a message stating that $RUNAS has been changed from the default 'opennms' user. Assuming you know what you're doing and not changing ownership of any files. , then exit with status 0.

This leaves the installation in an inconsistent state, with some files owned by the $RUNAS user and some owned by the opennms user, which requires additional steps by the sys admin.

The parts of the scripts that perform the file ownership change still use the value of the $RUNAS variable, and are not hardcoded to use the opennms user.

These scripts should update file ownership to match the $RUNAS user instead of bailing.

Environment

Red Hat and Debian Linux distributions

Acceptance / Success Criteria

None

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created April 16, 2024 at 9:09 PM
Updated April 17, 2024 at 5:37 PM
Resolved April 17, 2024 at 5:37 PM

Activity

Show:

Benjamin ReedApril 17, 2024 at 5:37 PM

Merged to `foundation-2024` (and up)

Will KeaneyApril 17, 2024 at 3:34 PM

Will KeaneyApril 16, 2024 at 10:01 PM