* add new options for na_ontap_aggregate
* add gpl line
* remove dup option
* Put files in wrong directory
* change unit test to match the request from PR 48941
* Changed for review comments
* pep8
* Fixes#38174: Add remove-brick operation for gluster_volume
Existing gluster_volume module does not support removal of bricks
from a gluster volume. Also, operation remove-brick needs to be
followed by a commit operation.
Signed-off-by: Devyani Kota <dkota@redhat.com>
* Updates #38174: Add documentation for remove-brick operation
Signed-off-by: Devyani Kota <dkota@redhat.com>
* Updates #38174: Add support to reduce cluster configuration.
An exceptional scenario exists where the user might want to
reduce the gluster cluster configuration for replicated
volumes from replica 3 to replica 2 that need to be handled
in a different manner than the generic gluster commands,
where the user is expected to mention the replica count
of the new configuration in order to remove the bricks.
Signed-off-by: Devyani Kota <dkota@redhat.com>
* Updates #38174: Add checks for self-heal status prior remove operation.
While reducing the cluster configuration from replica 3
to 2, it needs to be checked for status of self-heal
prior remove-brick operation is executed.
Signed-off-by: Devyani Kota <dkota@redhat.com>
When a non-existent Gluster volume is to be deleted, i.e.:
gluster_volume:
state: absent
name: vol1-does-not-exist
the "gluster_volume" module would always fail with "volume not found
vol1-does-not-exist". The reason is that the code checked whether the
state is "delete", a value which isn't accepted for the "state"
parameter. Instead the expected value for volume deletion is, as above,
"absent".
* Resolve invalid-unary-operand-type.
* Resolve raising-format-tuple.
* Resolve stop-iteration-return.
* Use disable comment instead of fixing logic.
The affected line in _find_address_range will only fail on Python 3.7
and later if the function is called with an empty address list. As an
internal method it is never called in this way, making it a non-issue
for use via public methods.
Using a comment to disable the rule in favor of an ignore.txt entry
since there are no plans to change the logic in the code itself. This
will also prevent any potential future issues being added in other
parts of the code when updating it based on upstream changes.
* Fixed netapp_e_lun_mapping options for backwards compatibility.
Readd lun and target_type as deprecated options.
Note: lun and target_type were removed in patch #44666 since they were
no longer needed for the logic in the module. However, this cause will
cause existing playbooks utilizing these options to break.
* Add lun specification and target_type verification for netapp_e_lun_mapping
Simon Dodsley
Chris Archibald
Dag Wieers
Toshio Kuratomi
Rene Bakkum
Piotr Olczak
Corey Wanless
Abhijeet Kasurde
Devyani Kota
John R Barker
Tzur Eliyahu
hansmi
Matt Clay
Sandra McCann
ndswartz
Jesse Morgan