Traceback when getting capacity in k8s_monitor
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Confirmed
|
Undecided
|
Unassigned | ||
Ubuntu Cloud Archive |
Fix Committed
|
High
|
Unassigned | ||
Pike |
Fix Committed
|
High
|
Unassigned | ||
python-k8sclient (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Artful |
Fix Released
|
High
|
Unassigned |
Bug Description
I'm seeing the following traceback in the magnum-conductor output:
2017-01-25 22:03:33.838 WARNING magnum.
2017-01-25 22:03:33.838 573 ERROR magnum.
2017-01-25 22:03:33.838 573 ERROR magnum.
2017-01-25 22:03:33.838 573 ERROR magnum.
2017-01-25 22:03:33.838 573 ERROR magnum.
2017-01-25 22:03:33.838 573 ERROR magnum.
2017-01-25 22:03:33.838 573 ERROR magnum.
2017-01-25 22:03:33.838 573 ERROR magnum.
2017-01-25 22:03:33.838 573 ERROR magnum.
2017-01-25 22:03:33.838 573 ERROR magnum.
Maybe it's related to the fix for https:/
Changed in cloud-archive: | |
status: | New → Triaged |
Changed in magnum (Ubuntu): | |
status: | New → Triaged |
Changed in cloud-archive: | |
importance: | Undecided → High |
Changed in magnum (Ubuntu): | |
importance: | Undecided → High |
The fix requires a fix in the k8sclient too. Check the version of your k8sclient. If you have version 0.3.0 it's expected that you'll have the bug.