Compute node confuses eth interface number during deploy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Sebastian Kalinowski | ||
5.1.x |
Fix Committed
|
High
|
Sebastian Kalinowski |
Bug Description
astute_sha: 65eb911c38afc0e
auth_required: true
build_id: 2014-11-18_22-00-23
build_number: '114'
feature_groups:
- mirantis
fuellib_sha: 5a5275370b33ab3
fuelmain_sha: e556f0e1b00c30e
nailgun_sha: b0add09c4361fee
ostf_sha: 82465a94eed4eff
production: docker
release: '6.0'
Steps to reproduce
1. Start deployment with 3 controllers in HA, and 97 compute nodes with ceph on CentOS with Neutron GRE
Deployment was failed because one node goes to offline
Log from jenkins job
01:31:27 2014-11-20 01:31:27,681 - python.http - DEBUG - PUT [{'interfaces': [{u'name': u'eth0', u'state': u'up', u'mac': u'00:25:
Output from Fuel
[root@fuel init.d]# fuel nodes | grep error
45 | error | compute_77 | 1 | 10.20.1.42 | 0c:c4:7a:1d:f1:e4 | ceph-osd, compute | | False | 1
As we see on attached screenshot from IPMI eth0 и eth1 confuses with eth2 and eth3
summary: |
- Compute node confuses number of eth interfaces during deploy + Compute node confuses eth interface number during deploy |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Sebastian Kalinowski (prmtl) |
status: | Triaged → In Progress |
no longer affects: | fuel/5.1.x |
no longer affects: | fuel/6.0.x |
I've heard about same behavior (that node goes offline, and deployment fails) from a few sources already. Sergey, thanks for catching the interfaces issue! I hope we will be able to find a way to fix it in 6.0.