Glance writes stack trace to logs in correct situations
Bug #1699512 reported by
Kairat Kushaev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
Medium
|
Kairat Kushaev | ||
9.x |
Fix Released
|
Medium
|
Kairat Kushaev |
Bug Description
When missing images are requested with glance API v1, long python-style
traceback is stored in glance-api log file. This affects many monitoring
systems and complicates the investigation of real techical issues.
we need get rid of this long stack trace and show error message only.
This affects only glance with registry backend- so it is not applicable to glance v2 and affects v1 only.
Test Case:
1.install openstack cloud, enable v1 registry for glance
2. glance --image-api-version 1 image-show not_existing
AR:a long stack trace with NotFound exception in /var/log/
ER: a short message with 404 exception in /var/log/
description: | updated |
description: | updated |
Changed in mos: | |
status: | New → In Progress |
Changed in mos: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
https:/ /bugs.launchpad .net/glance/ +bug/1533970 /bugs.launchpad .net/glance/ +bug/1654270- upstream bugs. upstream fix were rejected cause v1 is not supported in upstream
https:/