orchestrator.ini.sample should not bet tracked in git
Bug #1535889 reported by
Adam Gandelman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Astara |
Fix Released
|
Low
|
Adam Gandelman |
Bug Description
Running 'tox -e genconfig' produces different output every time its run. it appears that the ordering of things in the config sample changes on every run, causing lots of confusing changes everytime its generated. Ideally, it should produce the same sample every time it is run (provided actual config options do not change) I've tried setting PYTHONHASHSEED=0 hoping that might help, but it doesn't.
test:
git clone https:/
cd astara
tox -e genconfig
cp etc/orchestrato
tox -e genconfig
diff /tmp/1 etc/orchestrato
Changed in astara: | |
importance: | Undecided → Medium |
Changed in astara: | |
milestone: | none → mitaka-2 |
status: | New → Incomplete |
status: | Incomplete → In Progress |
Changed in astara: | |
assignee: | nobody → xiayu (1013230155-v) |
assignee: | xiayu (1013230155-v) → nobody |
summary: |
- config sample generation is non-deterministic + orchestrator.ini.sample should not bet racked in git |
summary: |
- orchestrator.ini.sample should not bet racked in git + orchestrator.ini.sample should not bet tracked in git |
Changed in astara: | |
assignee: | nobody → Adam Gandelman (gandelman-a) |
importance: | Medium → Low |
To post a comment you must log in.
OK so this isn't specific to astara. The thing that is specific, is that we're tracking the sample in git. We should probably drop it from git, ship an orchestrator.ini that gets updated at release time, and have devstack plugin generate config sample and use that as part of gating. some of this was originally proposed by xiayu and I -1d it, so apologies for that!