Skip to content
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

[kube ovn]dual stack #8619

Closed

Conversation

liupeng0518
Copy link
Member

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

/kind feature

What this PR does / why we need it:
kube ovn support dual stack
kube ovn upgrade to v1.9.1

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 10, 2022
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: liupeng0518
To complete the pull request process, please assign miouge1 after the PR has been reviewed.
You can assign the PR to them by writing /assign @miouge1 in a comment when ready.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@cristicalin
Copy link
Contributor

Hi @liupeng0518 , thanks for looking into this.
I see that there is still a failure on the ovn CI job: https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/jobs/2192359189 could you solve this?

@liupeng0518
Copy link
Member Author

I test ok, in my env

/retest

@liupeng0518
Copy link
Member Author

@oilbeater
Can you check this dual stack problem together:

==== START logs for container install-cni of pod kube-system/kube-ovn-cni-842xc ====
==== END logs for container install-cni of pod kube-system/kube-ovn-cni-842xc ====
==== START logs for container cni-server of pod kube-system/kube-ovn-cni-842xc ====
previous socket exists, remove and continue
I0314 13:55:19.003365    7614 cniserver.go:29] 
-------------------------------------------------------------------------------
Kube-OVN: 
  Version:       v1.9.1
  Build:         2022-03-10_02:02:45
  Commit:        git-46eb49a
  Go Version:    go1.17.5
  Arch:          amd64
-------------------------------------------------------------------------------
I0314 13:55:19.030407    7614 config.go:223] no --kubeconfig, use in-cluster kubernetes config
I0314 13:55:19.046901    7614 config.go:125] daemon config: &{ 1400 1360 true mirror0 /run/openvswitch/kube-ovn-daemon.sock /run/openvswitch/db.sock  0xc000032d80 0xc000704dd0 k8s-2 10.233.0.0/18,fd85:ee78:d8a6:8607::1000/116  false 10665 geneve provider  kube-system}
I0314 13:55:19.052898    7614 cniserver.go:137] finish adding chassis annotation
I0314 13:55:19.185832    7614 ovs.go:339] 100.64.0.4 network ready after 1 ping, gw 100.64.0.1
I0314 13:55:19.190788    7614 server.go:32] start listen on /run/openvswitch/kube-ovn-daemon.sock
I0314 13:55:19.325920    7614 controller.go:1316] Started workers
I0314 13:55:19.326215    7614 controller.go:747] route to add [10.233.64.0/18]
I0314 13:55:25.063907    7614 controller.go:747] route to add [fd00:100:64::/64]
I0314 13:55:25.081804    7614 controller.go:747] route to add [fd00:100:64::/64 fd85:ee78:d8a6:8607::1:0/112]
I0314 13:55:27.729313    7614 server.go:63] [2022-03-14T13:55:27Z] Incoming HTTP/1.1 POST /api/v1/add request
I0314 13:55:27.729430    7614 handler.go:77] add port request {kube-ovn kube-ovn-pinger-58p2g kube-system f8b679e7ddbdb9376e53ca8f54986f85d9cce41152810ddf51a5a815124c2a54 /var/run/netns/cni-ce3105dd-591a-9fdb-a98e-adf88511e3e4 eth0 ovn []  }
I0314 13:55:27.729448    7614 handler.go:93] wait address for pod kube-system/kube-ovn-pinger-58p2g provider ovn
I0314 13:55:28.297293    7614 controller.go:747] route to add [fd00:100:64::/64 fd85:ee78:d8a6:8607::1:0/112]
I0314 13:55:28.316704    7614 controller.go:747] route to add [fd00:100:64::/64 fd85:ee78:d8a6:8607::1:0/112]
I0314 13:55:28.374150    7614 controller.go:747] route to add [fd00:100:64::/64 fd85:ee78:d8a6:8607::1:0/112]
I0314 13:55:28.403302    7614 controller.go:747] route to add [fd85:ee78:d8a6:8607::1:0/112 fd00:100:64::/64]
I0314 13:55:28.426544    7614 controller.go:747] route to add [fd00:100:64::/64 fd85:ee78:d8a6:8607::1:0/112]
I0314 13:55:28.458539    7614 controller.go:747] route to add [fd00:100:64::/64 fd85:ee78:d8a6:8607::1:0/112]
I0314 13:55:28.730344    7614 handler.go:93] wait address for pod kube-system/kube-ovn-pinger-58p2g provider ovn
I0314 13:55:29.731437    7614 handler.go:93] wait address for pod kube-system/kube-ovn-pinger-58p2g provider ovn
I0314 13:55:30.735798    7614 handler.go:93] wait address for pod kube-system/kube-ovn-pinger-58p2g provider ovn
I0314 13:55:31.736799    7614 handler.go:93] wait address for pod kube-system/kube-ovn-pinger-58p2g provider ovn
I0314 13:55:32.737237    7614 handler.go:93] wait address for pod kube-system/kube-ovn-pinger-58p2g provider ovn
I0314 13:55:33.737561    7614 handler.go:93] wait address for pod kube-system/kube-ovn-pinger-58p2g provider ovn
I0314 13:55:34.410194    7614 controller.go:747] route to add [fd85:ee78:d8a6:8607::1:0/112 fd00:100:64::/64]
E0314 13:55:34.410431    7614 controller.go:689] failed to add route no route to host
E0314 13:55:34.410506    7614 controller.go:689] failed to add route no route to host
I0314 13:55:34.760741    7614 handler.go:216] create container interface eth0 mac 00:00:00:ED:5D:E6, ip 10.233.64.5/18,fd85:ee78:d8a6:8607::1:8/112, cidr 10.233.64.0/18,fd85:ee78:d8a6:8607::1:0/112, gw 10.233.64.1,fd85:ee78:d8a6:8607::1:1, custom routes []
I0314 13:55:34.789960    7614 controller.go:747] route to add [fd00:100:64::/64 fd85:ee78:d8a6:8607::1:0/112]
E0314 13:55:34.790006    7614 controller.go:689] failed to add route no route to host
E0314 13:55:34.790024    7614 controller.go:689] failed to add route no route to host
I0314 13:55:34.972946    7614 ovs.go:339] 10.233.64.5 network ready after 1 ping, gw 10.233.64.1
I0314 13:55:37.118853    7614 ovs.go:339] fd85:ee78:d8a6:8607::1:8 network ready after 3 ping, gw fd85:ee78:d8a6:8607::1:1
I0314 13:55:37.119929    7614 server.go:71] [2022-03-14T13:55:37Z] Outgoing response POST /api/v1/add with 200 status code in 9390ms
I0314 13:55:47.229092    7614 controller.go:747] route to add [fd00:100:64::/64 fd85:ee78:d8a6:8607::1:0/112]
E0314 13:55:47.229137    7614 controller.go:689] failed to add route no route to host
E0314 13:55:47.229347    7614 controller.go:689] failed to add route no route to host
I0314 13:55:47.374213    7614 server.go:63] [2022-03-14T13:55:47Z] Incoming HTTP/1.1 POST /api/v1/add request
I0314 13:55:47.374258    7614 handler.go:77] add port request {kube-ovn netchecker-agent-2xd67 default 1a0397d793af4ccbebdfbd6e9481c22904cd293912f2dda067dd32c6b374e0b1 /var/run/netns/cni-d5f5dbe6-b858-8b61-8593-6c8764baac24 eth0 ovn []  }
I0314 13:55:47.391397    7614 handler.go:216] create container interface eth0 mac 00:00:00:A5:FD:FC, ip 10.233.64.11/18,fd85:ee78:d8a6:8607::1:b/112, cidr 10.233.64.0/18,fd85:ee78:d8a6:8607::1:0/112, gw 10.233.64.1,fd85:ee78:d8a6:8607::1:1, custom routes []
I0314 13:55:47.435318    7614 controller.go:747] route to add [fd00:100:64::/64 fd85:ee78:d8a6:8607::1:0/112]
E0314 13:55:47.435361    7614 controller.go:689] failed to add route no route to host
E0314 13:55:47.435379    7614 controller.go:689] failed to add route no route to host
I0314 13:55:47.575251    7614 ovs.go:339] 10.233.64.11 network ready after 1 ping, gw 10.233.64.1
I0314 13:55:49.256603    7614 controller.go:747] route to add [fd00:100:64::/64 fd85:ee78:d8a6:8607::1:0/112]
E0314 13:55:49.256716    7614 controller.go:689] failed to add route no route to host
E0314 13:55:49.256757    7614 controller.go:689] failed to add route no route to host
I0314 13:55:49.727075    7614 ovs.go:339] fd85:ee78:d8a6:8607::1:b network ready after 3 ping, gw fd85:ee78:d8a6:8607::1:1
I0314 13:55:49.728093    7614 server.go:71] [2022-03-14T13:55:49Z] Outgoing response POST /api/v1/add with 200 status code in 2353ms
==== END logs for container cni-server of pod kube-system/kube-ovn-cni-842xc ====

