summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEoghan Glynn <eglynn@redhat.com>2012-12-18 14:01:47 +0000
committerEoghan Glynn <eglynn@redhat.com>2012-12-18 15:22:45 +0000
commitb08af59f34c49daf20ee6a668a6eb5ef22851da7 (patch)
treea5a945a948c2c2f256a3fdf7b96b03a0e5de33c7
parent6f16dc953aaaf4cc8fb29289549e6ca2e899ea65 (diff)
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
-rw-r--r--examples/site.pp1
1 files changed, 1 insertions, 0 deletions
diff --git a/examples/site.pp b/examples/site.pp
index 1f2fda9..acb6782 100644
--- a/examples/site.pp
+++ b/examples/site.pp
@@ -37,6 +37,7 @@ class role_glance_mysql {
37 keystone_tenant => 'services', 37 keystone_tenant => 'services',
38 keystone_user => 'glance', 38 keystone_user => 'glance',
39 keystone_password => 'glance_password', 39 keystone_password => 'glance_password',
40 sql_connection => 'mysql://glance:glance@127.0.0.1/glance',
40 } 41 }
41 class { 'glance::backend::file': } 42 class { 'glance::backend::file': }
42 43