glance-registry searches for [pipeline:glance-registry-<FLAVOR>]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Won't Fix
|
Undecided
|
Sana Khan |
Bug Description
Depending on what's in the flavor directive of /etc/glance/
If this is a feature, then the default configuration file should be updated to handle all values of the flavor directive.
If it's a bug (eg: regression) and that glance-registry is searching for the wrong section, then this should be corrected.
In the mean while, I'm patching the default configuration file in my Debian package to add the below lines to glance-
[pipeline:
pipeline = osprofiler unauthenticated
[pipeline:
pipeline = osprofiler unauthenticated
[pipeline:
pipeline = osprofiler unauthenticated
[pipeline:
pipeline = osprofiler unauthenticated
[pipeline:
pipeline = osprofiler unauthenticated
Without this, glance-registry may refuse to start by default, which is really annoying.
Changed in glance: | |
assignee: | nobody → Sana Khan (sana.khan) |
Looks like we're missing some values in the default file. This is expected behavior for what the operator wants to achieve with their configuration. But let's keep this bug open for some updates to the sample file in etc/ of the glance source tree.