[stein][kolla][haproxy] Waiting for virtual ip to appear

roshan anvekar roshananvekar at gmail.com
Fri Feb 12 09:08:36 UTC 2021


The deployment is failing at such stage that not even logs of any container
have come up yet.

Another scenario is where it went uptil mariadb container spawn, the issue
seemed to be like duplicate primary key appearing for mariadb.

Regards,
Roshan

On Fri, Feb 12, 2021, 2:31 PM Pierre Riteau <pierre at stackhpc.com> wrote:

> Hi Roshan,
>
> Even if you don't have logs on disks, have you checked standard output
> logs captured by Docker?
>
> docker logs haproxy
> docker logs keepalived
> docker logs mariadb
>
> Pierre
>
> On Fri, 12 Feb 2021 at 09:31, roshan anvekar <roshananvekar at gmail.com>
> wrote:
> >
> > Hi Folks,
> >
> > I am deploying a multinode Openstack cluster using kolla-ansible.
> >
> > Network composition:
> > Bond0: network_interface/kolla_internal_vip_address
> > Bond1.101: kolla_external_vip_address/interface
> > Bond1 also had br-ex ovs bridge configured on it directly.
> > Bond2: storage interface
> >
> > With this config I am trying to deploy through kolla.
> >
> > The deployment repeatedly fails at HAproxy: waiting for internal IP to
> appear or mariadb trying to be active via haproxy.
> >
> > Not sure what's the cause of this.
> >
> > I have given unique keepalive_id too.
> > Generated proper passwords as required by stein.
> >
> > Haproxy is not generating any logs too yet.
> >
> > Any help would be appreciated.
> >
> > Regards,
> > Roshan
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210212/fe4d2f2b/attachment.html>


More information about the openstack-discuss mailing list