raised severity as this blocks all minor updates in OSP13 z streams
*** Bug 1794846 has been marked as a duplicate of this bug. ***
Are you sure that this is a paunch issue? ~~~ 2020-01-16 13:54:01.505 573180 DEBUG paunch [ ] /usr/bin/docker-current: Error response from daemon: service endpoint with name neutron_ovs_agent already exists. ~~~ This looks like BZ1793455) Which I could work around by downgrading docker from -108 to -104 ...
@Andreas I was able to finish the staging clone of the reported jenkins job having the paunch fixes applied. Before that it was reproduced each time I ran the job, so doesn't look like some intermittent issue.
But indeed that fact does not make issues on the docker.108 side entirely impossible. Was it a regression in 'rm -f' CLI perhaps? Anyway, stopping doing rm -f by paunch seems also helped. But there was more than just that, other of the missing backports should also improve the idempotency and detection of containers by paunch, so it should not produce duplicates as in BZ1793455
ugh, actually I meant "...so it should not produce duplicates as in 1794121" (unsure about root cause in BZ1793455 yet!)
Ok I will keep that in mind for BZ1794121 once we can test this further with the customer (need a maintenance window)
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://access.redhat.com/errata/RHBA-2020:0760