[PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

[Gaudenz Steinlin]

Thomas Goirand <zigo at debian.org> writes:

> On 11/24/2014 01:52 AM, Gaudenz Steinlin wrote:
>> Why do you set PIDFile at all? IMO pidfiles are unnecessary when the
>> daemons managed by systemd run in the foreground and thus there is no
>> need for a pidfile at all.
>
> The point is, the way things are designed currently, we don't use
> foreground at all right now, we continue to use start-stop-daemon and
> execute the init.d startup script, even when using systemd. This is a
> bad design that would need improvement, and I would welcome a better
> implementation within openstack-pkg-tools. I would very much like to see
> some patches to use foreground (the way it's done in Fedora?), but it
> should support all properties and implementation of what's done in the
> init scripts.

I see. Wouldn't it be better to completely rely on the sysvinit
compatibility of systemd then and not ship any unit files at all? What's
the advantage of having systemd units that only wrap around sysv init
scripts?

>
> On 11/24/2014 04:54 AM, Mikaël Cluseau wrote:> Hi,
>> isn't it a duplicate of
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767711 ?
>
> Yes it is. And that's a general issue with all OpenStack packages in
> Sid/Jessie right now. We need to fix all of this before the 5th of
> December deadline.

I'll try to find some time to have a look, but can't promise anything.

Gaudenz