-
Notifications
You must be signed in to change notification settings - Fork 107
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
[release-ocm-2.7] Update default tag for index and service #2018
[release-ocm-2.7] Update default tag for index and service #2018
Conversation
@@ -42,9 +42,9 @@ CONTAINER_RUNTIME_COMMAND := $(or ${CONTAINER_COMMAND}, ${CONTAINER_RUNTIME_COMM | |||
LINT_CODE_STYLING_DIRS := src/tests src/triggers src/assisted_test_infra/test_infra src/assisted_test_infra/download_logs src/service_client src/consts src/virsh_cleanup src/cli | |||
|
|||
# assisted-service | |||
SERVICE := $(or $(SERVICE), quay.io/edge-infrastructure/assisted-service:latest) | |||
SERVICE := $(or $(SERVICE), quay.io/edge-infrastructure/assisted-service:ocm-2.7) |
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 wonder if we can make some adjustments that don't demand us to handle all those tag changes for the branches
I mean, if anything I would assume we override SERVICE
somewhere to use the right service image, and not use the default. Is it not the case?
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.
You're right, I'll see if I can do it from release repo
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 yes SERVICE shouldn't be required
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.
you know what, maybe this change is good for easing local testing of this version
/test ci/prow/e2e-metal-assisted-kube-api-late-binding-single-node |
@adriengentil: The specified target(s) for
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/test-infra repository. |
/test ci/prow/e2e-metal-assisted-kube-api-late-binding-single-node |
@adriengentil: The specified target(s) for
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/test-infra repository. |
/test e2e-metal-assisted-kube-api-late-binding-single-node |
/test e2e-metal-assisted-ha-kube-api-ipv6 |
/test e2e-metal-assisted-kube-api-late-binding-single-node |
@osherdp @eliorerz
it seems we provide IPv4 addresses to the configuration and as a consequence, the validation fails because we mix IPv4/6. Does it ring a bell to you? |
I think (but really not sure anymore) that we're missing an I am not sure how it happened though, maybe something we changed by mistake? Those jobs usually get less importance and treatment as the ztp ones are more comprehensive and simulate the use-case in a better way You can open a bug on it, @eliorerz can probably debug it pretty quickly if needed |
/retest |
/override ci/prow/e2e-metal-assisted-ha-kube-api-ipv6 |
@adriengentil: Overrode contexts on behalf of adriengentil: ci/prow/e2e-metal-assisted-ha-kube-api-ipv6 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. |
/override ci/prow/e2e-metal-assisted-ha-kube-api-ipv6 |
@adriengentil: The specified target(s) for
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/test-infra repository. |
@adriengentil: Overrode contexts on behalf of adriengentil: ci/prow/e2e-metal-assisted-ha-kube-api-ipv6 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 e2e-vsphere-assisted-kube-api |
1 similar comment
/test e2e-vsphere-assisted-kube-api |
@osherdp let's merge it? |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adriengentil, osherdp 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 |
@adriengentil: The following test 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. |
e2e-metal-assisted-ha-kube-api-ipv6
,e2e-metal-assisted-kube-api-late-binding-single-node
ande2e-metal-assisted-kube-api-late-unbinding-single-node
jobs are currently permafailing.I suspect it's because the index not being aligned with branch version.