Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

namespace test failing with q35 on centos #1604

Closed
jodh-intel opened this issue Apr 29, 2019 · 5 comments
Closed

namespace test failing with q35 on centos #1604

jodh-intel opened this issue Apr 29, 2019 · 5 comments
Assignees

Comments

@jodh-intel
Copy link
Contributor

CentOS q35 CI failing:

=== RUN   TestHostNetworkingRequested
--- FAIL: TestHostNetworkingRequested (0.01s)
    assertions.go:239: 
                          
	Error Trace:	network_test.go:99
        
	Error:      	Should be true

See #1587.

@jodh-intel
Copy link
Contributor Author

Also seen here: #1599 (comment).

@lifupan
Copy link
Member

lifupan commented Apr 29, 2019

Hi @jodh-intel,

I found the root cause is that the kernel in CentOS q35 is 3.10 which doesn't support the "nsfs",
and the "nsfs" isn't supported until 3.19 version.
I'm curious when did we add the centos q35 test? Why this failed didn't appear until recently?

@jodh-intel
Copy link
Contributor Author

Thanks @lifupan.

The Jenkins q35 jobs were added on kata-containers/ci#144, but I'm not sure if the date on that PR is the same as the time we actually started using them. Maybe @GabyCT can provide further info?

Rather than ignoring on centos, I think this is another use-case for #1587. I'll add a new call to allow skipping a test if the kernel version is too old...

@GabyCT
Copy link
Contributor

GabyCT commented Apr 30, 2019

@jodh-intel and @lifupan , yes the day that that PR landed the CI started running for PR, the master jenkins jobs for Q35 started working before that PR as I tested that the jobs were stable

@jodh-intel
Copy link
Contributor Author

This is a duplicate of #1517.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants