Skip to content

Fix use of use_tiered_aggregate in netapp-ontap_flexcache#582

Open
brinnjoyce wants to merge 2 commits intoNetApp:integration/mainfrom
brinnjoyce:fix_flexcache
Open

Fix use of use_tiered_aggregate in netapp-ontap_flexcache#582
brinnjoyce wants to merge 2 commits intoNetApp:integration/mainfrom
brinnjoyce:fix_flexcache

Conversation

@brinnjoyce
Copy link
Copy Markdown

use_tiered_aggregate can only be set on flexcache creation. It cannot be changed or read from the API.

Stop trying to read it from the API and update state which causes errors if it's set to true. The default of false does not hit these errors.

Closes #581

@brinnjoyce
Copy link
Copy Markdown
Author

On further testing this won't fix the issue seen in #340 but it does fix #581

The API just doesn't always return all volumes, making the same request multiple times I get a different number of volumes returned. Perhaps that's a bug that needs to be fixed on the OnTap side?
Testing manually with curl it seems the origins field is the most expensive. Removing that from the fields gets me consistent results.
Seems related https://community.netapp.com/t5/ONTAP-Rest-API-Discussions/Discrepancy-with-Public-REST-and-private-cli-REST-output-records-for-volume/td-p/463085

(cherry picked from commit ba7b41de7e4a2bb19f42607a9cc25ce15961a3b5)
Copy link
Copy Markdown
Contributor

@suhasbshekar suhasbshekar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We try to avoid defaults going forward as API may change defaults in future, this creates a dependency, lets try to have a solution without default

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: netapp-ontap_flexcache errors if use_tiered_aggregate set to true

2 participants