[Bug 1301036] Re: openstack.common.db.sqlalchemy.migration utf8 table check issue on initial migration
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: (OperationalError) (1005, "Can't create table 'heat.stack_lock' (errno: 150)") '\nCREATE TABLE stack_lock (\n\tstack_id VARCHAR(36) NOT NULL, \n\tcreated_at DATETIME, \n\tupdated_at DATETIME, \n\tengine_id VARCHAR(36), \n\tPRIMARY KEY (stack_id), \n\tFOREIGN KEY(stack_id) REFERENCES stack (id)\n)ENGINE=InnoDB CHARSET=utf8\n\n' () This happens when there is a foreign key reference from one of these utf8 tables to a latin1 table. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1301036 Title: openstack.common.db.sqlalchemy.migration utf8 table check issue on initial migration To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1301036/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1301036] Re: openstack.common.db.sqlalchemy.migration utf8 table check issue on initial migration
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. https://bugs.launchpad.net/bugs/1301036 Title: openstack.common.db.sqlalchemy.migration utf8 table check issue on initial migration To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1301036/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 570513] Re: NIS-based autofs maps don't load on startup
@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 notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 570513] Re: NIS-based autofs maps don't load on startup
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 stopped rc RUNLEVEL=[2345]) stop on runlevel[!2345] -- NIS-based autofs maps don't load on startup https://bugs.launchpad.net/bugs/570513 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
