Kube Orchestration patch apply timeout too short
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Al Bailey |
Bug Description
Brief Description
-----------------
It was observed in a lab environment that applying the second patch during the VIM kubernetes upgrade orchestration, that the patch apply timed out after 20 seconds, while the apply succeeded after 23 seconds.
Distributed Cloud orchestration uses a much longer timeout value, but the VIM defaults to 20 seconds.
Severity
--------
Minor
Steps to Reproduce
------------------
Attempt to do a kubernetes upgrade orchestration in the vim.
This was only seen once in one lab.
Expected Behavior
------------------
Applying the second kubernetes patch (called KUBE.2 in the StarlingX kubernetes upgrade steps) should pass, and the rest of orchestration should succeed.
Actual Behavior
----------------
The VIM orchestration failed due to the timeout.
It needed to be re-initiated to run to completion.
Reproducibility
---------------
Seen Once
System Configuration
-------
Duplex+1
Branch/Pull Time/Commit
-------
March 4 20201
Last Pass
---------
This is the only time this failure has been seen.
Its a timing issue.
Timestamp/Logs
--------------
VIM log
2021-05-
Traceback (most recent call last):
File "/usr/lib64/
future.result = (yield)
OpenStackException: [OpenStack Exception: method=POST, url=https://[fd01:1:
patching log shows the apply sync completed 4 seconds later
021-05-06T14:45:40: sw-patch-
Test Activity
-------------
Feature testing
Workaround
----------
Delete the failed strategy, create a new one, and apply it. The kubernetes upgrade orchestration will
resume properly.
Changed in starlingx: | |
assignee: | nobody → Al Bailey (albailey1974) |
Fix proposed to branch: master /review. opendev. org/c/starlingx /nfv/+/ 790135
Review: https:/