Wrong fuel plugin can break nailgun
Bug #1501681 reported by
Vyacheslav Struk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Sergey Slipushenko | ||
7.0.x |
Won't Fix
|
High
|
Sergey Slipushenko |
Bug Description
Fuel 7.0, release
Plugin with malformed network_roles.yaml could be successfully built and installed.
Just enabling the plugin breaks the environment. Web UI ignores all the clicks on that envioronment, nailgun logs returns http error 500.
Here is content of wrong network_roles.yaml to reproduce the bug:
- id: "ifname"
default_mapping: "private"
properties:
subnet: false
gateway: false
vip:
- name: "null"
description: | updated |
summary: |
- Wrong fuel plugin can brake nailgun + Wrong fuel plugin can break nailgun |
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
importance: | Undecided → High |
milestone: | none → 8.0 |
Changed in fuel: | |
status: | New → Triaged |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Sergey Slipushenko (sslypushenko) |
Changed in fuel: | |
status: | Triaged → In Progress |
tags: | added: area-python |
Changed in fuel: | |
status: | Fix Committed → In Progress |
tags: | added: on-verification |
To post a comment you must log in.
Is this an issue with the plugins or is this an issue that needs to be resolved by confirming the validity of the network_roles.yaml file and communicating to the user if it is not valid?
For example, if a user uploaded the same network_roles file as shown above, would it still fail the same way? Or is this unique to plugins?