Bug 1508922

Summary: There are a lot of "404 not found" errors in zaqar-server.log
Product: Red Hat OpenStack Reporter: Udi <ukalifon>
Component: openstack-zaqarAssignee: Thomas Hervé <therve>
Status: CLOSED ERRATA QA Contact: Shai Revivo <srevivo>
Severity: medium Docs Contact:
Priority: low    
Version: 12.0 (Pike)CC: apevec, jschluet, lhh, rrasouli, therve
Target Milestone: Upstream M2Keywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-zaqar-6.0.1-0.20180302005413.4659f9b.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:39:00 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:

Description Udi 2017-11-02 14:01:47 UTC
Description of problem:
This error is logged periodically (about once a minute) to zaqar-server.log:

INFO zaqar.transport.websocket.protocol [-] Response: API v2 txt, 201. Request: action "queue_create", body {"queue_name": "85fa5589-6fd3-40da-baf6-85dbbffb52a8"}.
INFO swiftclient [-] REQ: curl -i -X PUT -H "if-none-match: *" -H "x-delete-after: 10000" -H "X-Auth-Token: gAAAAABZ-uQDpYLc..."
INFO swiftclient [-] RESP STATUS: 404 Not Found
INFO swiftclient [-] RESP HEADERS: {u'Date': u'Thu, 02 Nov 2017 09:23:15 GMT', u'Content-Length': u'70', u'Content-Type': u'text/html; charset=UTF-8', u'X-Openstack-Request-Id': u'txe8ab1cf141dc4e0a91ff4-0059fae403', u'X-Trans-Id': u'txe8ab1cf141dc4e0a91ff4-0059fae403'}
INFO swiftclient [-] RESP BODY: <html><h1>Not Found</h1><p>The resource could not be found.</p></html>

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install the undercloud 
2. Look in /var/log/zaqar/zaqar-server.log

Actual results:
404 errors

Additional info:
This error might be harmless. No observable problems are known to be related to this issue. It just looks like something that shouldn't happen.

Comment 5 Udi 2018-04-18 05:45:02 UTC
Hi Thomas. The patch only reduces the logging level - what causes these 404s in the first place, and why is it ok to just not log them?

Comment 6 Thomas Hervé 2018-04-18 07:46:24 UTC
Zaqar needs to check object existence in Swift. 404 are returned when such objects don't exist. It's part of the normal lifecycle that those objects don't exist, there is nothing wrong in that case.

Comment 8 errata-xmlrpc 2018-06-27 13:39:00 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.