Package dependencies, podman, dnf modules

[Cédric Jeanneret]

This is an LP in order to track a mailing list thread - specifically the possible solutions:
http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019625.html

TLDR;
currently podman comes from a specific module stream (container-tools:2.0) while the default stream is container-tools:rhel8. It might happen (and, well, it DOES) that an operator overlook the doc point about the stream switch, and ends up with the wrong podman version.
RPM doesn't know about modules, so we can't get a nice "Requires @container-tools:2.0/podman" or anything close to it.

A current test[1] is about adding some bash script in tripleoclient spec file in order to ensure we get the correct stream, but it's mostly wrong, since it crashes the install once podman is already on the system..
[1] https://review.rdoproject.org/r/#/c/31411/

Another solution is to add some logic to tripleo-ansible in order to switch to the right stream and install podman, instead of adding the "Requires" in tripleoclient spec file - though it might create some other issues at some point.

[wes hayutin (weshayutin)]

Adding promotion-blocker for visibility to the prod-chain.. this issue is something we should track
thanks

[Alan Pevec (apevec)]

> RPM doesn't know about modules
yes, dnf is the component handling modules and you can express dependencies among modules

> so we can't get a nice "Requires @container-tools:2.0/podman" or anything close to it.

this could be expressed if tripleoclient were built as a module and have in its modulemd:
  dependencies:
  - buildrequires:
      platform: [el8]
    requires:
      platform: [el8]
      container-tools: [2.0]

Not suggesting to do that, just for completeness of options :)

[Cédric Jeanneret (cjeanner)]

The work around tirpleo-repos[1] will actually solve this issue for the upstream, since it will ensure we're using the correct stream version, among different things.

[1] https://galaxy.ansible.com/tripleo/repos