OpenStack Compute (nova)

Server name will all blank spaces should not be allowed via V3 API

Bug #1212096 reported by Christopher Yeoh on 2013-08-14

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Compute (nova)	Fix Released	Undecided	Christopher Yeoh	OpenStack Compute (nova) 2013.2 "havana"

Bug Description

A fix to ensure that all blank spaces for a server name is not allowed was applied to the V2 API (bug 1175956) but was not applied to the V3 API. It should be

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2013-08-14: Fix proposed to nova (master)

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

Changed in nova:
assignee:	nobody → Christopher Yeoh (cyeoh-0)
status:	New → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2013-09-05: Fix merged to nova (master)

Reviewed: https://review.openstack.org/41836
Committed: http://github.com/openstack/nova/commit/f11dc79a6e0cd8133421161d61c0feeb0a03717a
Submitter: Jenkins
Branch: master

commit f11dc79a6e0cd8133421161d61c0feeb0a03717a
Author: Chris Yeoh <email address hidden>
Date: Wed Aug 14 13:40:45 2013 +0930

Fix to disallow server name with all blank spaces (v3 API)

    Prevents a server name to be created, updated or rebuilt with all blank characters.
    A fix for the V2 API was merged in commit 98ff29d13af9e0c1fa96e49e68939634c24ad2c3
    but was not applied to the V3 API.

Fixes bug 1212096

Change-Id: Ibaf0ca7a766b6a279a83f56165edbf8ced29d5fa