FIX: Change ownership of newly-created VGs 10/3710/1
authordave kormann <davek@research.att.com>
Fri, 18 Sep 2020 18:39:49 +0000 (14:39 -0400)
committerdave kormann <davek@research.att.com>
Fri, 18 Sep 2020 18:42:10 +0000 (14:42 -0400)
commit76de2b3e9925960e461fd7d26e6cc1d00063078e
tree1e1fc8616df74658aa2e403b8f6769d0233aa52e
parentd2a34bd516008f9dac3d3dab55effa89cce3daf4
FIX: Change ownership of newly-created VGs

When creating a new volume group, allow a user/group to be specified
to own the root directory.  If no user/group is provided, use the
owner of the mountpoint or (if it doesn't exist) the current user/group.

This should fix the problem with mariadb permission problems when
installing to a vg, as opposed to the existing directory in the
image.

signed-off-by: dave korman   <davek@research.att.com>
Change-Id: Idf4418dca288a374c53fa6c180c3bdf62db10abb
roles/partfs_rootdisk/scripts/vol_mgmt.sh