Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 28.0.0
-
Fix Version/s: 28.0.1
-
Component/s: Minion
-
Security Level: Default (Default Security Scheme)
-
Labels:
-
Sprint:Horizon 2021 - May 26 - June 9, Horizon 2021 - Jun 9 - Jun 23
-
HB Backlog Status:Backlog NG
Description
I'm running Minion containers and since 28.0.0 the containers refuse to start.
Starting minion ... done Attaching to minion minion | WARNING: Credentials can be exposed via docker inspect and log files. Please consider to use a keystore file. minion | You can initialize a keystore file with the -s option. minion | [main] INFO org.opennms.features.scv.jceks.JCEKSSecureCredentialsVault - Loading existing keystore from: scv.jce minion | [main] INFO org.opennms.features.scv.jceks.JCEKSSecureCredentialsVault - Loading existing keystore from: scv.jce minion | OpenNMS Minion is already configured, skipped. minion | No configuration key store present, skipping confd configuration. minion | appending to custom.system.properties: /opt/minion/etc/opennms.properties.d/*.properties minion | cat: '/opt/minion/etc/opennms.properties.d/*.properties': No such file or directory minion exited with code 1
It seems that changes in NMS-13101 caused this.
