Zun

Server return 500 on non-existing volume uuid

Bug #1742346 reported by hongbin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zun
Fix Released
High
miaohb

Bug Description

Description
===========
Create a container with a non-existing cinder volume uuid. The server returns 500

Reproduce
=========
$ zun run --mount source=$(uuidgen),destination=/data nginx
ERROR: Internal Server Error (HTTP 500) (Request-ID: req-90fa7dfb-d881-4510-ae6d-0b6bc0be4dad)

Expect
======
Server return 4xx response

Actual
======
Server return 500 response

NOTE
====
NOTE: this bug occurred only if a *uuid* is passed (pass a cinder volume name is working fine).

hongbin (hongbin034)
Changed in zun:
importance: Undecided → High
status: New → Triaged
Changed in zun:
assignee: nobody → Vivek Jain (vivek-jain-openstack)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to zun (master)

Fix proposed to branch: master
Review: https://review.openstack.org/536248

Changed in zun:
assignee: Vivek Jain (vivek-jain-openstack) → miaohb (miao-hongbao)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to zun (master)

Reviewed: https://review.openstack.org/536248
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=6281d7aa6f60ecd999e47790b5e53fe6f04108ee
Submitter: Zuul
Branch: master

commit 6281d7aa6f60ecd999e47790b5e53fe6f04108ee
Author: miaohb <email address hidden>
Date: Mon Jan 22 00:22:36 2018 -0800

    Catch exception in volume get

    Server return 500 when creating a container with non-existing volume
    uuid in current version. We should add exception handler in volume get.

    Change-Id: I5920a3a51b7c8d78f516b947045235ddd78e729c
    Closes-Bug: #1742346

Changed in zun:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/zun 1.0.0

This issue was fixed in the openstack/zun 1.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.