misleading documentation of filesystem_store_metadata_file config opt
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Glance |
Triaged
|
Low
|
Khuong Luu | ||
| glance_store |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
In glance:
The short discussion of the filesystem_
(1) It makes it sound like the location metadata is dynamically pulled from the file and returned in the image-show response for any image. In fact, the way this works is that glance will use the info in the file when it writes the image location--so you will only see this metadata for images created *after* the option has been set.
(2) The example is misleading in that it uses the same UUID for the mountpoint and for the image_id, which I suppose would work, but it makes it look like the two fields are related.
See discussion about this in the glance channel log: http://
In glance_store:
The help text for this option is a bit vague; could stand a rewrite based on the improvements made in the glance docs.
| Changed in glance-store: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in glance: | |
| assignee: | nobody → Khuong Luu (organic-doge) |
| Brian Rosmaita (brian-rosmaita) wrote | #1 |
| OpenStack Infra (hudson-openstack) wrote Fix merged to glance_store (master) | #2 |
| Changed in glance-store: | |
| status: | In Progress → Fix Released |
This was removed from the glance docs in train by Change-Id: I65952f70f0216d
probably because it depends on show_multiple_
The option is still available in glance_store, so that part of the bug is still valid.