Bug 1456334
| Summary: | Creating LB on external network - The amphora's has only HM interface | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alexander Stafeyev <astafeye> |
| Component: | openstack-octavia | Assignee: | Nir Magnezi <nmagnezi> |
| Status: | CLOSED NOTABUG | QA Contact: | Alexander Stafeyev <astafeye> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 11.0 (Ocata) | CC: | astafeye, ihrachys, lpeer, majopela, nyechiel, oblaut |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-06-19 06:43:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1433523 | ||
Hi Alex,
Could you please recheck and see if you find it in the amphora-haproxy namespace?
Here's how I tested it (devstack):
$ neutron lbaas-loadbalancer-create --name lb2 public-subnet
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
Created a new loadbalancer:
+---------------------+--------------------------------------+
| Field | Value |
+---------------------+--------------------------------------+
| admin_state_up | True |
| description | |
| id | fcc4fe09-334b-40c7-b7a5-1beffe582541 |
| listeners | |
| name | lb2 |
| operating_status | OFFLINE |
| pools | |
| provider | octavia |
| provisioning_status | PENDING_CREATE |
| tenant_id | 6f53cdeee0d343af814207988e7b6550 |
| vip_address | 172.24.4.3 |
| vip_port_id | aa6dde11-d2e1-4bfb-b583-71aea0bbc801 |
| vip_subnet_id | 32dd48ca-55b6-4a7a-9786-d54487bb5fb0 |
+---------------------+--------------------------------------+
$ nova list | awk '/lb-mgmt/ {print $12,$13}'
lb-mgmt-net=192.168.0.6; public=172.24.4.14
**from within the amphora**
# ip netns exec ip a
Cannot open network namespace "ip": No such file or directory
root@amphora-982badea-b462-49bc-b676-e6c415f6ead7:~# ip netns exec amphora-haproxy ip a
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether fa:16:3e:2e:d1:3c brd ff:ff:ff:ff:ff:ff
inet 172.24.4.14/24 brd 172.24.4.255 scope global eth1
valid_lft forever preferred_lft forever
inet 172.24.4.3/24 brd 172.24.4.255 scope global secondary eth1:0
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe2e:d13c/64 scope link
valid_lft forever preferred_lft forever
root@amphora-982badea-b462-49bc-b676-e6c415f6ead7:~# ip netns exec amphora-haproxy ping 172.24.4.1
PING 172.24.4.1 (172.24.4.1) 56(84) bytes of data.
64 bytes from 172.24.4.1: icmp_seq=1 ttl=64 time=0.448 ms
64 bytes from 172.24.4.1: icmp_seq=2 ttl=64 time=0.269 ms
As a followup to comment #1, Closing this bug. If you feel that this is indeed a bug and interfaces are absent from the namespace, please reopen. |
Description of problem: After creation of a LB with external subnet id, the amphora VMs booted but nor LB VIP nor amphoras has connectivity. After login into the amphora I saw that it has no "data" interfaces. Version-Release number of selected component (if applicable): rhos11 How reproducible: 100% Steps to Reproduce: 1.Deploy ospd with octavia and run octavia post deployment steps 2. Create LB in external subnet 3. Actual results: 1. | 0e4d6eee-900c-4f9c-8085-b59a4f5adcd0 | amphora-42601e2b-3250-4cce-857b-b06494093b10 | ACTIVE | - | Running | int_net=192.168.2.12; lb-mgmt-net=192.168.199.52; public=10.0.0.217 | | e92e9e8f-8e8d-41ba-a7b8-6c691776bd8a | amphora-557a963a-1dc7-4bef-83b5-fdc8a04a6288 | ACTIVE | - | Running | int_net=192.168.2.8; lb-mgmt-net=192.168.199.51; public=10.0.0.218 | + The amphoras has ip of the internal network even though we did not configure anything with internal network. (192.168.2.X) 2. [root@amphora-42601e2b-3250-4cce-857b-b06494093b10 ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast state UP qlen 1000 link/ether fa:16:3e:52:8b:61 brd ff:ff:ff:ff:ff:ff inet 192.168.199.52/24 brd 192.168.199.255 scope global dynamic eth0 valid_lft 65352sec preferred_lft 65352sec inet6 fe80::f816:3eff:fe52:8b61/64 scope link valid_lft forever preferred_lft forever there are no ports with needed address, only HM port. Expected results: we should have connectivity and have only relevant ports while executing nova list , and on the vm Additional info: