[tripleo] Use Podman 1.6 in CI
Thank you for all of the feedback so far. The goal is definitely to fix
this everywhere we can, no just in CI. Sorry for my poor choice of words. I
will migrate this discussion over to the RDO community.
On Wed, Jan 8, 2020 at 5:55 PM Jeremy Stanley <fungi at yuggoth.org> wrote:
> On 2020-01-08 15:35:03 -0700 (-0700), Alex Schultz wrote:
> > On Wed, Jan 8, 2020 at 3:30 PM Jeremy Stanley <fungi at yuggoth.org> wrote:
> > > On 2020-01-08 16:49:15 -0500 (-0500), Luke Short wrote:
> > > > We have been running into a situation where an older version of
> > > > Podman is used in CI that has consistent failures. It has problems
> > > > deleting storage associated with a container.
> > > [...]
> > > > The question/ask I have is can we ship/use a newer version of
> > > > Podman in our upstream CI? Or should we continue our efforts on
> > > > making a workaround?
> > > [...]
> > >
> > > This sounds like a problem users of your software could encounter in
> > > production. If so, how does only fixing it in CI jobs help your
> > > users? It seems like time might be better spent fixing the problem
> > > for everyone.
> > Btw fixing CI implies fixing for everyone. In other words, how do we
> > make it available for everyone (including CI). This is one of those
> > ecosystem things because we (tripleo/openstack) don't necessarily ship
> > it but we do need to use it. I'm uncertain of the centos7/podman 1.6
> > support and which branches are affected by this? This might be a
> > better question for RDO.
> I see, "ship/use a newer version of Podman in our upstream CI"
> didn't seem to necessarily imply getting a newer version of Podman
> into RDO/TripleO and the hands of its users. I have a bit of a
> knee-jerk reaction whenever I see someone talk about "fixing CI"
> when the underlying problem is in the software being tested and not
> the CI jobs.
> Jeremy Stanley
-------------- next part --------------
An HTML attachment was scrubbed...