** Changed in: cloud-init
Status: Confirmed => Fix Committed
** Changed in: cloud-init
Status: Fix Committed => Confirmed
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Glance was tracking this in
https://bugs.launchpad.net/glance/+bug/1279000
** Changed in: glance
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
I looked at whether or not we could port the change from Glance into Heat, but
it turns out that's not going to be easy: because Heat from Havana - Icehouse
creates several new tables, all explicitly set to utf8, these upgrade steps
will fail with an error along the lines of:
ERROR:
Glance was tracking this in
https://bugs.launchpad.net/glance/+bug/1279000
** Changed in: glance
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301036
Title:
I looked at whether or not we could port the change from Glance into Heat, but
it turns out that's not going to be easy: because Heat from Havana - Icehouse
creates several new tables, all explicitly set to utf8, these upgrade steps
will fail with an error along the lines of:
ERROR:
Even with https://review.openstack.org/#/c/75356/ merged into glance,
glance master will still fail with the original error if it encounters a
non-utf8 database, because it calls db_sync with without modifying the
default sanity_check=True. So we either need an option to set
sanity_check=False
Ben: Ah, thanks, I missed that. Is there a similar fix for keystone?
Keystone has the same utf8 check, but does not yet appear to have merged
(or have pending) the changes to make it optional and to expose that to
the -manage command.
--
You received this bug notification because you are a
@Dern: That's correct, anything started out of /etc/init.d will start up
before autofs with this configuration. My solution is really just a
hack to work around the fundamental problem.
--
NIS-based autofs maps don't load on startup
https://bugs.launchpad.net/bugs/570513
You received this bug
@Dern: That's correct, anything started out of /etc/init.d will start up
before autofs with this configuration. My solution is really just a
hack to work around the fundamental problem.
--
NIS-based autofs maps don't load on startup
https://bugs.launchpad.net/bugs/570513
You received this bug
I'm also hitting this problem. Obviously the correct solution is to
move nis to use upstart and then make autofs depend on nis being up. In
the interim, I've modified autofs.conf to wait for the rc process to
finish:
start on (filesystem
and net-device-up IFACE!=lo
and
I'm also hitting this problem. Obviously the correct solution is to
move nis to use upstart and then make autofs depend on nis being up. In
the interim, I've modified autofs.conf to wait for the rc process to
finish:
start on (filesystem
and net-device-up IFACE!=lo
and
11 matches
Mail list logo
