Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-53204

[4.19] MicroShift 4.18 unable to start using default config.yaml

    • None
    • False
    • Hide

      None

      Show
      None

      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:

          

              pmatusza@redhat.com Patryk Matuszak
              dan5179 Dan Clark
              John George John George
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: