Fuel for OpenStack

Network verification does not work with sub-interfaces bonding

Bug #1580587 reported by Yevgeniy on 2016-05-11

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
Fuel for OpenStack	Confirmed	High	Fuel Sustaining	Fuel for OpenStack 10.0
8.0.x	Won't Fix	Medium	Fuel Sustaining	Fuel for OpenStack 8.0-updates
Mitaka	Won't Fix	Medium	Fuel Sustaining	Fuel for OpenStack 9.0
Newton	Confirmed	High	Fuel Sustaining	Fuel for OpenStack 10.0

Bug Description

Scenario:
  1) Deploy cluster with EMC using network template( http://paste.openstack.org/show/496874/ )
  2) Run network verification
Actual results:
  Verification failed.

Method verify_networks. a51a8034-1861-49c6-9b89-3b8d2a06d1ea: MCollective call failed in agent 'net_probe', method 'start_frame_listeners', failed nodes:

ID: 8 - Reason: Failed to run 'net_probe.py -c /tmp/net_probe20160511-8351-bn8hl8'

ID: 9 - Reason: Failed to run 'net_probe.py -c /tmp/net_probe20160511-8368-11154du'

ID: 6 - Reason: Failed to run 'net_probe.py -c /tmp/net_probe20160511-8414-1c9xy5o'

ID: 7 - Reason: Failed to run 'net_probe.py -c /tmp/net_probe20160511-8413-1y8tv0m'

ID: 10 - Reason: Failed to run 'net_probe.py -c /tmp/net_probe20160511-8424-1964rua'

Inspect Astute logs for the details

See original description

Tags:

Yevgeniy (yshapovalov) on 2016-05-12

summary:	- [EMC 3.0.0] Network verification failed + Network verification does not work with bonding
affects:	fuel-plugins → fuel
Changed in fuel:
milestone:	8.0 → none
assignee:	nobody → Fuel for Openstack (fuel)

Yevgeniy (yshapovalov) on 2016-05-12

Changed in fuel:
milestone:	none → 8.0-updates

Revision history for this message

Yevgeniy (yshapovalov) wrote on 2016-05-12: Re: Network verification does not work with bonding

astute.log Edit (20.2 MiB, text/plain)

Revision history for this message

Aleksey Zvyagintsev (azvyagintsev) wrote on 2016-05-12:

Could you please share logs ? network\deployment\etc schemas ?

Aleksey Zvyagintsev (azvyagintsev) on 2016-05-12

Changed in fuel:
status:	New → Incomplete

Revision history for this message

Yevgeniy (yshapovalov) wrote on 2016-05-12:

screenshot_2016-05-12_13.48.41_1024.png Edit (64.5 KiB, image/png)

Revision history for this message

Yevgeniy (yshapovalov) wrote on 2016-05-12:

screenshot_2016-05-12_13.49.02_1024.png Edit (62.5 KiB, image/png)

Revision history for this message

Yevgeniy (yshapovalov) wrote on 2016-05-12:

screenshot_2016-05-12_13.49.14_1024.png Edit (161.5 KiB, image/png)

Yevgeniy (yshapovalov) on 2016-05-12

description:

updated

Yevgeniy (yshapovalov) on 2016-05-12

description:

updated

Revision history for this message

Aleksey Kasatkin (alekseyk-ru) wrote on 2016-05-12:

Network verification does not support bonds of sub-interfaces for now.

summary:	- Network verification does not work with bonding + Network verification does not work with sub-interface bonding
summary:	- Network verification does not work with sub-interface bonding + Network verification does not work with sub-interfaces bonding

Aleksey Kasatkin (alekseyk-ru) on 2016-05-12

Changed in fuel:
status:	Incomplete → Confirmed
tags:	added: feature-network-template

Revision history for this message

Aleksey Kasatkin (alekseyk-ru) wrote on 2016-05-12:

One more problem is:

"Can not read config file net_probe20160512-8368-1gz4lw7"

Seems it is not connected to using of network template and to network configuration.

Nastya Urlapova (aurlapova) on 2016-05-17

tags:

added: customer-found

Dmitry Klenov (dklenov) on 2016-05-18

tags:

added: area-python

Revision history for this message

Aleksandr Didenko (adidenko) wrote on 2016-05-19:

It's rather a feature for network checker then a bug. As Aleksey said, it's not supported currently and adding new features to stable releases is not allowed. Marking as won't fix for stable releases.

tags:

added: feature

Revision history for this message

Sergey Vasilenko (xenolog) wrote on 2016-05-19:

#10

Classic network-checker does not support network_templates. If you really need check of network configuration, and you use fuel 9.0 and higher -- you can try to use connectivity-checker plugin.
https://github.com/xenolog/fuel-plugin-connectivity-checker

This plugin will fail deployment directly after netconfig task if some nodes can't access to anothes by some networks.

Curtis Hovey (sinzui) on 2017-04-13

Changed in fuel:
assignee:	Registry Administrators (registry) → nobody

Oleksiy Molchanov (omolchanov) on 2017-04-14

Changed in fuel:
assignee:	nobody → Fuel Sustaining (fuel-sustaining-team)

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.