clh: Add support to unplug block devices#2833
Conversation
|
Thank you for raising your pull request. Please note that the main development of Kata Containers has moved to the 2.0-dev branch of https://github.com/kata-containers/kata-containers repository. The kata-containers/runtime repository is kept for 1.x release maintenance. Please check twice if your change should go to the 2.0-dev branch directly. If it is strongly required for adding the change to Kata Containers 1.x releases, please ping @kata-containers/runtime to assign a dedicated developer to be responsible for porting the change to 2.0-dev branch. Thanks! |
This patch extends the existing scripts to cover a new Jenkins job on testing k8s with crio for cloud-hypervisor. Fixes: kata-containers#2546 Depends-on: github.com/kata-containers/runtime#2833 Signed-off-by: Bo Chen <chen.bo@intel.com>
|
/test-clh |
Codecov Report
@@ Coverage Diff @@
## master #2833 +/- ##
=======================================
Coverage 51.40% 51.41%
=======================================
Files 118 118
Lines 17411 17434 +23
=======================================
+ Hits 8950 8963 +13
- Misses 7379 7388 +9
- Partials 1082 1083 +1 |
|
/test-ubuntu |
|
/test-clh |
|
/test-ubuntu |
|
/test-clh |
|
/test-ubuntu |
This patch extends the existing scripts to cover a new Jenkins job on testing k8s with crio for cloud-hypervisor. Fixes: kata-containers#2546 Depends-on: github.com/kata-containers/runtime#2833 Signed-off-by: Bo Chen <chen.bo@intel.com>
|
@jcvenegas @GabyCT The metrics CI is failing on |
|
@likebreath if you see the log, there are issues of unexpected processes |
|
that corrupted the tests and that is why the failure, that process is there before running the metrics |
@GabyCT Thank you for the inputs. Any thoughts on why this error is happening and how it can be fixed? |
|
@likebreath no, check the logs maybe you will get an info there of what is happening |
|
/test-clh-docker |
|
/test-clh-metrics |
|
I re-ran the metrics CI again, and it is now not failing on the original setup stage in the CI. For now it is failing on the memory foot-print metrics, as listed below: With pointer from @jcvenegas, the root cause of this failure is: A similar metrics CI failure is also observed from PR #2863 (@amshinde). From the log: @GabyCT Can you please share any insights about the above obversations? Also, do you have pointers to explain the metrics CI in general? I am interested to know how those reference data are generated, and what kind of data are we tracking as the part of the metrics (e.g. why are we monitoring minimum memory-footprint, etc). Thank you. |
To support unplug block device, we need to set the 'Id' explicitly while hotplugging devices with cloud-hypervisor HTTP API. Fixes: kata-containers#2832 Signed-off-by: Bo Chen <chen.bo@intel.com>
|
/test-clh |
|
/test-clh |
This patch enables kata+clh to unplug block devices, which is required to pass cri-o integration tests. Fixes: kata-containers#2832 Signed-off-by: Bo Chen <chen.bo@intel.com>
|
/test-clh-metrics |
|
/test-ubuntu |
|
@amshinde @jcvenegas This PR is ready to be landed. Please take a look and ACK. Thanks. |
This patch enables kata+clh to unplug block devices, which is required
to pass cri-o integration tests.
Fixes: #2832
Signed-off-by: Bo Chen chen.bo@intel.com