'-k' option fails when re-installing because of changed config files
Bug #960611 reported by
Gunther
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| anvil |
Won't Fix
|
Medium
|
Joshua Harlow | ||
Bug Description
When using the '-k' option all the packages and git repos stay around which is a good thing. However, when re-installing (same target dir) the install fails because of changed config files (keystone.conf). The error message is to 'commit or stash changes'
Revision history for this message
| Joshua Harlow (harlowja) wrote | #1 |
Revision history for this message
| Joshua Harlow (harlowja) wrote | #2 |
Revision history for this message
| Doug Hellmann (doug-hellmann) wrote | #3 |
| Changed in devstackpy: | |
| assignee: | nobody → Joshua Harlow (harlowja) |
| Changed in devstackpy: | |
| status: | New → Fix Committed |
| Changed in anvil: | |
| status: | Fix Committed → Won't Fix |
To post a comment you must log in.
Possible fixes.
1. Stop placing config files in the checkout dirs.
2. When in downloading git, if the dir already exists, just leave it alone instead of trying to git pull from master...
3. Run a stash, pull, and then unstash
Issue #2 means that you might never get the latests