fix: r/vsphere_nas_datastore
not mounted to additional hosts as day-two
#1860
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix a bug in nasDatastoreMountProcessor.diff() method which was the root cause of #1589
Description
Fix
r/vsphere_nas_datastore
not mounted to additional hosts as day-two.The nasDatastoreMountProcessor.diff() method was not correctly calculating the difference between the old and the new datastore hosts and as a result of this the nasDatastoreMountProcessor.processMountOperations()was not mounting the datastore the new hosts.
Testing done:
Added additional ESXi hosts to the "host_system_ids" of NFS datastore and verified that terraform apply correctly mounted the datastore to the new hosts.
Closes #1589
Acceptance tests
Output from acceptance testing: