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

[Gaudenz Steinlin]

Hi

Mikaël Cluseau <mcluseau at isi.nc> writes:

> Hi Gaudenz,
>
> I will focus on the so called "minimal set" for now. If you don't mind, 
> we will open another bug to improve systemd's integration after this one 
> is fixed.
>
> On 12/03/2014 04:58 AM, Gaudenz Steinlin wrote:
>> Did you test the patches with the "minimal set of changes". I think we 
>> need strong arguments that they are working if we want to propose them 
>> to the Release Team for jessie. I currently don't have a good setup to 
>> test such patches. 
>
> I did with keystone but developper tests are never to be trusted ;-) Its 
> quite easy to test BTW, as root:
>
> apt-get build-dep openstack-pkg-tools
> git clone -b debian/unstable 
> https://github.com/MikaelCluseau/debian-openstack-pkg-tools.git
> cd debian-openstack-pkg-tools
> debuild -us -uc -b
> dpkg -i ../openstack-pkg-tools_19_all.deb
>
> Then you can build any other OpenStack package from source. For 
> instance, keystone:
>
> apt-get source keystone
> cd keystone-*/
> debuild -us -uc -b
> dpkg -i ../keystone_*.deb

OK I tested keystone on unstable now and this works as it should. It's
definitely an improvement over the current unit file which does not work
at all. I did not go down the route to do a full openstack installation
but I also installed nova and the service units there work too. I did
not go all the way to have a working setup, but the problems I have seem
to be unrelated to the systemd unit files.

One thing I noticed is that all services are disabled by default even
though they were configured through debconf and should be ready to use.
Is this intentional as an off by default behavior or is this a bug. How
is this handled with sysvinit?

Gaudenz