-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failure trying to expunge two external IP zones #7305
Comments
I ran into a similar issue over the weekend. I got into this situation after expunging two disks on a certain sled but forgot to regenerate/enable a new blueprint in between the two expunge-disk actions. It's a user error but it's also a sharp edge since the error was irrecoverable:
Here is what I captured from crdb at the time (on london but the data is already wiped):
|
I think (?) this is a different problem; at least, the error from |
To confirm: I'm 99% sure the original issue here is a bug in reconfigurator-cli only (details in #7307 (comment)), whereas what you saw on london was presumably not going through reconfigurator-cli at all? |
Continuing from #7304, where I had a freshly installed a4x2 system and expunged an external DNS zone: I then generated a new blueprint (which added a new zone to get the count back up), executed it (which worked), and then tried to expunge it, but it failed with:
Here are the full steps:
The text was updated successfully, but these errors were encountered: