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

misc: bump net-next vagrant box version #9657

Merged
merged 1 commit into from Feb 28, 2020
Merged

misc: bump net-next vagrant box version #9657

merged 1 commit into from Feb 28, 2020

Conversation

borkmann
Copy link
Member

@borkmann borkmann commented Nov 25, 2019

Add the latest net-next kernel to our CI in order to provide more test
exposure for the recently merged set [0].

[0] https://lore.kernel.org/bpf/cover.1574452833.git.daniel@iogearbox.net/

Signed-off-by: Daniel Borkmann daniel@iogearbox.net


This change is Reviewable

@borkmann borkmann requested a review from a team as a code owner November 25, 2019 12:27
@@ -5,4 +5,4 @@
$SERVER_BOX = "cilium/ubuntu-dev"
$SERVER_VERSION= "164"
$NETNEXT_SERVER_BOX= "cilium/ubuntu-next"
$NETNEXT_SERVER_VERSION= "32"
$NETNEXT_SERVER_VERSION= "37"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Style/GlobalVars: Do not introduce global variables.
Layout/SpaceAroundOperators: Surrounding space missing for operator =.
Style/StringLiterals: Prefer single-quoted strings when you don't need string interpolation or special symbols.

@borkmann
Copy link
Member Author

test-me-please

@coveralls
Copy link

coveralls commented Nov 25, 2019

Coverage Status

Coverage increased (+0.04%) to 45.558% when pulling 0dd2163 on pr/update-netnext into b0a3d92 on master.

@borkmann
Copy link
Member Author

test-me-please

1 similar comment
@aanm
Copy link
Member

aanm commented Nov 26, 2019

test-me-please

@borkmann
Copy link
Member Author

test-me-please

3 similar comments
@brb
Copy link
Member

brb commented Nov 29, 2019

test-me-please

@brb
Copy link
Member

brb commented Nov 29, 2019

test-me-please

@brb
Copy link
Member

brb commented Dec 2, 2019

test-me-please

@brb
Copy link
Member

brb commented Dec 3, 2019

[2019-12-02T11:27:50.470Z] The following SSH command responded with a non-zero exit status.
[2019-12-02T11:27:50.470Z] Vagrant assumes that this means the command failed!
[2019-12-02T11:27:50.470Z] 
[2019-12-02T11:27:50.470Z] systemctl restart systemd-networkd.service
[2019-12-02T11:27:50.470Z] 
[2019-12-02T11:27:50.470Z] Stdout from the command:
[2019-12-02T11:27:50.470Z] 
[2019-12-02T11:27:50.470Z] 
[2019-12-02T11:27:50.470Z] 
[2019-12-02T11:27:50.470Z] Stderr from the command:
[2019-12-02T11:27:50.470Z] 
[2019-12-02T11:27:50.470Z] Job for systemd-networkd.service failed because a timeout was exceeded.
[2019-12-02T11:27:50.470Z] See "systemctl status systemd-networkd.service" and "journalctl -xe" for details.

🤷‍♂️

@brb
Copy link
Member

brb commented Dec 3, 2019

test-me-please

@brb
Copy link
Member

brb commented Dec 3, 2019

Tried to reproduce it locally. In dmesg I see many instances of (systemd-networkd):

[  726.129954] INFO: task (networkd):2419 blocked for more than 120 seconds.
[  726.132010]       Tainted: G        W         5.4.0+ #1
[  726.134178] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  726.136351] (networkd)      D    0  2419      1 0x00004004
[  726.136357] Call Trace:
[  726.136370]  __schedule+0x293/0x700
[  726.136376]  schedule+0x44/0xb0
[  726.136382]  request_wait_answer+0x12e/0x200
[  726.136390]  ? wait_woken+0x80/0x80
[  726.136395]  fuse_simple_request+0x16d/0x280
[  726.136402]  fuse_statfs+0xe5/0x160
[  726.136413]  statfs_by_dentry+0x6d/0x90
[  726.136419]  vfs_statfs+0x1b/0xc0
[  726.136424]  user_statfs+0x5a/0xa0
[  726.136431]  __do_sys_statfs+0x27/0x60
[  726.136438]  __x64_sys_statfs+0x16/0x20
[  726.136445]  do_syscall_64+0x57/0x190
[  726.136449]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  726.136454] RIP: 0033:0x7fef51e68977
[  726.136463] Code: Bad RIP value.
[  726.136465] RSP: 002b:00007ffd7e333438 EFLAGS: 00000246 ORIG_RAX: 0000000000000089
[  726.136470] RAX: ffffffffffffffda RBX: 000055678422b000 RCX: 00007fef51e68977
[  726.136472] RDX: 00005567840e6010 RSI: 00007ffd7e333440 RDI: 000055678422b000
[  726.136475] RBP: 00007ffd7e333440 R08: 0000000000001000 R09: 0000000000000000
[  726.136477] R10: 00007ffd7e333354 R11: 0000000000000246 R12: 00007ffd7e3334e0
[  726.136480] R13: 00007ffd7e3335d0 R14: 00005567841a5f30 R15: 00005567841a5f60

@brb
Copy link
Member

brb commented Dec 5, 2019

test-me-please

@github-actions
Copy link

