Bug 1663456

+++ This bug was initially created as a clone of Bug #1654659 +++

Description of problem:

When installing RDO packages into a container image, it is preferable to use the systemd_ordering macro to not bring in all of the systemd and its dependencies into containers.

According to https://fedoraproject.org/wiki/Packaging:Scriptlets:
If a package is suitable for installation without systemd (in a
container image, for example) and does not require any of the
systemd mechanisms such as tmpfiles.d, then the systemd_ordering macro
MAY be used instead of the systemd_requires macro. 


**Topic with patches proposed**: https://review.rdoproject.org/r/#/q/topic:base-container-reduction

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Bogdan Dobrelya on 2018-11-29 11:20:58 UTC ---

It would be also very nice to have this for Fedora28. Please let me know if I have to clone this bug for that release? (Not sure what to do to the patch then, I submitted it against master of https://src.fedoraproject.org/rpms/cronie repo, and I can see no stable branches there)

--- Additional comment from Panu Matilainen on 2018-11-29 11:21:47 UTC ---

This has nothing to do with rpm.

--- Additional comment from Bogdan Dobrelya on 2018-11-29 11:30 UTC ---

this version of the patch also covers SUSE and RHEL distros

--- Additional comment from Bogdan Dobrelya on 2018-11-29 11:32:34 UTC ---

@Panu, I'm sorry I was confused by the 'rpm' path used in the repo URL https://src.fedoraproject.org/rpms/cronie :)

--- Additional comment from Tomas Mraz on 2018-11-30 08:39:19 UTC ---

What would be the point of installing cronie into a container where systemd is not present? This is a system service which cannot be started without systemd.

Also we do not ship anything that is specific to other distros than Fedora and RHEL in Fedora package spec so the SUSE part is irrelevant.

--- Additional comment from Bogdan Dobrelya on 2018-11-30 10:01:18 UTC ---

@Tomas, in TripleO (OpenStack installer) we have containers that run crond and consume tasks from /var/spool/cron (puppet generates those via the tooling we have in tripleo to trigger puppet in config-containers https://review.openstack.org/#/c/478919/5/docker/docker-puppet.py), like in this example https://review.openstack.org/#/c/485865/2/docker/services/heat-api.yaml@94

So that should be working totally w/o having systemd in containers AFAICT.

--- Additional comment from Bogdan Dobrelya on 2018-11-30 10:08 UTC ---



--- Additional comment from Tomas Mraz on 2018-11-30 10:27:38 UTC ---

OK, then.

--- Additional comment from Bogdan Dobrelya on 2018-11-30 10:40:43 UTC ---

Thank you Tomas! What else shall I do to have it also accepted into fc28?

--- Additional comment from Tomas Mraz on 2018-11-30 10:49:06 UTC ---

I wonder if it is really a safe change to do in already released Fedoras.

--- Additional comment from Bogdan Dobrelya on 2018-11-30 13:20:44 UTC ---

It would be very nice to have this for f28-stabilized as well.