[FT] "TestMonitorDaemon._run_monitor" failing radomly, initial message not written
Bug #2035382 reported by
Rodolfo Alonso
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
In Progress
|
High
|
Miro Tomaska |
Bug Description
The method ``TestMonitorDa
Snippet: https:/
tags: | added: functional-tests |
Changed in neutron: | |
importance: | Undecided → High |
Changed in neutron: | |
assignee: | nobody → Miro Tomaska (mtomaska) |
tags: | added: stable |
To post a comment you must log in.
It appears this is the same issue we fixed few months ago [1][2]. There we have raised the log file read timeout by 3 seconds, totaling to 18 seconds. The Traceback[3] from this failure states that timeout was set to 15 seconds which makes me believe this is an older branch. If I am reading the job output correctly this run on Xena[4] which would explain the failure.
@Rodolfo Alonso, should I just backport[2] to earlier branches? Thanks!
[1]https:/ /bugs.launchpad .net/neutron/ +bug/2003022 /review. opendev. org/c/openstack /neutron/ +/870679 /paste. opendev. org/show/ bJCAjIqiUOcWB0x BhPnX/ /opendev. org/openstack/ neutron/ src/commit/ 067364fce50ca41 05b3a98f9838d7f ecc8e6baec/ neutron/ tests/functiona l/agent/ l3/test_ keepalived_ state_change. py#L99
[2]https:/
[3]https:/
[4]https:/