storwize svc driver needs to avoid SVC CLI shortcut
Bug #1163964 reported by
Alan Jiang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Avishay Traeger | ||
Grizzly |
Fix Released
|
High
|
Avishay Traeger |
Bug Description
For SVC storwize driver, the SVC cli is invoked directly by using cli shortcut instead of a svcinfo or svctask wrapper.
The shortcut is h/w model dependent. The safer way to invoke svc CLI is to wrap SVC cli with svcinfo and svctask command and handle the SVC error code if the command is not supported.
svcinfo -? and svctask -? can dump all the supported cli on a given SVC.
For example, on V3700, lslicense is not supported, and some older SVC f/w version doesn't support lssystem
Those SVC CLI error will cause storwize_svc to throw exception and break cinder when managing some SVC model.
tags: | removed: drivers grizzly-backport-potential |
Changed in cinder: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
tags: | removed: in-stable-grizzly |
Changed in cinder: | |
milestone: | havana-1 → 2013.2 |
To post a comment you must log in.
This bug is related to bug 1163754, which is one instance of a command that is not supported in all firmware versions. They can be fixed together.