Bug 1508922
Summary: | There are a lot of "404 not found" errors in zaqar-server.log | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Udi Kalifon <ukalifon> |
Component: | openstack-zaqar | Assignee: | 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 M2 | Keywords: | Triaged |
Target Release: | 13.0 (Queens) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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: | |
Embargoed: |
Description
Udi Kalifon
2017-11-02 14:01:47 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? 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. 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/RHEA-2018:2086 |