engine: do not stall the host command queue on a failed send in Agent… - #14040
engine: do not stall the host command queue on a failed send in Agent…#14040nagaboinaramgopal wants to merge 1 commit into
Conversation
b280ae5 to
b42f357
Compare
b42f357 to
dab7711
Compare
|
@blueorangutan package |
|
@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.20 #14040 +/- ##
============================================
+ Coverage 16.34% 19.78% +3.43%
- Complexity 13574 19993 +6419
============================================
Files 5669 6371 +702
Lines 501368 575900 +74532
Branches 60903 70495 +9592
============================================
+ Hits 81964 113953 +31989
- Misses 410219 449513 +39294
- Partials 9185 12434 +3249
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Packaging result [SF]: ✖️ el8 ✖️ el9 ✖️ debian ✖️ suse15. SL-JID 19095 |
|
@nagaboinaramgopal , an compile error in your test code: can you have a look? |
…Attache.sendNext When sending the next queued request threw AgentUnavailableException, the request was cancelled but _currentSequence was still set to that dead sequence. No answer ever arrives for a cancelled command, so sendNext was never driven again and every later in-sequence command to the host queued behind it and timed out until the attache was rebuilt. Advance _currentSequence only on a successful send, and on failure move on to the next queued request.
dab7711 to
4d8e427
Compare
fixed and pushed, Thanks Daan |
Description
When sending the next queued request threw AgentUnavailableException, the request
was cancelled but _currentSequence was still set to that dead sequence. No answer
ever arrives for a cancelled command, so sendNext was never driven again and every
later in-sequence command to the host queued behind it and timed out, until the
attache was rebuilt.
Advance _currentSequence only on a successful send, and on failure move on to the
next queued request.
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
How Has This Been Tested?
Added a unit test where the first queued command fails to send and asserts the
next queued command is dispatched and becomes the current sequence, instead of
stalling on the failed one. Also built the standard packages and deployed on a KVM
advanced zone.