[mos-xenial] "ip netns list" can produce different output format
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Medium
|
Dmitry Burmistrov | ||
Mitaka |
Won't Fix
|
Medium
|
Dmitry Burmistrov | ||
Newton |
Fix Committed
|
Medium
|
Dmitry Burmistrov |
Bug Description
Detailed bug description:
Here outputs from different environments, second one has different output
root@14.04:~# ip netns list | tail -1
vrouter
root@16.04:~# ip netns list | tail -1
haproxy (id: 0)
Steps to reproduce:
Install Ubuntu 16.04 with iproute2=
Expected results:
ocf scripts handle both outputs
Actual result:
ocf scripts works only with 1st outputs
Reproducibility:
-
Workaround:
-
Impact:
Launch MOS with Ubuntu 16.04
Description of the environment:
Operation system: Ubuntu 16.04
Versions of components: -
Reference architecture: -
Network model: -
Related projects installed: -
Additional information:
affected scripts:
- ns_IPaddr2
- ns_dns
- ns_haproxy
- ns_vrouter
command/function: `ip netns list | grep "$OCF_RESKEY_ns"` # "check_ns" function
In any case script should be smarter to handle both outputs.
Maybe "check_ns" function can be extracted to "library" file with common functions (instead of duplicating code in all scripts).
tags: | added: area-linux |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
status: | Confirmed → In Progress |
tags: | added: ubuntu-xenial |
tags: |
added: mos-xenial removed: ubuntu-xenial |
summary: |
- "ip netns list" can produce different output format + [mos-xenial] "ip netns list" can produce different output format |
patch: https:/ /review. openstack. org/#/c/ 313303/