df4183bcb1
When controller-0 is deployed and the dc-vault is configured, if
dc-vault was already mounted (by systemd/fstab automount) while only
controller-0 is being deployed, Puppet attempts to mount dc-vault
again due to the automount flag. This causes Puppet to return an error
indicating that the filesystem is already mounted.
To resolve this, the automount option for dc-vault was disabled in the
Puppet configuration.
Test plan:
STD and DX (DC)
- PASS: run bootstrap and perform unlock on controler-0
- PASS: after unlock controller-0, before installing the hosts,
perform 3 reboots
- PASS: complete the installation and run a DOR test
Closes-bug: 2121539
Change-Id: I3def039f8c4eb2175ecfb0ddfc4412e7da19ffc1
Signed-off-by: Gabriel Przybysz Gonçalves Júnior <gabriel.przybyszgoncalvesjunior@windriver.com>
stx-puppet
The starlingx/stx-puppet repository handles the Puppet service1.
The Puppet service runs during bootstrap, and at every reboot, to provide a consistent configuration across the StarlingX system nodes.
This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest2.