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

MicroShift does not find lvmd config if no microshift config file exists.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • openshift-4.12
    • None
    • None
    • None
    • uShift Sprint 228

      Description of problem:

      PR #1151 changed the default config file name in the rpm spec from config.yaml to config.yaml.default.  This broke the logic for discovering the lvmd.yaml file, which assumed co-location with config.yaml.  If the config.yaml doesn't exist, the logic bails out and provides default values.  Because host storage environments are typically unique, with LVM volume groups must be provided to MicroShift, users nearly always need to define their own lvmd config.

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

      n/a

      How reproducible:

      100%
      Either
      a) a host does not have a VG named "rhel", in which case the topolvm-node fails to start or ...
      b) a "rhel" vg is present, meaning the user-specified lvmd.config file is quietly ignored.

      Steps to Reproduce:

      1. Configure a host without a "rhel" VG
      2. Start MicroShift
      

       

            jcope@redhat.com Jon Cope
            jcope@redhat.com Jon Cope
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: