NetApp SVM scoped account is not working
Bug #1882590 reported by
Felipe Rodrigues
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Felipe Rodrigues |
Bug Description
Steps to reproduce
==================
Setup a backend as svm scoped following:
Then, restart the manila service. That backend will not be up.
Expected result
===============
backend should be up using a svm scoped.
Actual result
=============
backend fails to start. The error is showed in the log.
Environment
===========
1. ussuri release
2. Netapp backend
3. dhss false
Logs & Configs
==============
Changed in manila: | |
assignee: | nobody → Felipe Rodrigues (felipefutty) |
summary: |
- svm scoped account is not working NetappDriver + NetApp SVM scoped account is not working |
Changed in manila: | |
importance: | Undecided → Medium |
milestone: | none → victoria-1 |
status: | New → Confirmed |
tags: | added: netapp |
tags: | added: backport-potential |
To post a comment you must log in.
This issue blocks the driver's pool update function when using NetApp SVM scopped accounts. It's affecting all branches from Queens to Ussuri and the fix needs to be backported. /review. opendev. org/#/c/ 665142/
The problem started after merging this fix: https:/