Failed to match node "name" with group_id
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Łukasz Oleś |
Bug Description
{"build_id": "2014-04-
Steps to reproduce:
Setup master node, see the notifications
Actual result in UI(path /var/log/
Every ~3 minutes appears the messages:
15-04-2014 12:36:26
Failed to match node 'Untitled (44:be)' with group_id. Add fuelweb_admin NetworkGroup to match '10.20.204.238'
15-04-2014 12:36:21
Failed to match node 'Untitled (f0:d5)' with group_id. Add fuelweb_admin NetworkGroup to match '10.20.204.148'
15-04-2014 12:36:14
Failed to match node 'Untitled (7a:ff)' with group_id. Add fuelweb_admin NetworkGroup to match '10.20.204.230'
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in fuel: | |
importance: | High → Medium |
assignee: | nobody → Fuel Python Team (fuel-python) |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Łukasz Oleś (loles) |
It seems that according to multi-l23 ideas 'admin' network is to be created for every node group. But it doesn't. It isn't created for new cluster either. Additional logic must be introduced to create admin network per cluster and manipulate with it properly. Quick fix can be made to skip writing this warning if there is no admin network in current cluster.