github-actions bot commented Dec 5, 2019

Release note label not set, please set the appropriate release note.

@brb
Copy link
Member

brb commented Dec 5, 2019

test-me-please

Copy link
Contributor

@soumynathan soumynathan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

Copy link
Contributor

@soumynathan soumynathan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like it requires a release note.

@brb
Copy link
Member

brb commented Dec 5, 2019

test-me-please

@brb
Copy link
Member

brb commented Dec 9, 2019

Discussed offline: we will wait for a new merge to bpf-next to check whether the systemd-networkd problem has been fixed.

@aanm aanm added the wip label Dec 17, 2019
@brb
Copy link
Member

brb commented Dec 20, 2019

test-me-please

2 similar comments
@brb
Copy link
Member

brb commented Dec 20, 2019

test-me-please

@brb
Copy link
Member

brb commented Dec 21, 2019

test-me-please

@brb
Copy link
Member

brb commented Dec 23, 2019

vboxsf fails again:

[2019-12-21T07:19:56.449Z] Vagrant was unable to mount VirtualBox shared folders. This is usually
[2019-12-21T07:19:56.449Z] because the filesystem "vboxsf" is not available. This filesystem is
[2019-12-21T07:19:56.449Z] made available via the VirtualBox Guest Additions and kernel module.
[2019-12-21T07:19:56.449Z] Please verify that these guest additions are properly installed in the
[2019-12-21T07:19:56.449Z] guest. This is not a bug in Vagrant and is usually caused by a faulty
[2019-12-21T07:19:56.449Z] Vagrant box. For context, the command attempted was:
[2019-12-21T07:19:56.449Z] 
[2019-12-21T07:19:56.449Z] mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
[2019-12-21T07:19:56.449Z] 
[2019-12-21T07:19:56.449Z] The error output from the command was:

@brb
Copy link
Member

brb commented Jan 13, 2020

test-me-please

@brb
Copy link
Member

brb commented Jan 14, 2020

CI failing due to:

2020-01-13T17:21:05.879217332Z level=error msg="Command execution failed" cmd="[tc filter replace dev lxc2802e4c21dd8 ingress prio 1 handle 1 bpf da obj 619_next/bpf_lxc.o sec from-container]" error="exit status 1" subsys=datapath-loader
2020-01-13T17:21:05.879305756Z level=warning subsys=datapath-loader
2020-01-13T17:21:05.879360237Z level=warning msg="Prog section 'from-container' rejected: Operation not permitted (1)!" subsys=datapath-loader
2020-01-13T17:21:05.879408267Z level=warning msg=" - Type:         3" subsys=datapath-loader
2020-01-13T17:21:05.879465306Z level=warning msg=" - Attach Type:  0" subsys=datapath-loader
2020-01-13T17:21:05.879513122Z level=warning msg=" - Instructions: 91 (0 over limit)" subsys=datapath-loader
2020-01-13T17:21:05.879559133Z level=warning msg=" - License:      GPL" subsys=datapath-loader
2020-01-13T17:21:05.879604525Z level=warning subsys=datapath-loader
2020-01-13T17:21:05.879739917Z level=warning msg="Verifier analysis:" subsys=datapath-loader
2020-01-13T17:21:05.879788516Z level=warning subsys=datapath-loader
2020-01-13T17:21:05.879849643Z level=warning msg="Error fetching program/map!" subsys=datapath-loader
2020-01-13T17:21:05.879919926Z level=warning msg="Unable to load program" subsys=datapath-loader
2020-01-13T17:21:05.881274417Z level=warning msg="JoinEP: Failed to load program" containerID=0a303bdceb datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=619 error="Failed to load tc filter: exit status 1" file-path=619_next/bpf_lxc.o identity=39204 ipv4=10.10.1.48 ipv6="f00d::a0a:100:0:4231" k8sPodName=kube-system/coredns-687db6485c-4cttz subsys=datapath-loader veth=lxc2802e4c21dd8

@borkmann borkmann added the release-note/misc This PR makes changes that have no direct user impact. label Feb 28, 2020
@borkmann borkmann added area/CI Continuous Integration testing issue or flake and removed dont-merge/needs-rebase This PR needs to be rebased because it has merge conflicts. ci-check-only labels Feb 28, 2020
@borkmann
Copy link
Member Author

test-me-please

@borkmann
Copy link
Member Author

Checked with @nebril that the default entry can be ignored.

@borkmann borkmann merged commit ad223e8 into master Feb 28, 2020
@borkmann borkmann deleted the pr/update-netnext branch February 28, 2020 22:59
@maintainer-s-little-helper maintainer-s-little-helper bot added this to Needs backport from master in 1.7.1 Mar 2, 2020
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Needs backport from master to Backport pending to v1.7 in 1.7.1 Mar 3, 2020
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Needs backport from master to Backport pending to v1.7 in 1.7.1 Mar 3, 2020
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Backport pending to v1.7 to Needs backport from master in 1.7.1 Mar 3, 2020
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Backport pending to v1.7 to Needs backport from master in 1.7.1 Mar 3, 2020
@maintainer-s-little-helper maintainer-s-little-helper bot removed this from Needs backport from master in 1.7.1 Mar 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CI Continuous Integration testing issue or flake release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants