Hello, Hernando! I think Trove calls nova to inject files here: https://opendev.org/openstack/trove/src/branch/master/trove/taskmanager/mode... When cloud-init fails to inject Trove's configuration files, I think you should check the following parameters. 1. `use_nova_server_config_drive` configuration on trove.conf. This value should be True if you use config_drive to inject files. 2. `DIB_CLOUD_INIT_DATASOURCES` environment when buiding your own image. This value should contains `OpenStack` if you set `use_nova_server_config_drive` as False. and I think you should also check cloud-init log using journalctl. Thanks, Hirotaka On Tuesday, June 28, 2022, 09:55:24 PM GMT+9, <openstack-discuss-request@lists.openstack.org> wrote: Send openstack-discuss mailing list submissions to openstack-discuss@lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to openstack-discuss-request@lists.openstack.org You can reach the person managing the list at openstack-discuss-owner@lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Re: Regarding Floating IP is existing Setup (Adivya Singh) 2. Issues With trove guest agent (Hernando Ariza Perez) 3. Openstack keystone LDAP integration | openstack user list --domain domain.com | Internal server error (HTTP 500) (Swogat Pradhan) ---------------------------------------------------------------------- Message: 1 Date: Tue, 28 Jun 2022 18:12:51 +0530 From: Adivya Singh <adivya1.singh@gmail.com> To: Slawek Kaplonski <skaplons@redhat.com>, OpenStack Discuss <openstack-discuss@lists.openstack.org> Subject: Re: Regarding Floating IP is existing Setup Message-ID: <CA+ykd61rKBam86Avut-7g+8EOS4snnzgTmMu5GvAETR3p5EuPg@mail.gmail.com> Content-Type: text/plain; charset="utf-8" hi Slawek, it happens with a given router namespace at a time Regards Adivya Singh On Fri, Jun 24, 2022 at 10:13 PM Adivya Singh <adivya1.singh@gmail.com> wrote:
Hi,
Thanks for the advice and the link,
What i saw when i do testing using tcpdump was "ARP" was not working, and it is not able to associate the FLoating IP with the MAC address of the interface in the VM, When i do the associate and disassociate the VM , it works fine
But the Router NameSpace got changed.
Regards Adivya Singh
On Thu, Jun 23, 2022 at 1:22 PM Slawek Kaplonski <skaplons@redhat.com> wrote:
Hi,
Dnia wtorek, 21 czerwca 2022 13:55:51 CEST Adivya Singh pisze:
hi Eugen,
The current setup is 3 controller nodes, The Load is not much on each controller and the number of DHCP agent is always set to 2 as per the standard in the neutron.conf, The L3 agent seems to be stables as other router namespace works fine under it, Only few router Namespace get affected under the agent.
Is it that problem happens for new floating IPs or for the FIPs which were working fine and then suddenly stopped working? If the latter, was there any action which triggered the issue to happen? Is there e.g. only one FIP broken in the router or maybe when it happens, then all FIPs which uses same router are broken?
Can You also try to analyze with e.g. tcpdump where traffic is dropped exactly? You can check http://kaplonski.pl/blog/neutron-where-is-my-packet-2/ for some more detailed description how traffic should go from the external network to Your instance.
Most of the template having issue , Have all instance having FLoating
IP, a
Stack with a single floating IP have chance of issue very less
Regards Adivya Singh
On Tue, Jun 21, 2022 at 1:18 PM Eugen Block <eblock@nde.ag> wrote:
Hi,
this sounds very familiar to me, I had to deal with something similar a couple of times in a heavily used cluster with 2 control nodes. What does your setup look like, is it a HA setup? I would start checking the DHCP and L3 agents. After increasing dhcp_agents_per_network to 2 in neutron.conf and restarting the services this didn't occur again (yet). This would impact floating IPs as well, sometimes I had to disable and enable the affected router(s). If you only have one control node a different approach is necessary. Do you see a high load on the control node?
Zitat von Adivya Singh <adivya1.singh@gmail.com>:
hi Team,
We got a issue in Xena release, where we set the environment in Ubuntu Platform, But later we get some issues in Floating IP not reachable.
In a Network node, not all router namespace are Impacted and only few of them get affected, So we can not comment Network node has a issue.
The L3 agent where the Router is tied up, Worked just fine, as other routers work Fine.
and the one having issue in Floating IP, if i unassigned and assigned it starts working most of the time.
Any thoughts on this
Regards Adivya Singh
-- Slawek Kaplonski Principal Software Engineer Red Hat