cancelling `chef-server-ctl cleanse --with-external` still acts on external sources
Open
Nobody has claimed this yet.
Status: Consider for next release
Status: move to jira
Status: To be prioritized
Triage: Confirmed
Type: Bug
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
Running chef-server-ctl cleanse --with-external and then typing CTRL-C will proceed to attempt cleanse the external solr and postgresql data.
It should actually abort.
This is with 12.14.0. I have not tested other versions.
# chef-server-ctl cleanse --with-external
*******************************************************************
* * * * * * * * * * * STOP AND READ * * * * * * * * * *
*******************************************************************
This command will delete *all* local configuration, log, and
variable data associated with Chef Server.
This will also delete externally hosted Chef Server data.
This means that any service you have configured as 'external'
will have any Chef Server permanently deleted.
You have 60 seconds to hit CTRL-C before configuration,
logs, local, and remote data for this application are permanently
deleted.
*******************************************************************
^C
Deleting data from external service: opscode-solr4
Cleansing data in a remote Sol4 instance is not currently supported.
Deleting data from external service: postgresql
Chef Server databases and roles have been successsfully deleted from your_database.rds.amazonaws.com
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the chef-server-ctl cleanse --with-external command and trace how CTRL-C is handled before external Solr and PostgreSQL cleanup begins. Reproduce the 12.14.0 behavior with external services configured, then verify cancellation stops all cleanup rather than deleting external data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang, postgresql
- Domain
- backend, cli, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100