Skip to content
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

Cant delete default templates "incorrect state" #6124

Closed
ITJamie opened this issue Feb 24, 2022 · 1 comment · Fixed by #6119
Closed

Cant delete default templates "incorrect state" #6124

ITJamie opened this issue Feb 24, 2022 · 1 comment · Fixed by #6119

Comments

@ITJamie
Copy link

ITJamie commented Feb 24, 2022

Describe the bug
Cant delete built-in xcp-ng templates from xoa

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'templates'
  2. select a default template
  3. press delete
  4. See error, goto logs page. see "incorrect state" as error

Expected behavior
default template gets deleted

error log

vm.delete
{
  "id": "79e0da2f-f30f-8ae5-0dc6-08540ed01a24-094706dd-5d22-4830-99b7-c710769c9dcc",
  "forceDeleteDefaultTemplate": true
}
{
  "code": 25,
  "data": {
    "actual": true,
    "expected": false,
    "object": "094706dd-5d22-4830-99b7-c710769c9dcc",
    "property": "isDefaultTemplate"
  },
  "message": "incorrect state",
  "name": "XoError",
  "stack": "XoError: incorrect state
    at incorrectState (/opt/xo/xo-builds/xen-orchestra-202202231631/packages/xo-common/src/api-errors.js:21:32)
    at Xapi.destroy (/opt/xo/xo-builds/xen-orchestra-202202231631/@xen-orchestra/xapi/src/vm.js:298:13)
    at runMicrotasks (<anonymous>)
    at runNextTicks (node:internal/process/task_queues:61:5)
    at processImmediate (node:internal/timers:437:9)
    at process.topLevelDomainCallback (node:domain:152:15)
    at process.callbackTrampoline (node:internal/async_hooks:128:24)
    at Api.callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202202231631/packages/xo-server/src/xo-mixins/api.mjs:307:20)"
} 

Desktop (please complete the following information):

  • Node: v17.6.0
  • xo-server: 5.87.0
  • xo-web: 5.92.0
  • hypervisor: XCP-ng 8.2.0 - fully updated

Additional context
Add any other context about the problem here.

@julien-f
Copy link
Member

Thank you for your report, this is a known issue that will be fixed soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants