-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to 22.07 TridentBackendConfig nas and nas-eco failed state #759
Comments
|
@ntap-arorar
There are a lot of logs: I try to give you the interesting parts (these parts are repeated several times):
|
@zwiy There was a change in 22.07 that prohibits the use of two authentication methods for a backend, you can only use one. Can you please remove one of the storage controller authentication methods from the secret, please keep the one that is valid. After you modify the secret ( |
@ntap-arorar
It's exactly the same structure like the
If I delete the failing TridentBackendConfiguration and recreate it with the same YAML afterwards. Everything is working. Thanks for your help! |
Maybe this message refers to this issue? #755 |
@zwiy Thanks! |
Hello @zwiy I investigated this issue and was able to reproduce it. This issue only affects pre-22.07 backends that have been created using the We will work on fixing this issue, in the meantime, there is a workaround to get out of this situation. You will need to do the following:
Once the Trident deployment pod are online, the state of your backend should also be |
Hello @ntap-arorar Thank you for your help! Your solution works and all backends are now online. Have a nice day! |
I hit this same issue, but fixed it with a heavier hammer:
followed by a restart. |
Could you please add this issue to release notes? |
This issue is fixed with commit 9b78a23 and will be included in the Trident 22.10 release. |
We had the same Issue in our ONTAP SAN drivers. The Workaround fixed the problem. |
Describe the bug
After the upgrade from v21.10.1 (and 22.04.0) to v22.07.0 only the
ontap-nas
andontap-nas-economy
drivers are stuck in afailed
state:But the IP address wasn't changed.
ONTAP SAN drivers (ontap-san, ontap-san-economy) don't have these problem.
Trident-main Logs:
Current Configuration:
I'tried to set the
dataLIF
IP address but it didn't change anything in the status.The only way to get it work is deleting the TridentBackendConfig and reapplying the configuration (made for backend-tbc-ontap-nas) - but this doesn't work if there are any volumes associated with the backend:
Environment
The problem occures on several clusters after the upgrade: RKE/RKE2, v1.22.10 and v1.21.7+rke2r2
Is there another workaround to get this work?
The text was updated successfully, but these errors were encountered: