yahoo-eng-team team mailing list archive

[Flavio Percoco <1316504@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

glance-manage db_sync silently fails to prepare the database:

# glance-manage db_sync && echo ok
ok

# mysql glance -e "show tables"
+------------------+
| Tables_in_glance |
+------------------+
| migrate_version  |
+------------------+

Steps to Reproduce:
$ glance-manage db_sync && echo ok
Tables "migrate_version" have non utf8 collation, please make sure all tables are CHARSET=utf8
ok

# mysql glance -e "show tables"
+------------------+
| Tables_in_glance |
+------------------+
| migrate_version  |
+------------------+

Expected results:
The glance database should be ready to be used or an error should be clearly reported.

The quick fix for the issue is to set `db_enforce_mysql_charset=False`.
Although this config option will go away in Juno, I think the migration
process should report a proper error and exit w/ an error code.

** Affects: glance
     Importance: Medium
         Status: New

** Changed in: glance
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1316504

Title:
  glance-manage does not print an error on failed db_sync

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  glance-manage db_sync silently fails to prepare the database:

  # glance-manage db_sync && echo ok
  ok

  # mysql glance -e "show tables"
  +------------------+
  | Tables_in_glance |
  +------------------+
  | migrate_version  |
  +------------------+

  Steps to Reproduce:
  $ glance-manage db_sync && echo ok
  Tables "migrate_version" have non utf8 collation, please make sure all tables are CHARSET=utf8
  ok

  # mysql glance -e "show tables"
  +------------------+
  | Tables_in_glance |
  +------------------+
  | migrate_version  |
  +------------------+

  Expected results:
  The glance database should be ready to be used or an error should be clearly reported.

  The quick fix for the issue is to set
  `db_enforce_mysql_charset=False`. Although this config option will go
  away in Juno, I think the migration process should report a proper
  error and exit w/ an error code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1316504/+subscriptions