Bug #87
Do not allow VPS setup script to proceed if VPS already exists
Status: | Closed | Start: | 2011-09-28 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assigned to: | - | % Done: | 0% |
|
Category: | - | |||
Target version: | - | |||
Votes: | 0 |
Description
A (non-customer-facing) VPS setup script currently will proceed to overwrite an existing VPS with new VPS filesystem and config if given the name of an existing VPS. This is probably not intentional, and there's no way to recover from it. It shouldn't be allowed to happen unless really really really sure.
History
Updated by admin over 13 years ago
- Tracker changed from Feature to Bug
Updated by admin over 13 years ago
- Status changed from New to Resolved
It's no longer possible to overwrite an existing VPS disk or deploy config to an active VPS without using --force.
Updated by admin almost 13 years ago
- Status changed from Resolved to Closed