action #13914
open
[qe-core][functional][ipmi] wait_serial does not get expected output because ipmi console connection is closed
Added by xlai over 7 years ago.
Updated about 2 months ago.
hm, what do you think could be the potential error sources? Is it the IPMI itself or network connection or related to test or backend changes or maybe the product itself?
I do not have any proof yet. But I strongly suspect the ipmi performance under high test pressure.
- Category set to Bugs in existing tests
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: gi-guest_sles11sp4-on-host_sles12sp3-xen
http://openqa.suse.de/tests/781640
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: gi-guest_sles11sp4-on-host_sles12sp3-xen
http://openqa.suse.de/tests/781640
- Related to action #18144: [tools] restart ipmi management controller before every ipmi job added
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: gnome@64bit-ipmi
https://openqa.suse.de/tests/1002264
This issue is absolutely ipmi itself unstability issue, has nothing to do with test itself. If relevant, then we can only say that high work pressure on ipmi may lead to this much more.
- Description updated (diff)
- Category changed from Bugs in existing tests to Infrastructure
- Priority changed from Normal to High
updated description format. IMHO it's an "infrastructure" issue. I don't see anything done wrong in the test code itself. Of course, if we can not find a more stable solution in any IMPI worker that means the ticket is about workarounds in the test code or the backend itself.
- Related to action #34699: [qe-core][functional][ipmi] access to serial log during installation added
- Related to coordination #44843: [qe-core][functional][epic] Cleanup the use of serial-/virtio-/ssh-consoles in our tests (was: use $self->select_serial_terminal instead of checking IPMI in every module) added
- Subject changed from [ipmi] wait_serial does not get expected output because ipmi console connection is closed to [functional][u][ipmi] wait_serial does not get expected output because ipmi console connection is closed
- Status changed from New to Blocked
- Assignee set to okurz
- Target version set to future
- Assignee changed from okurz to mgriessmeier
Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.
- Related to deleted (action #34699: [qe-core][functional][ipmi] access to serial log during installation)
- Blocked by action #34699: [qe-core][functional][ipmi] access to serial log during installation added
- Assignee changed from mgriessmeier to SLindoMansilla
- Subject changed from [functional][u][ipmi] wait_serial does not get expected output because ipmi console connection is closed to [qe-core][functional][ipmi] wait_serial does not get expected output because ipmi console connection is closed
- Status changed from Blocked to New
- Assignee deleted (
SLindoMansilla)
No time to work on this :(
- Priority changed from High to Normal
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Also available in: Atom
PDF