OpenStack Compute (nova)

connection_type flag ERROR should be warning

Bug #1011788 reported by Dan Prince on 2012-06-11

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Compute (nova)	Fix Released	Low	Dan Prince	OpenStack Compute (nova) 2012.2 "folsom"

When you use connection_type in nova.conf you now get this:

Line 1 : 2012-06-11 19:02:50 ERROR nova.virt.connection [-] Specifying virt driver via connection_type is deprecated

Deprecation log messages are typically warnings instead of errors.

Dan Prince (dan-prince) on 2012-06-11

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2012-06-11: Fix proposed to nova (master)

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

Revision history for this message

Sean Dague (sdague) wrote on 2012-06-12:

I'm working on a nova.common decorator for deprecation, maybe we can work on levels over there?

I was concerned that WARNING wasn't going to be strong enough for people to realize it's going to get removed as soon as Folsom releases.

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2012-06-13: Fix merged to nova (master)

commit f03b728989673d06f49e349a23b9ad2ffc66753e
Author: Dan Prince <email address hidden>
Date: Mon Jun 11 15:08:32 2012 -0400

Log connection_type deprecation message as WARNING

Updates the connection_type log messages to log as
a warning instead of an error.

Change-Id: I4cc2d9d5fdea2c8871f760b73a905fe61edcbe8f

Changed in nova:
status:	In Progress → Fix Committed

Thierry Carrez (ttx) on 2012-07-04

Thierry Carrez (ttx) on 2012-09-27

Changed in nova:
milestone:	folsom-2 → 2012.2

This report contains Public information

Everyone can see this information.

You are

Subscribing...

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