Fencing generation client command uses incorrect IPMI level parameter
Bug #1664568 reported by
Chris Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Chris Jones | ||
Ocata |
Fix Committed
|
Undecided
|
Chris Jones |
Bug Description
This was my mistake when landing the code before Ocata-3. A key ("ipmi_level") was not changed completely across all its locations.
Changed in tripleo: | |
milestone: | none → pike-1 |
importance: | Undecided → Medium |
Changed in tripleo: | |
milestone: | pike-1 → pike-2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/433649
Review: https:/