-
Notifications
You must be signed in to change notification settings - Fork 199
AGENT-1207: automate OVE cluster installation #1796
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
AGENT-1207: automate OVE cluster installation #1796
Conversation
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`, `oc get clusterversion`, `oc get packagemanifests` and `oc wait clusterversion version --for=condition=Available=True --timeout=60m` - Ensuring the number of nodes matches values defined in dev-scripts
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cc @andfasano |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @pawanpinjarkar for the update, it's definitely an improvement and the number of vendored files has been reduced. The post validation part still needs some additional tweaks.
This version looks good for having a better CI job, but once consolidated though, I'd prefer to find a way to remove such all golang files from this repo, so I'd advise to schedule a card for such task
exit 0 | ||
oc wait clusterversion version --for=condition=Available=True --timeout=60m | ||
oc get csv -A | ||
oc get packagemanifests -n openshift-marketplace |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are these two commands for? It doesn't seem they are testing anything. I was expecting a more explicit check on the list of installed operators
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oc get csv -A
is not useful seems like. oc get packagemanifests -n openshift-marketplace
gives a list of operators , e.g.
oc get packagemanifests -n openshift-marketplace
Member
NAME CATALOG AGE
kubernetes-nmstate-operator 3d20h
kubevirt-hyperconverged 3d20h
node-healthcheck-operator 3d20h
fence-agents-remediation 3d20h
mtv-operator 3d20h
cluster-kube-descheduler-operator 3d20h
node-maintenance-operator 3d20h
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are these two commands for? It doesn't seem they are testing anything. I was expecting a more explicit check on the list of installed operators
Could you suggest what else we should be testing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andfasano Created this task https://issues.redhat.com/browse/AGENT-1304
exit 1 | ||
fi | ||
|
||
oc get clusterversion |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And also this one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought this to be a good way to see the cluster version
e.g. oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.19.7 True False 3d19h Error while reconciling 4.19.7: the cluster operator insights is not available
rendezvousIP=$(getRendezvousIP) | ||
get_vips | ||
# Simulate user actions as done on the webUI and start cluster installation | ||
RENDEZVOUS_IP=$rendezvousIP OCP_DIR=$OCP_DIR INGRESS_VIP=$INGRESS_VIPS API_VIP=$API_VIPS go run -mod vendor agent/isobuilder/ui_driven_cluster_installation.go |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a blocking point, but wouldn't it have been simpler to pass them as a regular args?
@pawanpinjarkar it looks like the |
/retest e2e-agent-iso-no-registry-compact-ipv4 |
@pawanpinjarkar: The
The following commands are available to trigger optional jobs:
Use
In response to this:
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. |
The job is not passing from past few days. Will take a look. Thanks. |
/test e2e-agent-iso-no-registry-compact-ipv4 |
1 similar comment
/test e2e-agent-iso-no-registry-compact-ipv4 |
The assisted UI does not come up while this is not the same behaviour locally. |
/test e2e-agent-iso-no-registry-compact-ipv4 |
/test e2e-agent-iso-no-registry-compact-ipv4 |
4 similar comments
/test e2e-agent-iso-no-registry-compact-ipv4 |
/test e2e-agent-iso-no-registry-compact-ipv4 |
/test e2e-agent-iso-no-registry-compact-ipv4 |
/test e2e-agent-iso-no-registry-compact-ipv4 |
16d6693
to
a99c2a3
Compare
/test e2e-agent-iso-no-registry-compact-ipv4 |
Looks like a temp glitch. All jobs failed. |
/test e2e-agent-iso-no-registry-compact-ipv4 |
/test e2e-agent-iso-no-registry-compact-ipv4 |
/test e2e-agent-iso-no-registry-compact-ipv4 |
@pawanpinjarkar: The following tests failed, say
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. |
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:
oc get nodes
,oc get clusterversion
,oc get packagemanifests
andoc wait clusterversion version --for=condition=Available=True --timeout=60m
Set
Then run
make agent