Cleaning this after a while, no further action is needed.
- T/X have a workaround in Neutron
- Latter versions of keepalive use systemd MAINPID tracking which is somewhat
more robust in this regard
That said in the context this appeared it is fixed, lets set the old
tasks to Won't Fix unless
** Changed in: keepalived (Ubuntu Xenial)
Assignee: Joshua Powers (powersj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1583503
Title:
** Changed in: keepalived (Ubuntu Xenial)
Status: Triaged => Incomplete
** Changed in: keepalived (Ubuntu Trusty)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in
** Changed in: keepalived (Ubuntu Xenial)
Assignee: (unassigned) => Joshua Powers (powersj)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1583503
Title:
Yes, this issue is fixed by https://review.openstack.org/#/c/296532/ for
everyone. Any PID file that would block keepalived from starting
(regardless of the contents, empty/numeric/non-numeric) is removed
before keepalived is started.
--
You received this bug notification because you are a
Does https://review.openstack.org/#/c/296532/ fix the issue for
everyone?
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1583503
Title:
keepalived fails to start when
With version 2:8.1.0-0ubuntu0.16.04.2 from xenial-proposed the stale pid
file is removed and the l3-agent can start the new keepalived
successfully.
Maybe we could also get rid of this error that is still being logged:
2016-05-20 10:43:00.913 16153 ERROR neutron.agent.linux.utils [-] Unable
to
2:8.0.0-0ubuntu1 from Ubuntu Xenial version was published on 2016-04-08
and thus missed patch https://review.openstack.org/#/c/299135/ that
worked around this issue by removing keepalived PID files and was merged
on 2016-04-12. There is already 8.1.0 package that contains this fix
according to
** Changed in: neutron
Status: New => Confirmed
** Changed in: neutron
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1583503
Neutron cannot assume what keepalived version is used underneath, so we
tend to introduce workarounds for issues such as this. @Hynek, can you
take a look? I remember you tackled a similar issue recently.
** Changed in: neutron
Assignee: (unassigned) => Hynek Mlnarik (hmlnarik-s)
** Tags
Ah, right, sorry for not checking Yakkety, I'm still not used to Xenial
having been released ... ;)
So for me this affects Xenial, package version is 1:1.2.19-1. From a
small check, 1:1.2.7-1ubuntu1 on Trusty seems also to be affected, but
having a fix in Xenial would be good enough for me.
--
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Yakkety has 1.2.20, so this is Fix Released. You asked for a backport
but you haven't said what package version you're using, what release you
want the fix backported to or in which releases you have confirmed the
12 matches
Mail list logo
