Comment 2 for bug 2033083

Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

The issue is related to a ipxe request that should be receive from a private IP [1]. However, in 22:10:41, the request comes from an external IP.
  2023-08-24 22:10:41.560 [-] 172.24.5.109 "GET /boot.ipxe HTTP/1.1" 200 1004

The router GW is update with "enable_snat=False" [2]. However, just before the ipxe messages, a new FIP is created with fixed IP 10.1.0.12 and external IP 172.24.5.109 [3]. This new FIP is adding a new NAT rule, similar to the NAT rule deleted when the GW port was updated with "enable_snat=False".

[1]https://f65b0483f01fbf97cb5c-1988f1bc3d637497f7692396b58d77ce.ssl.cf2.rackcdn.com/885087/49/check/ironic-tempest-ipa-wholedisk-bios-agent_ipmitool/0990cd1/controller/logs/apache/ipxe_access_log.txt
[2]https://paste.opendev.org/show/b06qEnS8T33M6DydP2tV/
[3]https://paste.opendev.org/show/bqP5pH5aYF1odKHlHbVo/