Do not use separate partition for cloudinit configuration
In our usecases the separate partition is not needed. It is enough just
to put cloudinit configuration into the root filesystem.
This also allows to avoid a race condition which sometimes happens: some
process deletes the folder in tmp where the configuration partition is
mounted resulting in cloudinit failure to read its configuration.
Change-Id: Ib3efb4f517a5cf86dbf91ee53ac00108d4624dcd
Closes-Bug: #1652002
(cherry picked from commit b9842ce714f9369f4881fcefd1e96f0e458d3644)
Reviewed: https:/ /review. openstack. org/436416 /git.openstack. org/cgit/ openstack/ fuel-agent/ commit/ ?id=739326df02e 0fae2fd17fe5989 0fc381d5adf1a3
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit 739326df02e0fae 2fd17fe59890fc3 81d5adf1a3
Author: Georgy Kibardin <email address hidden>
Date: Mon Feb 20 12:29:05 2017 +0300
Do not use separate partition for cloudinit configuration
In our usecases the separate partition is not needed. It is enough just
to put cloudinit configuration into the root filesystem.
This also allows to avoid a race condition which sometimes happens: some
process deletes the folder in tmp where the configuration partition is
mounted resulting in cloudinit failure to read its configuration.
Change-Id: Ib3efb4f517a5cf 86dbf91ee53ac00 108d4624dcd f4881fcefd1e96f 0e458d3644)
Closes-Bug: #1652002
(cherry picked from commit b9842ce714f9369