veth vif status is down after compute reboot
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
Medium
|
Ashok Singh | |||
R2.21.x |
Fix Committed
|
Medium
|
Ashok Singh | |||
R2.22.x |
Fix Committed
|
Medium
|
Ashok Singh | |||
R3.0 |
Fix Committed
|
Medium
|
Ashok Singh | |||
Trunk |
Fix Committed
|
Medium
|
Ashok Singh |
Bug Description
root@b1s21:
<active type="string" identifier=
root@b1s21:
root@b1s21:
23: veth3fd177d9-0: <BROADCAST,
link/ether 6a:f3:ea:32:6c:30 brd ff:ff:ff:ff:ff:ff
root@b1s21:
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: int-f0ce38f1-d: <BROADCAST,
link/ether 02:72:aa:72:89:36 brd ff:ff:ff:ff:ff:ff
3: gw-3fd177d9-0a: <BROADCAST,
link/ether 02:a7:45:34:35:9c brd ff:ff:ff:ff:ff:ff
However the status of the other veth interface bound to netns is active
root@b1s21:
<active type="string" identifier=
The gcore of the agent will be at /cs-shared/
bug update...