XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • openshift-4.14
    • None
    • None
    • None
    • Allow PXE-booting the agent image
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • In Progress
    • OCPSTRAT-592 - PXE Support for Agent
    • OCPSTRAT-592PXE Support for Agent
    • 0% To Do, 0% In Progress, 100% Done
    • S
    • Hide

      14/Aug/2023

      Green

       

      27/Jun/2023

      Green

       

      05/Jun/2023

      Green

       

      27/April/2023

      AGENT-510 "Support interactive network console when PXE booting" cannot be tested on dev-eng local machine - collaboration needed with QE who have access to an environment - further clarity is needed here. If there are no issues here we are not at risk here but if there are we need to do further investigation.

      AGENT-439 will require a learning curve and potentially additional support.

      AGENT-440 need to look into CI infrastructure

      Show
      14/Aug/2023 Green   27/Jun/2023 Green   05/Jun/2023 Green   27/April/2023 AGENT-510 "Support interactive network console when PXE booting" cannot be tested on dev-eng local machine - collaboration needed with QE who have access to an environment - further clarity is needed here. If there are no issues here we are not at risk here but if there are we need to do further investigation. AGENT-439 will require a learning curve and potentially additional support. AGENT-440 need to look into CI infrastructure
    • Sprint 236

      Epic Goal

      As an OpenShift installation admin I want to PXE-boot the image generated by the openshift-install agent subcommand

      Why is this important?

      We have customers requesting this booting mechanism to make it easier to automate the booting of the nodes without having to actively place the generated image in a bootable device for each host.

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

            ppinjark@redhat.com pawan pinjarkar
            racedoro@redhat.com Ramon Acedo
            Manoj Hans Manoj Hans
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: