scenario012-standalone fails all the time
Bug #1818643 reported by
Jakub Libosvar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Sagi (Sergey) Shnaidman |
Bug Description
The translation from multinode into standalone didn't go well with tripleo switching from ml2/ovs into OVN. Current scenario012 fails both on multinode and on standalone because of networking misconfiguration. The scenario uses br-tenant provider bridge that used to be created by puppet-neutron, but with the switch to OVN, this bridge is no longer created by puppet-ovn because it relies on heat templates and its configuration.
The job should create br-tenant on the controller node/standalone via os-net-config.
An example of the failed job can be found for now at:
http://
tags: | added: ci |
tags: | added: alert |
Changed in tripleo: | |
milestone: | none → train-1 |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in tripleo: | |
milestone: | train-1 → train-2 |
Changed in tripleo: | |
importance: | Medium → High |
Changed in tripleo: | |
assignee: | Derek Higgins (derekh) → Sagi (Sergey) Shnaidman (sshnaidm) |
status: | Triaged → In Progress |
To post a comment you must log in.
The job you pasted is from when the scenario012 was first merged, and it's a successful run. Do you have logs with failed runs ?