All such issues were only spotted in one patch
https://review.openstack.org/#/c/610280/ and it looks for me that it could be
related to the change from this patch.
I don't think we have any issue with this test in fullstack jobs for now.
** Changed in: neutron
Status: New => Incomplete
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1798689
Title:
Fullstack test test_create_one_default_qos_policy_per_project failed
Status in neutron:
Invalid
Bug description:
* Job: neutron-fullstack-python36
* Failed tests: test_create_one_default_qos_policy_per_project,
test_create_two_default_qos_policies_per_project, test_update_default_status,
test_update_default_status_conflict
* Example failure:
http://logs.openstack.org/80/610280/8/check/neutron-fullstack-python36/9811ceb/logs/testr_results.html.gz
* Sample trace: http://paste.openstack.org/show/732449/
* Logstash:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22ValueError%3A%20Field%20%60project_id'%20cannot%20be%20None%5C%22
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1798689/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
