[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
We enabled back our failing CI tests after switching to kernel
4.4.0-92.115 and everything went back to normal. Current 4.4.0-93.116
works just fine too. Thanks a lot for a quick help! I think you can
close this bug as resolved :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
Hi @libosvar,
Could you please verify the follow-up fix with the xenial kernel in
-proposed?
Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
Xenial kernel 4.4.0-92.115 had a quick fix for the issue, which was to
revert the patch that introduced the regression ("netfilter: synproxy:
fix conntrackd interaction"). The kernel build that's in -proposed
(currently 4.4.0-93.116) reapplies this patch and applies on top the
proper fix found upstream ("netfilter: nf_ct_ext: fix possible panic
after nf_ct_extend_unregister").
Could someone please verify if the kernel in -proposed really fixes the
issue?
Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
This bug was fixed in the package linux - 4.4.0-92.115
---
linux (4.4.0-92.115) xenial; urgency=low
* linux: 4.4.0-92.115 -proposed tracker (LP: #1709812)
* Creating conntrack entry failure with kernel 4.4.0-89 (LP: #1709032)
- Revert "netfilter: synproxy: fix conntrackd interaction"
-- Kleber Sacilotto de Souza Thu, 10 Aug
2017 10:29:51 +0200
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
This bug was fixed in the package linux - 4.4.0-92.115
---
linux (4.4.0-92.115) xenial; urgency=low
* linux: 4.4.0-92.115 -proposed tracker (LP: #1709812)
* Creating conntrack entry failure with kernel 4.4.0-89 (LP: #1709032)
- Revert "netfilter: synproxy: fix conntrackd interaction"
-- Kleber Sacilotto de Souza Thu, 10 Aug
2017 10:29:51 +0200
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
I cherry-picked 9c3f3794 to Ubuntu-4.4.0-89.112 tag and built the kernel
and I'm able to create a conntrack entry without any issues or traces,
so it *does* fix the issue. I assume what I had is the same as what
Joseph provided :) Thanks for helping us out guys!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
I built a xenial test kernel with a pick of commit 9c3f379492 and
WITHOUT commit 2ad4caea651 reverted.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1709032/patched
Can you give that kernel a test?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
I'll build a Xenial test kernel with the commit Jay mentioned in comment
#16 and post it shortly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
Just to confirm, the revert did fix the bug as posted in comment #15?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
Are you sure 9c3f3794 fixes it? I'm not a kernel expert but since the backtrace
differs and, according to the commit message, I'd say it's a different issue.
We could try backporting it manually and check but maybe reverting 2ad4caea651
suffices until
ubuntu guys fix the bug in a future tag?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
Is it possible to backport the patch to 4.4.0 kernel in Xenial LTS
version?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
The panic appears to be fixed upstream via:
commit 9c3f3794926a997b1cab6c42480ff300efa2d162
Author: Liping Zhang
Date: Sat Mar 25 16:35:29 2017 +0800
netfilter: nf_ct_ext: fix possible panic after
nf_ct_extend_unregister
If one cpu is doing nf_ct_extend_unregister while another cpu is doing
__nf_ct_ext_add_length, then we may hit BUG_ON(t == NULL). Moreover,
there's no synchronize_rcu invocation after set nf_ct_ext_types[id] to
NULL, so it's possible that we may access invalid pointer.
[...]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
Thanks Joseph, I tested both, creating a conntrack entry using conntrack
CLI and running the Neutron functional tests, both are fine with the
revert.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
I built a test kernel with a revert of commit 2ad4caea651. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1709032/
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
** Tags added: kernel-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
Re-confirmed - I see the same regression in behaviour between -81 -> -89
using the test case in #11.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