@liupeng0518
Copy link
Member Author

/retest

@liupeng0518 liupeng0518 marked this pull request as draft March 16, 2022 13:02
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 16, 2022
@floryut
Copy link
Member

floryut commented Mar 16, 2022

@liupeng0518 could you put the ovn dual stack test in unit-tests or at least step 1 ? running all the pipeline everytime seems a little overkill

@liupeng0518 liupeng0518 force-pushed the kube_ovn_dual_stack branch from 44d1839 to f6c6658 Compare March 17, 2022 07:22
@liupeng0518 liupeng0518 force-pushed the kube_ovn_dual_stack branch from f6c6658 to 612a326 Compare March 17, 2022 10:18
@liupeng0518 liupeng0518 force-pushed the kube_ovn_dual_stack branch from 5f7fe59 to 6e7058a Compare April 20, 2022 01:15
@liupeng0518
Copy link
Member Author

/retest

@k8s-ci-robot
Copy link
Contributor

@liupeng0518: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-kubespray-yamllint 6e7058a link true /test pull-kubespray-yamllint

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

@cristicalin
Copy link
Contributor

Hi @liupeng0518 , this PR needs to be rebased on the latest state of the master branch to address the packet CI failure.

@liupeng0518
Copy link
Member Author

/close

@k8s-ci-robot
Copy link
Contributor

@liupeng0518: Closed this PR.

In response to this:

/close

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.

@floryut
Copy link
Member

floryut commented May 5, 2022

/close

too bad :( the update to 1.9.x was at least needed 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants