Bug 13902 - Add --force option to koha-create and koha-remove commands
Summary: Add --force option to koha-create and koha-remove commands
Status: RESOLVED DUPLICATE of bug 16291
Alias: None
Product: Koha
Classification: Unclassified
Component: Command-line Utilities (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Mason James
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-25 04:32 UTC by Mason James
Modified: 2016-05-18 02:06 UTC (History)
0 users

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mason James 2015-03-25 04:32:00 UTC
Add --force option to koha-create and koha-remove commands
Comment 1 Mason James 2016-04-19 03:55:06 UTC
(In reply to Mason James from comment #0)
> Add --force option to koha-create and koha-remove commands

hmm, i had an interesting experience related to this BZ...


a koha-remove failed to delete a /etc/koha/sites/aaa1 dir, as the dir contained an unexpected foo.backup file

on a reboot, the /etc/init.d/koha-common script then failed to run koha-create-dirs on all other koha instances alphabetically after 'aaa1'

this caused zebrasrv to fail on all following instances?!
Comment 2 Mason James 2016-05-18 02:06:21 UTC
(In reply to Mason James from comment #1)
> (In reply to Mason James from comment #0)
> > Add --force option to koha-create and koha-remove commands
> 
> hmm, i had an interesting experience related to this BZ...
> 
> 
> a koha-remove failed to delete a /etc/koha/sites/aaa1 dir, as the dir
> contained an unexpected foo.backup file
> 
> on a reboot, the /etc/init.d/koha-common script then failed to run
> koha-create-dirs on all other koha instances alphabetically after 'aaa1'
> 
> this caused zebrasrv to fail on all following instances?!

this BZ is basically a dupe of bug 16291
Comment 3 Mason James 2016-05-18 02:06:54 UTC

*** This bug has been marked as a duplicate of bug 16291 ***