AGENT-1207: automate OVE cluster installation

[pawanpinjarkar]

Automates OVE cluster installation using the Go-based library go-rod in headless mode.
The workflow fills in cluster details, captures screenshots for each step, downloads
credentials, and triggers the install action without requiring a visible browser.

Verification steps include:

• Confirming cluster installation completion
• Running oc get nodes and oc get co
• Ensuring the number of nodes matches values defined in dev-scripts

Set

export AGENT_E2E_TEST_BOOT_MODE=ISO_NO_REGISTRY
export AGENT_RENDEZVOUS_NODE_HOSTNAME="${CLUSTER_NAME:-ostest}_master_2"
export OPENSHIFT_RELEASE_IMAGE=quay.io/openshift-release-dev/ocp-release:4.19.9-x86_64

Then run make agent

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign sadasu for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pawanpinjarkar]

/cc @rwsu

[openshift-ci]

@pawanpinjarkar: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-agent-iso-no-registry-compact-ipv4	8e02ff8	link	false	/test e2e-agent-iso-no-registry-compact-ipv4
ci/prow/e2e-metal-ipi-ovn-dualstack	8e02ff8	link	false	/test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-metal-ipi-bm	8e02ff8	link	true	/test e2e-metal-ipi-bm
ci/prow/e2e-metal-ovn-arbiter	8e02ff8	link	false	/test e2e-metal-ovn-arbiter
ci/prow/e2e-metal-ipi-virtualmedia	8e02ff8	link	false	/test e2e-metal-ipi-virtualmedia
ci/prow/e2e-metal-ipi-bm-bond	8e02ff8	link	false	/test e2e-metal-ipi-bm-bond
ci/prow/e2e-metal-ipi-serial-ipv4-1of2	8e02ff8	link	true	/test e2e-metal-ipi-serial-ipv4-1of2
ci/prow/e2e-metal-ipi-serial-ipv4-2of2	8e02ff8	link	true	/test e2e-metal-ipi-serial-ipv4-2of2
ci/prow/e2e-metal-ipi-serial-ovn-ipv6	8e02ff8	link	false	/test e2e-metal-ipi-serial-ovn-ipv6
ci/prow/e2e-metal-ipi-ovn-ipv6	8e02ff8	link	true	/test e2e-metal-ipi-ovn-ipv6

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[andfasano]

This go program seems to do much more things than expected. The original goal was just to automate the UI value insertion. I didn't go through all the details, but all the part related to waiting seems a (partial) duplicate of what we already have.

[pawanpinjarkar]

The go-lang code in this file, does 2 main things - automate inserting user provided values in UI, capturing screenshots of each step/page and finally start/monitor cluster installation.

Monitoring cluster installation is duplicated from main installer code repo here https://github.com/openshift-metal3/dev-scripts/pull/1781/files#diff-4fa267ac514a8d80c180951b590be1e52cf0122057a8c833fd0d954e143f2220R344-R746

[pawanpinjarkar]

Alternate approach #1796 Closing this as we don't want to duplicate golang code for wait-for commands from installer.