NoneType error when deployment starts on baremetal lab
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Fedor Zhadaev | ||
Mitaka |
Fix Released
|
Critical
|
Fedor Zhadaev | ||
Newton |
Fix Released
|
Critical
|
Fedor Zhadaev |
Bug Description
Detailed bug description:
When I start to deploy env on barametal lab it is impossible because of Error
'NoneType' object has no attribute 'update'
Steps to reproduce:
1) Create env
2) Start deploy
Expected results:
deployment is successful
Actual result:
'NoneType' object has no attribute 'update' at the beginning
Description of the environment:
1 controller
1 compute with pinning
1 compute with hp
2 compute with sr-iov
snapshot #767
Full trace:
ERROR [7ff76ccf0880] (manager) Traceback (most recent call last):
File "/usr/lib/
to_return = method(task, *args, **kwargs)
File "/usr/lib/
dry_
File "/usr/lib/
args = getattr(cls, method)
File "/usr/lib/
transaction
File "/usr/lib/
ignore_
File "/usr/lib/
ignore_
File "/usr/lib/
self.
File "/usr/lib/
serialized_
File "/usr/lib/
self.
File "/usr/lib/
serialized_node = base.serialize_
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
serialized_
AttributeError: 'NoneType' object has no attribute 'update'
Changed in fuel: | |
assignee: | Timur Nurlygayanov (tnurlygayanov) → Fedor Zhadaev (fzhadaev) |
summary: |
- NoneType error when deployment starts on barametal lab + NoneType error when deployment starts on baremetal lab |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
It is a regression issue (so code worked fine the week before) and it is Critical issue because we can't deploy environment (with any configuration) of the hardware lab.
Steps To Reproduce are simple:
1. Deploy master node with Fuel 9.2
2. Add bare-metal nodes for controller and computes
3. Press "deploy environment" button
Observed Result:
We got an exception from Nailgun python code about the None parameter, because of the bug in the code.
Note: I know how to fix it, the fix is trivial and shouldn't affect other features.
I'm going to create pull request.