Browse Source

site.pp overrides sql_connection for glance-api.conf also

Previously, the sql_connection config was overridden for the
glance-registry.conf only, whereas in the glance-api.conf this
is left to default to a non-existent sqlite DB.

This causes an issue with the v2 API is used - in this case,
the glance-api service accesses the DB directly instead of
delegating to the registry service. Since the sqlite DB is
non-existent, such v2 API calls fail with 500 ServerError.

This is especially problematic with cinder, as it tries the
glance v2 API by default when creating a bootable volume from
an image, see:

  https://bugzilla.redhat.com/888241
tags/2.0.0
Eoghan Glynn 6 years ago
parent
commit
b08af59f34
1 changed files with 1 additions and 0 deletions
  1. 1
    0
      examples/site.pp

+ 1
- 0
examples/site.pp View File

@@ -37,6 +37,7 @@ class role_glance_mysql {
37 37
     keystone_tenant   => 'services',
38 38
     keystone_user     => 'glance',
39 39
     keystone_password => 'glance_password',
40
+    sql_connection    => 'mysql://glance:glance@127.0.0.1/glance',
40 41
   }
41 42
   class { 'glance::backend::file': }
42 43
 

Loading…
Cancel
Save