From 9d859ef3a54063ed9d24f57cf243b03f8ce502bc Mon Sep 17 00:00:00 2001 From: Jessica Castelino Date: Fri, 24 Apr 2020 17:13:02 -0400 Subject: [PATCH] Rename the existing /opt/patch-vault filesystem to /opt/dc-vault The filesystem /opt/patch-vault is renamed to /opt/dc-vault so that it can be re-used to store FPGA images and software loads. Thus, necessary changes have been made in the manual tests. Change-Id: I095a9c90afef8af5a64d7025745a15b136a56a2f Story: 2006740 Task: 39550 Depends-On: https://review.opendev.org/#/c/723007/ Signed-off-by: Jessica Castelino --- doc/source/manual_tests/distributed_cloud/index.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/manual_tests/distributed_cloud/index.rst b/doc/source/manual_tests/distributed_cloud/index.rst index 5b6ec2f..195d664 100644 --- a/doc/source/manual_tests/distributed_cloud/index.rst +++ b/doc/source/manual_tests/distributed_cloud/index.rst @@ -771,9 +771,9 @@ All killed processes will be recovered. Here are observations from testing (for - dcorch-neutron-api-proxy done (kill once and swact. Tried later and saw kill once and process cannot recover - eventually we will swact CGTS-9742) - dcorch-cinder-api-proxy done (similar behaviour to dcmanager-manager) -- drbd-patch-vault NOT SURE HOW TO KILL (tried systemctl and service +- drbd-dc-vault NOT SURE HOW TO KILL (tried systemctl and service but there is no process) -- patch-vault-fs NOT SURE HOW TO KILL (tried systemctl and service +- dc-vault-fs NOT SURE HOW TO KILL (tried systemctl and service but there is no process) - dcorch-patch-api-proxy (done, kill once and saw swact, later multiple kills and no swact, later two kills and a swact - inconsistent behaviour)