We recently triggered the tagging of builds to cloud9s-openstack-dalmatian-testing with one API call (tasks ID from 4243609 to 4243857). The tagging operation went fine, but our program got stucked still awaiting for a response from CBS server [1]). It seems that the tagging session was not closed properly (note that the TCP session was still open in client side) Is it possible to check the logs to understand the reason of this behavior ?
[1] https://review.rdoproject.org/zuul/build/d2bd9d18a5184efeba1147e729302bef
As we don't control the various networks/routers between your env and ours, it's difficult to have a look. Is that the first time it happens at your side ? Tempted to just close it until we find something that can be reproduced easily and only then we'd be able to debug that in sync mode somewhere (as nothing would show up in the normal logs anyway)
Metadata Update from @arrfab: - Issue tagged with: need-more-info
Metadata Update from @arrfab: - Issue tagged with: cbs
Ok WFM. We were just curious if something explicit would show up in the logs. That's the second time IIRC, but we can live with it as it's a post job in our CI/CD (so even if it ends up TIMED OUT, it's not a big deal as long as the builds are tagged). Thank you for having taken a look.
Metadata Update from @jcapitao: - Issue close_status updated to: Insufficient Data - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.