UnknownScheme exception should be caught
Bug #1379308 reported by
Stuart McLaren
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Glance |
Fix Released
|
Medium
|
Stuart McLaren | ||
Bug Description
In glance/
| Changed in glance: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| assignee: | nobody → Stuart McLaren (stuart-mclaren) |
| Changed in glance: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to glance (master) | #1 |
| Changed in glance: | |
| status: | In Progress → Fix Committed |
| Changed in glance: | |
| milestone: | none → kilo-rc1 |
| status: | Fix Committed → Fix Released |
| Changed in glance: | |
| milestone: | kilo-rc1 → 2015.1.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit d88b4b6d56dd6a2
Author: Stuart McLaren <email address hidden>
Date: Thu Oct 9 12:23:21 2014 +0000
Catch UnknownScheme exception
There are a couple of places where an UnknownScheme
exception could be raises but was not being caught.
Change-Id: I25af9a762c49a1
Closes-bug: #1379308