I'm curious as to why this is happening. When running the initial
Essex/Folsom migrations we explicitly set the default DB schema to use
the UTF8 charset.
What do you see from the output of this query:
SELECT default_character_set_name FROM information_schema.SCHEMATA S
WHERE schema_name = nova;
*** This bug is a duplicate of bug 993663 ***
https://bugs.launchpad.net/bugs/993663
** Changed in: nova
Assignee: (unassigned) = Dan Prince (dan-prince)
** This bug has been marked a duplicate of bug 993663
dns_domains table mysql charset is 'latin1'. Should be 'utf8'
--
You
*** This bug is a duplicate of bug 934276 ***
https://bugs.launchpad.net/bugs/934276
This is a dup of 934427.
https://bugs.launchpad.net/nova/+bug/934276
The should be pretty simple:
+++ b/nova/compute/manager.py
@@ -2244,7 +2244,7 @@ class
** Changed in: nova (Ubuntu)
Assignee: Dan Prince (dan-prince) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/915614
Title:
Add policy.json to packages
To manage
Public bug reported:
Trying to use nova-network on an isolated node... To my surprise I got
errors because dnsmasq and bridge-utils were missing. These are both
used directly by nova-network so we should require them in the
packaging.
** Affects: nova (Ubuntu)
Importance: Undecided
