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

MicroShift config ingress error from default

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.16
    • MicroShift
    • None
    • Low
    • No
    • 1
    • uShift Sprint 255, uShift Sprint 256
    • 2
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

      Description of problem:

      When you copy the config.yaml from defaults and do not configure ingress, the microshift will fail to start with error:
      
      Jun 13 20:43:24 node-0 microshift[8824]: ??? E0613 20:43:24.440185    8824 run.go:74] "command failed" err="invalid configuration: error validating ingress.listenAddress: interface  not present in the host"
      

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

      4.16
      

      How reproducible:

      - copy the config.yaml from default, do not fill in "ingress.listenAddress.
      

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

      
      

      Expected results:

      - improvement should be that when config.yaml.defaults will be created, the listenAddress will be propagated from the current host
      - put this in the docs as requirement or set the microshift to ignore that value and take default interface (based on default route) as listenAddress
      

      Additional info:

      
      

              pacevedo@redhat.com Pablo Acevedo Montserrat
              rhn-support-vwalek Vladislav Walek
              John George John George
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: