[RFE] Enable to set Swift as Glance default store

Bug #1234261 reported by Dafna Ron
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Packstack
Won't Fix
Undecided
Unassigned

Bug Description

I have swift configured as glance backend.
when I run packstack again to make changes it changes the field default_store in glance-api.conf back to file and than the images I create are created locally instead of in swift storage servers.
the change I was trying to do is add more zones, replication and storage servers for swift.

reproduce:
1. install swift as an object server using packstack - give it 1 zone, 1 replication and 2 storage servers
2. configure swift as glance default_store.
3. change the fields in the answer file for swift to add more storage servers, more zones and more replication and re-run packstack

the results:

(currently we fail the update - different bug will be opened)

the default_store in glance-api.conf is changed to file by packstack

Revision history for this message
Martin Mágr (mmagr) wrote :

This is not a bug. If you modify config files manually and then re-run packstack, you will have those config files changed as packstack was set to.

Changed in packstack:
status: New → Invalid
Revision history for this message
Dafna Ron (dron-3) wrote :

the whole point of running packstack is that you do not have to change the config files manually - this should be done by packstack.

Changed in packstack:
status: Invalid → New
Revision history for this message
Martin Mágr (mmagr) wrote :

Then you should state exactly what you want to the summary and description.

summary: - default_store in glance-api.conf changes from swift to file when you re-
- run packstack
+ [RFE] Enable to set Swift as Glance default store
Revision history for this message
Ivan Chavero (imcsk8) (ichavero-ichavero) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report got closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce it, please:
* reopen the bug report (set to status "New")
* AND add the steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (TRUNK, TRUNK).
  Valid example: CONFIRMED FOR: TRUNK

Changed in packstack:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.