Chuck Fouts

This issue is fixed with [commit 9b78a23](https://github.com/NetApp-openstack-dev/trident/commit/9b78a23f968b478f51c95283224f2e478a0f9b96) and will be included in the Trident 22.10 release.

@wonderland, to clarify your request are you asking that we review the Trident documentation with the idea to make it more GitOps friendly?

While implementing NodeExpand it was found that it is useful to know that the VolumePath in the NodeExpandVolumeRequest is actually the staging_target_path. In our implementation, the staging path is needed...

Hi @eedo369 and @bert-jan, This isn't an enhancement that Trident can support as ONTAP does not support taking or restoring snapshots of individual Qtrees. The ontap-nas-economy driver has the trade...

Hi @bernot-dev, It was determined that an additional change went in to 22.07 after the dependency update commit was merged that caused this issue. The team is taking steps to...

Hi @bernot-dev, It doesn't really make sense to open a PR to fix this. The team may decide to add this check in the CI/CD pipeline instead of adding it...

Hi @MrMarlin, There is an existing GitHub Issue asking for [Hashicorp Nomad support](https://github.com/NetApp/trident/issues/376). We are tracking the requests for Nomad support but you and others can help by asking your...

Hi @clementnuss. From the error message it appears that the qtree was created using the ontap-nas-economy driver and that you are trying to use to use the ontap-nas economy driver...

Hi @ffilippopoulos, A change was included in Trident v22.04.0 with [commit 952659](https://github.com/NetApp-openstack-dev/trident/commit/952659d77c6eb727ee3ef46af10d8a6af26cca31) to run fsck prior to the volume being attached. When a SAN volume is resized it is necessary...

Hi @rsjonte, If you are still seeing this issue then please open a NetApp Support case. We haven't been able to reproduce the issue you've reported in our testing.