Load import via sysinv-api proxy could fail in slow vbox
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Tee Ngo |
Bug Description
Brief Description
-----------------
Load import via sysinv api proxy could fail in vbox if the load files are removed by sysinv-conductor from staging directory before they are copied over to dc-vault by sysinv api proxy.
Severity
--------
Major
Steps to Reproduce
------------------
Import a 20.06 load on the system controller in vbox by running the command:
system --os-region-name SystemController load-import bootimage.iso bootimage.sig
Expected Behavior
------------------
Load import via sysinv api proxy completes successfully
Actual Behavior
----------------
Load import via sysinv api proxy failed as the copy of bootimage.iso file to dc-vault took longer in vbox and did not complete before sysinv-conductor removes the load files from staging director.
This issue was only observed in a distributed cloud system in one designer's vbox running 20.01 load. The issue was not observed in a distributed cloud system in another designer's vbox running 20.06 load or on hardware.
Reproducibility
---------------
100% reproducible on the designer with slow vbox
System Configuration
-------
IPv4
Branch/Pull Time/Commit
-------
Latest 20.01 load + load import patch
Last Pass
---------
Yes this test passed on hardware and also passed in vbox running 20.06 load.
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Developer Testing
Workaround
----------
Describe workaround if available
Changed in starlingx: | |
assignee: | nobody → Tee Ngo (teewrs) |
tags: | added: stx.distcloud |
Changed in starlingx: | |
importance: | Undecided → High |
tags: | added: stx.4.0 |
Fix proposed to branch: master /review. opendev. org/737430
Review: https:/