is_loaded not set when novaclient resource instantiated by manager
Bug #971183 reported by
Gabriel Hurley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-novaclient |
Fix Released
|
Low
|
Brian Waldon |
Bug Description
When instantiating an object using the manager class' get method, the loaded=True kwarg is not being passed in, thus the resource thinks it's not loaded, causing weird double-fetching issues when accessing attributes which may or may not exist.
The changeset that introduced this bug is here:
https:/
tags: | added: python-novaclient |
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
importance: | Medium → Low |
tags: | removed: essex-rc-potential |
Changed in nova: | |
assignee: | nobody → Brian Waldon (bcwaldon) |
status: | Confirmed → In Progress |
Changed in nova: | |
milestone: | none → folsom-1 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
affects: | nova → python-novaclient |
Changed in python-novaclient: | |
milestone: | folsom-1 → none |
To post a comment you must log in.
Should be as simple as setting loaded=True wherever a Manager instantiates a Resource.