o-hm0 port doesn't receive IP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Octavia Charm |
Triaged
|
High
|
Unassigned |
Bug Description
I have deployed Octavia with charm version 34 (latest stable) and OVN network on a functional Openstack Wallaby cloud, based on Ubuntu Focal.
Everything works correctly when deploying an Amphorae instance until Octavia tries to check the status connecting to port 9443.
I had these in my logs:
2021-10-21 12:06:10.183 109815 WARNING octavia.
Ports are UP in openstack port list
octavia-
fa:16:3e:cb:98:49 | ip_address=
Amphorae instance port:
fa:16:3e:10:87:64 | ip_address=
On octavia LXD container, port o-hm doesn't have any IP, nor there is a DHCP service enabled or config file in /etc/dhcp/octavia.
7: o-hm0: <BROADCAST,
link/ether fa:16:3e:cb:98:49 brd ff:ff:ff:ff:ff:ff
inet6 fe80::840b:
valid_lft forever preferred_lft forever
Once I added the IP from the port: ip a a 10.21.0.141/24 dev o-hm0 , these changed in logs:
2021-10-21 12:06:55.231 109815 WARNING octavia.
2021-10-21 12:07:00.476 109815 INFO octavia.
2021-10-21 12:07:12.735 109815 INFO octavia.
2021-10-21 12:07:13.685 109815 INFO octavia.
2021-10-21 12:07:21.256 109815 INFO octavia.
2021-10-21 12:07:28.420 109815 INFO octavia.
2021-10-21 12:07:42.795 109815 INFO octavia.
After this, I can ping the Amphorae image:
root@juju-
PING 10.21.0.27 (10.21.0.27) 56(84) bytes of data.
64 bytes from 10.21.0.27: icmp_seq=1 ttl=64 time=2.14 ms
64 bytes from 10.21.0.27: icmp_seq=2 ttl=64 time=1.25 ms
64 bytes from 10.21.0.27: icmp_seq=3 ttl=64 time=0.650 ms
64 bytes from 10.21.0.27: icmp_seq=4 ttl=64 time=0.567 ms
summary: |
- hm0 port binding_failed on Wallaby/Focal + o-hm0 port doesn't receive IP |
description: | updated |
Changed in charm-octavia: | |
importance: | Undecided → High |
Changed in charm-octavia: | |
assignee: | nobody → Hemanth Nakkina (hemanth-n) |
tags: |
added: seg removed: sts |
tags: |
added: sts removed: seg |
Changed in charm-octavia: | |
assignee: | Hemanth Nakkina (hemanth-n) → nobody |
status: | In Progress → Triaged |
Hello Radu,
I just hit a similar issue and have spent some time looking at this.
It looks like there's been a bug fix for a different bug, https:/ /bugs.launchpad .net/charm- octavia/ +bug/1893446, which will cause the octavia units to go into a blocked state if the port isn't set up right. That's in the stable/21.10 release of the OpenStack charms, which would currently mean cs:octavia-37.
This caused me to review code and docs a bit, and it seems to me like we both may want to run the configure-resources action. Quoting from the charm's README:
> By executing the configure-resources action the charm will create the resources required for operation of the Octavia service. If you want to manage these resources yourself you must set the create-mgmt-network configuration option to False.
>
> You can at any time use the configure-resources action to prompt immediate resource discovery.
Hope this helps; I'm going to see if we can run this on my side to resolve the issue.
Best Regards,
Paul Goins