Network verification failed because node is not available via mcollective
Bug #1551336 reported by
Volodymyr Shypyguzov
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Georgy Kibardin | ||
Mitaka |
Invalid
|
High
|
Georgy Kibardin |
Bug Description
Deploy cluster with active-backup bonding and Neutron VXLAN fails on step 5
Scenario:
1. Create cluster
2. Add 1 node with controller role
3. Add 1 node with compute role and 1 node with cinder role
4. Setup bonding for all interfaces (including admin interface
bonding)
5. Run network verification << FAIL
6. Deploy the cluster
7. Run network verification
8. Run OSTF
With message AssertionError: Task 'verify_networks' has incorrect status. error != ready, 'Method verify_networks. Network verification not avaliable because nodes ["3"] not avaliable via mcollective.
tags: | added: area-python |
Changed in fuel: | |
milestone: | none → 9.0 |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: team-network |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Georgy Kibardin (gkibardin) |
milestone: | 9.1 → 10.0 |
Changed in fuel: | |
status: | Confirmed → Incomplete |
Changed in fuel: | |
status: | Incomplete → Invalid |
To post a comment you must log in.
There are no logs related to deployment in diagnostic snapshot (only bootsrtap and network_verify). It's impossible to do any analysis based on info we have in this bug. Please provide more info and a valid diagnostic snapshot.
Also please confirm that your network infrastructure supports bonding that you're trying to configure.