Copying final preseed fails to overwrite previous run
Bug #1130901 reported by
Max Brustkern
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| UTAH |
Fix Released
|
Medium
|
Max Brustkern | ||
Bug Description
plars reported an error that occurred here:
http://
It looks to me like if we try to copy to the same output preseed file twice (i.e., in a jenkins job that repeatedly runs on the same physical machine,) we'll copy the file with 644 the first time, and be unable to copy it on subsequent runs as the jenkins user. I think doing a chmod at some point, either before or during the copy, should fix this.
Related branches
lp:~nuclearbob/utah/consolidate-scripts
- Javier Collado (community): Approve
- Max Brustkern (community): Needs Resubmitting
-
Diff: 1559 lines (+257/-849) (has conflicts)19 files modifieddebian/changelog (+11/-0)
debian/utah.manpages (+0/-3)
docs/source/conf.py (+1/-9)
docs/source/man/run_install_test.py.rst (+0/-26)
docs/source/man/run_test_cobbler.py.rst (+0/-26)
docs/source/man/run_test_vm.py.rst (+0/-26)
examples/run_install_test.py (+0/-114)
examples/run_test_bamboo_feeder.py (+0/-119)
examples/run_test_cobbler.py (+0/-127)
examples/run_test_vm.py (+0/-115)
examples/run_utah_tests.py (+146/-57)
tests/test_run.py (+4/-3)
utah/config.py (+28/-9)
utah/provisioning/baremetal/bamboofeeder.py (+7/-10)
utah/provisioning/baremetal/cobbler.py (+2/-2)
utah/provisioning/baremetal/power.py (+3/-3)
utah/provisioning/provisioning.py (+24/-46)
utah/provisioning/vm/vm.py (+14/-31)
utah/run.py (+17/-123)
| Changed in utah: | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Max Brustkern (nuclearbob) |
| Changed in utah: | |
| milestone: | none → 0.12 |
| status: | In Progress → Fix Committed |
| Changed in utah: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
