Clarify driver load error message
The NoValidDefaultForInterface exception is a little misleading
in that if one doesn't have the base interface enabled, and they
attempt to enable a hardware type which requires or only supports
disabled interfaces, they will also get an exeption. The reality
is we need to suggest for them to look at enabling the interfaces
before looking at the default interface overrides, because logically
the brain jumps to setting a default before checking the interface
settings.
Change-Id: I50d4381e11da96cb7ae0ee8cbda18534380bd471
(cherry picked from commit fdc6424de3
)
This commit is contained in:
parent
badf1eb2aa
commit
fc0f1c951c
|
@ -245,7 +245,8 @@ class NoValidDefaultForInterface(InvalidParameterValue):
|
|||
# because node_info could be an empty string. If node_info
|
||||
# is not empty, it should start with a space.
|
||||
_msg_fmt = _("For%(node_info)s hardware type '%(driver)s', no default "
|
||||
"value found for %(interface_type)s interface.")
|
||||
"value found for %(interface_type)s interface could be "
|
||||
"determined. Please ensure the interfaces are enabled.")
|
||||
|
||||
|
||||
class ImageNotFound(NotFound):
|
||||
|
|
Loading…
Reference in New Issue