Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-5282

Starting microshift service fails with standard config

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • openshift-4.19
    • None
    • None
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 3
    • None
    • None
    • uShift Sprint 265, uShift Sprint 266
    • None
    • None
    • None

      Description of problem:

      
      I am testing microshift version 4.19.0~ec.0 and before starting the service I am doing cp /etc/microshift/config.yaml.default /etc/microshift/config.yaml and service failed.
      
      

      Version-Release number of selected component (if applicable):

      $ microshift version
      MicroShift Version: 4.19.0~ec.0
      Base OCP Version: 4.19.0-ec.0
      

      How reproducible:

      Everytime
      

      Steps to Reproduce:

      1. Install provided version of microshift
      2. sudo cp /etc/microshift/config.yaml.default /etc/microshift/config.yaml
      3. sudo systemctl start microshift
      

      Actual results:

      Failed to start service
      

      Expected results:

      Service should be started with standard config
      

      Additional info:

      systemd[1]: Stopped MicroShift.
      systemd[1]: Starting MicroShift...
      microshift[16219]: ??? I0113 14:01:12.826688   16219 run.go:65] "Version" microshift="4.19.0~ec.0" base="4.19.0-ec.0"
      microshift[16219]: ??? E0113 14:01:12.839994   16219 run.go:72] "command failed" err="failed to unmarshal user cfg json to config: time: invalid duration \"\""
      systemd[1]: microshift.service: Main process exited, code=exited, status=1/FAILURE
      systemd[1]: microshift.service: Failed with result 'exit-code'.
      

              pmatusza@redhat.com Patryk Matuszak
              prkumar@redhat.com Praveen Kumar
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: