Describe the bug
When sending a request to trident to create a new volume, the code silently drops the tiering policy from the request (as seen here) even though a tiering policy is defined to be a valid volume config (here)
Environment
Provide accurate information about the environment to help us reproduce the issue.
- Trident version: [e.g. 19.10]
- Trident installation flags used: [e.g. -d -n trident --use-custom-yaml]
- Container runtime: [e.g. Docker 19.03.1-CE]
- Kubernetes version: [e.g. 1.15.1]
- Kubernetes orchestrator: [e.g. OpenShift v3.11, Rancher v2.3.3]
- Kubernetes enabled feature gates: [e.g. CSINodeInfo]
- OS: [e.g. RHEL 7.6, Ubuntu 16.04]
- NetApp backend types: [e.g. CVS for AWS, ONTAP AFF 9.5, HCI 1.7]
- Other:
To Reproduce
Steps to reproduce the behavior:
Send an HTTP request to Trident to create a new volume with a specific tieringPolicy different from the default defined in the backend config.
Expected behavior
The tiering policy defined in the request should be respected and the new volume is created with that tiering policy
Additional context
Add any other context about the problem here.
Describe the bug
When sending a request to trident to create a new volume, the code silently drops the tiering policy from the request (as seen here) even though a tiering policy is defined to be a valid volume config (here)
Environment
Provide accurate information about the environment to help us reproduce the issue.
To Reproduce
Steps to reproduce the behavior:
Send an HTTP request to Trident to create a new volume with a specific tieringPolicy different from the default defined in the backend config.
Expected behavior
The tiering policy defined in the request should be respected and the new volume is created with that tiering policy
Additional context
Add any other context about the problem here.