-
Notifications
You must be signed in to change notification settings - Fork 383
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
WIP: BCC and conntrack #744
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: michaelgugino 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 |
@michaelgugino: 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/test-infra repository. I understand the commands that are listed here. |
Update `SOURCE_GIT_TAG` parsing logic to correctly identify the new tag format: `openshift-clients-<version>`. It fixes openshift#1688, openshift#744, openshift#740. Previously, it incorrectly returned `v4.2.0-alpha.0` for all releases.
Update `SOURCE_GIT_TAG` parsing logic to correctly identify the new tag format: `openshift-clients-<version>`. It fixes openshift#1688, openshift#744, openshift#740. Previously, it incorrectly returned `v4.2.0-alpha.0` for all releases.
Update `SOURCE_GIT_TAG` parsing logic to correctly identify the new tag format: `openshift-clients-<version>`. It fixes openshift#1688, openshift#744, openshift#740. Previously, it incorrectly returned `v4.2.0-alpha.0` for all releases.
Update `SOURCE_GIT_TAG` parsing logic to correctly identify the new tag format: `openshift-clients-<version>`. It fixes openshift#1688, openshift#744, openshift#740. Previously, it incorrectly returned `v4.2.0-alpha.0` for all releases.
No description provided.