Bug 1790792

Summary: [OSP13]Network ci update jobs are failing when it tries to start the new containers: already exists
Product: Red Hat OpenStack Reporter: Candido Campos <ccamposr>
Component: python-paunchAssignee: Bogdan Dobrelya <bdobreli>
Status: CLOSED ERRATA QA Contact: Jad Haj Yahya <jhajyahy>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: akaris, bcafarel, bdobreli, jhajyahy, mburns, sathlang, yobshans
Target Milestone: zstreamKeywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-paunch-2.5.0-11.el7ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-10 11:23:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 12 Bogdan Dobrelya 2020-01-17 15:11:56 UTC
raised severity as this blocks all minor updates in OSP13 z streams

Comment 13 Bogdan Dobrelya 2020-01-27 09:35:32 UTC
*** Bug 1794846 has been marked as a duplicate of this bug. ***

Comment 14 Andreas Karis 2020-01-28 11:17:14 UTC
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 ...

Comment 15 Bogdan Dobrelya 2020-01-28 11:23:38 UTC
@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.

Comment 16 Bogdan Dobrelya 2020-01-28 11:27:34 UTC
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

Comment 17 Bogdan Dobrelya 2020-01-28 11:29:32 UTC
ugh, actually I meant "...so it should not produce duplicates as in 1794121" (unsure about root cause in BZ1793455 yet!)

Comment 18 Andreas Karis 2020-01-28 12:05:16 UTC
Ok I will keep that in mind for BZ1794121 once we can test this further with the customer (need a maintenance window)

Comment 24 errata-xmlrpc 2020-03-10 11:23:24 UTC
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