Minion container v28.0.0 refuse to start
Description
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Christian Pape June 14, 2021 at 11:18 AM
Merged.
Christian Pape June 9, 2021 at 6:37 AM
Please review:
fooker June 2, 2021 at 2:57 PM
I think right way to do this is:
Christian Pape June 2, 2021 at 2:09 PM
A workaround is to bind a volume to `/opt/minion/etc/opennms.properties.d` and put an empty .properties file inside. It seems the existence of the directory is not sufficient.
Stefan Wachter June 2, 2021 at 11:11 AMEdited
The relevant code part in entrypoint.sh is:
Can someone explain why
does not expand the asterisk? Is there a special behavior in case the directory is empty?
Fixed
Details
Details
Assignee
Christian PapeReporter
Christian PapeLabels
HB Backlog Status
Backlog NG
Components
Sprint
None
Fix versions
Affects versions
Priority
MajorPagerDuty
PagerDuty Incident
PagerDuty
PagerDuty Incident
Created June 2, 2021 at 8:57 AM
Updated July 1, 2021 at 8:54 PM
Resolved June 14, 2021 at 11:18 AM
I'm running Minion containers and since 28.0.0 the containers refuse to start.
It seems that changes in NMS-13101 caused this.