Failed to initialize driver due to unrecognized option '--ignoreskippedcluster
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Bob Ball |
Bug Description
When start the service of cinder-volume, it failed to initialize driver due to unrecognized option '--ignoreskippe
It looks like the following commit added this option and it's attending to only add this option when lvm is later than 2.02.103. But obviously it's not working as expected: it's using the option of '--ignoreskippe
https:/
stack@devstack:
LVM version: 2.02.98(2) (2012-10-15)
Library version: 1.02.77 (2012-10-15)
Driver version: 4.27.0
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
2017-02-01 23:19:15.287 13448 ERROR cinder.
Something is odd here. My latest and greatest Ubuntu 14.04 install has LVM version 2.2.98, which should fail to pass the check and therefore not pass in --ignoreskipped cluster. And if an install does have an LVM version that passes that check, it should include that option. Will have to investigate more.