-
Notifications
You must be signed in to change notification settings - Fork 35
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
NETOBSERV-889: fix too many colons in address error #98
NETOBSERV-889: fix too many colons in address error #98
Conversation
@msherif1234: This pull request references NETOBSERV-889 which is a valid jira issue. 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. |
@msherif1234: This pull request references NETOBSERV-889 which is a valid jira issue. 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. |
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #98 +/- ##
==========================================
+ Coverage 41.61% 42.00% +0.39%
==========================================
Files 29 30 +1
Lines 1992 2002 +10
==========================================
+ Hits 829 841 +12
+ Misses 1125 1123 -2
Partials 38 38
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
/ok-to-test |
New image: ["quay.io/netobserv/netobserv-ebpf-agent:20a990e"]. It will expire after two weeks. |
@msherif1234 Tried updating the CSV with this eBPF image, the eBPF pods went to CrashLoopBackoff with error |
I get the same above error with source install too; after updating the eBPF image in deployments |
/ok-to-test |
New image: ["quay.io/netobserv/netobserv-ebpf-agent:0816e2c"]. It will expire after two weeks. |
/ok-to-test |
New image: ["quay.io/netobserv/netobserv-ebpf-agent:f073254"]. It will expire after two weeks. |
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.
/lgtm
/ok-to-test |
New image: ["quay.io/netobserv/netobserv-ebpf-agent:ceaa4ca"]. It will expire after two weeks. |
tried this more and discussed error with @msherif1234 , our initial understanding of not being able to pull image: quay.io/netobserv/netobserv-ebpf-agent:ceaa4ca from quay was incorrect, it was able to pull Image and landing in above runtime error. This is likely a bug with new code. |
/ok-to-test |
New image: ["quay.io/netobserv/netobserv-ebpf-agent:a8e0892"]. It will expire after two weeks. |
Signed-off-by: msherif1234 <[email protected]>
/ok-to-test |
New image: ["quay.io/netobserv/netobserv-ebpf-agent:3652daa"]. It will expire after two weeks. |
/qe-approved |
@jotak - is something wrong with labels? I don't see qe-approved label being added. |
@msherif1234: This pull request references NETOBSERV-889 which is a valid jira issue. 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. |
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.
LGTM
thanks @msherif1234 ! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jotak 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 |
Signed-off-by: msherif1234 <[email protected]>
This PR fixed two issues
1- when hostIP is IPv6 address we endup with following error when gRPC try to connect
for IPv6 we need to use
[2604:1380:4642:7e00::5b]:2055
format.2- on single stack ipv6 cluster with IPType=="any" , ipv4 DNS address was incorrectly used which prevented ebpf agent to come up and the pod stay in crashloop with this error:-
Signed-off-by: msherif1234 [email protected]