Refactor config drive mounting
There are a few places where we mount the config drive which
is not done in a consistent manner which results in failures
for the cases where the config drive is VFAT, which makes the
device label report as CONFIG-2 and not config-2 (uppercase).
This refactors the mounting and unmounting codebase to the
same block and reuses it to ensure a consistent behaviour across
tests, also letting the tags checks pass when using VFAT for
config drives.
Change-Id: I529cff87c848bc87d63d2ec407ed18cdd631ecef
diff --git a/releasenotes/notes/create-mount-config-drive-to-lib-1a6e912b8afbcc7e.yaml b/releasenotes/notes/create-mount-config-drive-to-lib-1a6e912b8afbcc7e.yaml
new file mode 100644
index 0000000..f92cd78
--- /dev/null
+++ b/releasenotes/notes/create-mount-config-drive-to-lib-1a6e912b8afbcc7e.yaml
@@ -0,0 +1,4 @@
+---
+features:
+ - A function has been added to the common library to allow mounting and
+ unmounting of the config drive consistently.