So problem is elsewhere. /var/run should be symlink to /run and all new services should use /run.

Our old version systemd in rhel7 uses old path, so for example systemctl is working without problem. But there is couple of new parts, which use the new library which looks in /run. Fix for this in systemd should be quite easy, but I would like to fix the culprit, so it works for all packages.

My first suspision is filesystem package, which should create this symlink in pretrans.

D: filesystem-3.2-18.el7.x86_64: SHA1 digest v hlavičce: OK (170efc540bf1be952e5fbda6302ad1e133047ab8)
%pretrans(filesystem-3.2-18.el7.x86_64): running <lua> scriptlet.

Thanks for the quick answer. I didn't knew about this part.

The stuff around the var/lock is properly in place but indeed the run and var/run isn't. It's maybe on my side, I'm checking that and keep you posted.

Thanks for the hint.

Created attachment 927945 [details]
Initial Chroot creation

I've been double checking. 

- Before the creation of the chroot, the /var/run & /var/lock doesn't exist
- After the chroot creation, /var/lock is a symlink but /var/run is a directory

Please find attached the trace of the package installation process and the command used. 

Can you confirm this behaviour ?

Note that doing a " yum --installroot /var/lib/debootstrap/install/RH7.0-1.6.0/base install -y filesystem" is enough to trigger the bug.

Installing the filesystem rpm by itself with a very crappy way shows that it does the job of creating the /var/run properly. So another package is killing that stuff after... I have to go for today, I'll inspect the other packages on that selection tomorrow.

It might be anything - pretrans scriptlet in filesystem works just fine for most of the usecases, however I haven't tried --installroot option before. It might be yum issue, it might be some other package doing something wrong - or some corner case causing the pretrans failure. Definitely needs more debugging to find a culprit.

Sounds like I got the culprit. I did pause yum at the earlier stages even before downloading or installing anything.

I saw that : /var/lib/debootstrap/install/RH7.0-1.6.0/base/var/run/yum.pid

Looking at yum source-code we have :
YUM_PID_FILE = '/var/run/yum.pid' as shown here : http://yum.baseurl.org/gitweb?p=yum.git;a=blob;f=yum/constants.py;h=5c728d4b86cbd4f6363b47582c578080e3bfb553;hb=HEAD#l21

Then we do have a doLock() function that setup PID file at the earlier stage of yum.
http://yum.baseurl.org/gitweb?p=yum.git;a=blob;f=yum/__init__.py;h=bf13f40d4f09b63c2c28a99de758cfa18bb0fc17;hb=HEAD#l2148

So we have here an issue that prevent creating a clean chroot by using yum install-root

I do see several options to solve this issue :
- Changing YUM_PID_FILE to /run
- Adding a quirk in the pretrans to move everything from /var/run to /run, delete /var/run and create the symlink

Other options ?

Note that I did forced manually my YUM_PID_FILE to /run and that made the /var/run to be created properly.

I do propose https://github.com/ErwanAliasr1/yum/commit/bea1d001a20234211d40768b61b383c5d76eea92

This is fixed upstream by:

commit ffb40e6a1b9c3f4b5b08151a04a5922fc5a9b521
Author: James Antill <james>
Date:   Wed Jan 29 16:04:18 2014 -0500

    Don't create lockdir directories, as they are magic now. BZ 975864

Good news, thanks !

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0398.html