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
Update prow deployment script #8608
Update prow deployment script #8608
Conversation
2b98c5f
to
d2bc0b5
Compare
@pcbailey: PR needs rebase. 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/test-infra repository. |
d2bc0b5
to
8509513
Compare
VIRTCTL_DOWNLOAD_URL="https://github.com/kubevirt/kubevirt/releases/download/${KUBEVIRT_VERSION}/virtctl-${KUBEVIRT_VERSION}" | ||
VIRTCTL_X86_64="${VIRTCTL_DOWNLOAD_URL}-linux-x86_64" | ||
VIRTCTL_AMD64="${VIRTCTL_DOWNLOAD_URL}-linux-amd64" | ||
HCO_VERSION="master" |
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.
can we use some version that works for us, o/w we may get stuck with broken master (now called main) versions ?
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.
The latest release doesn't install the common templates. I think we should leave it at master/main until they release again.
frontend/packages/kubevirt-plugin/integration-tests/deploy-kubevirt-gating.sh
Outdated
Show resolved
Hide resolved
8509513
to
ab2c17e
Compare
25b7d9c
to
6eb429c
Compare
/test kubevirt-plugin |
1 similar comment
/test kubevirt-plugin |
|
||
VIRTCTL_DOWNLOAD_URL="https://github.com/kubevirt/kubevirt/releases/download/${KUBEVIRT_VERSION}/virtctl-${KUBEVIRT_VERSION}" |
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.
if you remove the VIRTCTL_DOWNLOAD_URL
how does it know where to get the virtctl command line from ?
22a6a17
to
417b5b7
Compare
/test kubevirt-plugin |
6b1b784
to
708553b
Compare
/retest |
data: | ||
feature-gates: "DataVolumes,SRIOV,LiveMigration,CPUManager,CPUNodeDiscovery,Sidecar,Snapshot" | ||
EOF | ||
oc get -n openshift template windows10-desktop-large |
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 -n openshift template windows10-desktop-large | |
output=$(oc get -n openshift template windows10-desktop-large 2>/dev/null) |
/lgtm |
/lgtm cancel |
8f9cc75
to
7df526b
Compare
mkdir virtctl | ||
|
||
wget ${VIRTCTL_AMD64} -O virtctl/virtctl || wget ${VIRTCTL_X86_64} -O virtctl/virtctl | ||
[[ ! -f "virtctl/virtctl" ]] && echo "ERROR: virtctl binary is unavailable for download" && exit 1 | ||
|
||
chmod +x virtctl/virtctl | ||
|
||
export PATH="${PATH}:$(pwd)/virtctl" | ||
export PATH="${PATH}:$(pwd)/virtctl/virtctl" |
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.
hmm, are you sure ?
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.
During my testing, it didn't recognize it without adding that. I saw the error that virtctl couldn't be found, though. I don't know why adding something to the path would be different in CI vs other methods, but I'll change it back. I found it odd that I had to change it in the first place since we've been using this in the current deploy script for some time now.
@pcbailey hi, the test that fails tests for "redhat support" label on a template and expect it to be missing ... so the install script worked correctly, now we need to understand why the test is failing when we add redhat support (test is wrong ? we have a bug the test caught ? ... ) |
@yaacov I'll look into it. I'm assuming the test is currently written with the expectation that the support label will not be there since our CI installation currently doesn't add the support annotations. |
@gouyang hi, do you know if we should test with "templates support annotations" or without them (e.g. downstream or upstream) ? |
9e740f4
to
fd4bc4f
Compare
fd4bc4f
to
fb2a97b
Compare
/test kubevirt-plugin |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pcbailey, yaacov The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test kubevirt-plugin |
/test ci/prow/analyze |
@pcbailey: The specified target(s) for
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/test-infra repository. |
/test analyze |
/test kubevirt-plugin |
/retest Please review the full test history for this PR and help us cut down flakes. |
This script will replace the current installation of KubeVirt on prow with an HCO installation. It will also add the Red Hat support annotations to Red Hat supported templates.
Depends on #8654