diff options
author | Zuul <zuul@review.opendev.org> | 2022-07-20 08:23:55 +0000 |
---|---|---|
committer | Gerrit Code Review <review@openstack.org> | 2022-07-20 08:23:55 +0000 |
commit | 21b21a5f15bce4871f6af0dc06ebf50d0e9b0967 (patch) | |
tree | b39fc6a45ecc4aeac290a91a71e2ff99534abe7a /releasenotes | |
parent | 6a1334a0683121dc94390c8a57aec1c3af208398 (diff) | |
parent | beb7484858d56ef34699895412881945c5507c81 (diff) | |
download | ironic-python-agent-21b21a5f15bce4871f6af0dc06ebf50d0e9b0967.tar.gz |
Merge "Guard shared device/cluster filesystems"
Diffstat (limited to 'releasenotes')
-rw-r--r-- | releasenotes/notes/prevent-deletion-of-shared-disk-filesystems-4c17c7666d2fe3bc.yaml | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/releasenotes/notes/prevent-deletion-of-shared-disk-filesystems-4c17c7666d2fe3bc.yaml b/releasenotes/notes/prevent-deletion-of-shared-disk-filesystems-4c17c7666d2fe3bc.yaml new file mode 100644 index 00000000..c29b3121 --- /dev/null +++ b/releasenotes/notes/prevent-deletion-of-shared-disk-filesystems-4c17c7666d2fe3bc.yaml @@ -0,0 +1,20 @@ +--- +fixes: + - | + Previously when the ``ironic-python-agent`` would undergo erasure of block + devices during cleaning, it would automatically attempt to erase the + contents of any "Shared Device" clustered filesystems which may be in use + by distinct multiple machines over a storage fabric. In particular + IBM GPFS, Red Hat Global File System 2, and VmWare Virtual Machine File + System (VMFS), are now identified and cleaning is halted. This is important + because should an active cluster be using the this disk, cleaning could + potentially cause the cluster to go down forcing restoration from backups. + Ideally, infrastructure operators should check their environment's storage + configuration and un-map any clustered filesystems from being visible to + Ironic nodes, unless explicitly needed and expected. Please see the + Ironic-Python-Agent troubleshooting documentation for more information. +issues: + - | + Logic to guard VMFS filesystems from being destroyed *may* not recognize + VMFS extents. Operators with examples of partitioning for extent usage + are encouraged to contact the Ironic community. |