Uploaded image for project: 'OpenShift Core Networking'
  1. OpenShift Core Networking
  2. CORENET-4229 Post-merge Testing
  3. CORENET-4390

HCP to support mgmt on 4.13 (non-OVNIC) and hosted on 4.14 (OVN-IC) and mgmt to upgrade to 4.14

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • None

      rhn-support-heli rhn-support-jiezhao We probably need your help covering a scenario/template probably for this to run on prow regularly. I am not sure if there is already one. Please advise.

      4.13 is NON OVN IC release and 4.14 is with OVNIC changes (different OVN arch)

      We need to make sure users can keep mgmt on 4.13 say and only install OVN IC builds 4.14 on Hosted and HCP should work fine on this inter-op usecase.

       

      Currently I understand our Jenkins framework can support `n` build for mgmt and `n+1` for hosted based on right LAUNCHER_VARS which I can test manually

              rhn-support-heli He Liu
              anusaxen Anurag Saxena
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: