-
Notifications
You must be signed in to change notification settings - Fork 149
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
Fix bug and change cri selection procedure of cluster-sync #2155
Conversation
Hi @jcanocan. Thanks for your PR. I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Hi @jcanocan. Thanks for your PR. I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/cc @tiraboschi |
cluster/sync.sh
Outdated
@@ -1,15 +1,15 @@ | |||
#!/bin/bash -ex | |||
|
|||
source ./hack/common.sh | |||
source ${PWD}/_kubevirtci/cluster-up/cluster/ephemeral-provider-common.sh |
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.
Use same path style as above? .
instead of ${PWD}
?
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 agree.
cluster/sync.sh
Outdated
container_command=podman | ||
|
||
registry_port=$(${container_command} ps | grep -Po '(?<=0.0.0.0:)\d+(?=->5000\/tcp)' || echo "") | ||
container_command=$_cri_bin |
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.
Why not replace container_command
with _cri_bin
everywhere?
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.
Makes sense for me too.
cluster/sync.sh
Outdated
|
||
registry_port=$(${container_command} ps | grep -Po '(?<=0.0.0.0:)\d+(?=->5000\/tcp)' | head -n 1) |
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.
Did you check if the regex works for both podman and docker?
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.
Yes, I just checked it.
The command for getting the registry port gets more than one output, which breaks following commands in the deploying scripts. The output is now parsed to pickup just the first port. Also the container runtime selection was hardcoded, now it uses the cri selection script of kubervirtci. Co-authored-by: Felix Matouschek <fmatouschek@redhat.com> Signed-off-by: Javier Cano Cano <jcanocan@redhat.com>
c5dd3ec
to
e2b19e2
Compare
Kudos, SonarCloud Quality Gate passed! |
/lgtm |
/ok-to-test |
Pull Request Test Coverage Report for Build 3533846405
💛 - Coveralls |
Coverage reduction seems not related to this PR, because it does not change code nor unit tests. /override coverage/coveralls |
@nunnatsa: Overrode contexts on behalf of nunnatsa: coverage/coveralls 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nunnatsa 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 |
…#2155) The command for getting the registry port gets more than one output, which breaks following commands in the deploying scripts. The output is now parsed to pickup just the first port. Also the container runtime selection was hardcoded, now it uses the cri selection script of kubervirtci. Co-authored-by: Felix Matouschek <fmatouschek@redhat.com> Signed-off-by: Javier Cano Cano <jcanocan@redhat.com> Signed-off-by: Javier Cano Cano <jcanocan@redhat.com> Co-authored-by: Felix Matouschek <fmatouschek@redhat.com>
* [release-1.8] Align github actions from newer branches Backport a few configuration changes in github actions. Signed-off-by: stirabos <stirabos@redhat.com> * Fix bug and change cri selection procedure of cluster-sync. (#2155) The command for getting the registry port gets more than one output, which breaks following commands in the deploying scripts. The output is now parsed to pickup just the first port. Also the container runtime selection was hardcoded, now it uses the cri selection script of kubervirtci. Co-authored-by: Felix Matouschek <fmatouschek@redhat.com> Signed-off-by: Javier Cano Cano <jcanocan@redhat.com> Signed-off-by: Javier Cano Cano <jcanocan@redhat.com> Co-authored-by: Felix Matouschek <fmatouschek@redhat.com> * cluster-up: Fix tag updating (#2189) In case the _kubevirtci folder exists, changing the tag won't reclone the folder. The cluster-up folder won't be updated and it can lead to bugs in case the folder is changed. Fix it by deleting the folder in case of tag mismatch. It will enforce a reclone. Signed-off-by: Or Shoval <oshoval@redhat.com> Signed-off-by: Or Shoval <oshoval@redhat.com> * Bump the default kubevirtci provider Signed-off-by: stirabos <stirabos@redhat.com> * Workaround for SELinux boolean for chardev Workaround for kubevirt/kubevirt#9434 we started setting SELinux boolean for chardev access with kubevirt/kubevirtci#968 but it got reverted with kubevirt/kubevirtci#975 altough it's still needed with Kubevirt v0.58.1 TODO: let's remove this once kubevirt/kubevirt#9434 is fixed Signed-off-by: stirabos <stirabos@redhat.com> --------- Signed-off-by: stirabos <stirabos@redhat.com> Signed-off-by: Javier Cano Cano <jcanocan@redhat.com> Signed-off-by: Or Shoval <oshoval@redhat.com> Co-authored-by: Javier Cano Cano <jcanocan@redhat.com> Co-authored-by: Felix Matouschek <fmatouschek@redhat.com> Co-authored-by: oscollabus <oshoval@redhat.com>
The command for getting the registry port gets more than one output, which breaks following commands in the deploying scripts. The output is now parsed to pickup just the first port.
Also the container runtime selection was hardcoded, now it uses the cri selection script of kubervirtci.
Further details can be found at issue 2153
Fixes #2153
Reviewer Checklist
Release note: