Rhosp: TSN provison fails if the interface of TSN and compute nodes are not same in contrail-net.yaml
Bug #1709974 reported by
shajuvk
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R3.2 |
Won't Fix
|
Critical
|
Michael Henkel | |||
| R4.0 |
Won't Fix
|
High
|
Michael Henkel | |||
| R4.1 |
Won't Fix
|
High
|
Michael Henkel | |||
| R5.0 |
Fix Committed
|
High
|
Michael Henkel | |||
| Trunk |
Fix Committed
|
High
|
Michael Henkel | |||
Bug Description
Contrail-TSN provisioning failed in R3.2 since the vrouter nic name and TSN node nic name are different.
Vrouter eno1 wil be vhost0 but in TSN node it is eth1. contrail-net.ymal has an entry VrouterPhysical
We don't have a separate option in contrail-net.yaml for specifying nic name for TSN.
| information type: | Proprietary → Public |
| tags: | added: provisioning rhosp |
| description: | updated |
Revision history for this message
| Michael Henkel (mhenkel-3) wrote | #1 |
Revision history for this message
| Jeba Paulaiyan (jebap) wrote | #2 |
Revision history for this message
| Michael Henkel (mhenkel-3) wrote | #3 |
| tags: | added: beta-blocker |
Revision history for this message
| Michael Henkel (mhenkel-3) wrote | #4 |
To post a comment you must log in.
This problem cannot be solved in OSP10 as there is only a global definition for the vrouter interface. In OSP11 it will be per role. In OSP12 it won't be needed anymore as we'll use os-net-config.