fuel-devops not trackig dependencies between network devices
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel QA Team |
Bug Description
https:/
this code return network objs in random order, meanwhile we may have dependencies between them, e.g.
public network may be bridged with public-raw and we must ensure public raw will be started first.
Workaround is to order networks by ifaces and first bring up ifaces with most dependecies like
- return self.l2networkd
+ devs = self.l2networkd
+ return sorted(devs, key=lambda dev: len(dev.
but proper solution is to build tree and return first ifaces wo dependencies.
In attachment yaml which will help to reproduce issue. It will fail because public will be started before public-raw.
tags: | added: area-devops |
Changed in fuel: | |
milestone: | none → 10.0 |
assignee: | nobody → Fuel QA Team (fuel-qa) |
importance: | Undecided → Medium |
status: | New → Confirmed |
Reviewed: https:/ /review. openstack. org/319258 /git.openstack. org/cgit/ openstack/ fuel-devops/ commit/ ?id=83bfa424a21 13cd897b9b73cdd 36ebfee4fe9ee1
Committed: https:/
Submitter: Jenkins
Branch: master
commit 83bfa424a2113cd 897b9b73cdd36eb fee4fe9ee1
Author: Anton Studenov <email address hidden>
Date: Mon Jul 4 17:55:31 2016 +0300
Proper ordering for objects loaded from templates
- Use OrderedDict for loading objects from yaml template.
- Load objects from db with the order they were saved.
It guarantees that objects will be defined in the same order
that they appear in template file.
- added id field to Group
- added unit tests for yaml_template_load
Related-Bug: #1591750 ddbd5546d06938e 65c9b6bf4bf
Change-Id: I2cafa1fbe156b1