-
Bug
-
Resolution: Done
-
Undefined
-
4.18
-
None
-
False
-
Description of problem:
Microshift will not restart when using its own example config.yaml
Version-Release number of selected component (if applicable):
4.18.2
How reproducible:
100%
Steps to Reproduce:
1. sudo dnf -y install microshift 2. sudo systemctl enable --now microshift 3. wait for microshift to start successfully 4. sudo systemctl stop microshift 5. sudo cp /etc/microshift/conf.yaml.default /etc/microshift/config.yaml 6. sudo systemctl start microshift # No changes of any kind were made to the config.yaml. We copied the config.yaml.default to config.yaml in preparation to make changes but had to stop for the day. When we tried starting everything back up the next day, we hit this problem. Microshift should be able to start using its own default config file unedited.
Actual results:
??? E0312 10:21:41.737385 5135 run.go:72] "command failed" err="failed to unmarshal user cfg json to config: time: invalid duration \"\""
Expected results:
Microshift starts back up with no errors
Additional info:
- clones
-
OCPBUGS-53026 MicroShift 4.18 unable to start using default config.yaml
-
- Verified
-
- duplicates
-
USHIFT-5282 Starting microshift service fails with standard config
-
- Closed
-
- is depended on by
-
OCPBUGS-53026 MicroShift 4.18 unable to start using default config.yaml
-
- Verified
-