mirror of
https://github.com/ConvoyPanel/panel.git
synced 2026-04-25 04:35:52 +03:00
[GH-ISSUE #26] Can't delete server after creation #13
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/panel#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @urobasa on GitHub (Jun 2, 2023).
Original GitHub issue: https://github.com/ConvoyPanel/panel/issues/26
The server created in the web interface, it is not created in proxmox
After that, it cannot be removed from the interface and it is impossible to remove the node on which this no-delete server is located.
Api user created, add to variables secret
Is it possible to set up a convoy with an already existing Proxmox cluster, or should the cluster be new with only cluster nodes and no virtual machines?
I am using an existing cluster with previously created virtual machines through the proxmox web interface and I do not see them in the convoy interface.
https://paste.frocdn.com/upuyefapok
@urobasa commented on GitHub (Jun 2, 2023):
version 3.8.1-beta
access.log pveproxy
root@pam!convoy_panel [02/06/2023:22:40:14 +0300] "GET /api2/json/nodes/asusnode0/qemu/853887097/config HTTP/1.1" 500 13
proxmox task - download:debian-11.7.0-amd64-netinst.iso:root@pam!convoy_panel: 6475ECAE OK
successfully
:qmstop:853887097:root@pam!convoy_panel: 6475F038 unable to find configuration file for VM 853887097 on node XXX
@ericwang401 commented on GitHub (Jun 4, 2023):
Please see if updating to the latest version of Convoy resolves this issue
@urobasa commented on GitHub (Jun 7, 2023):
To create a virtual machine in proxmox over panel convoy, a template must exist, the number of which must be specified in the convoy template group.
This information is missing from the documentation.
@ericwang401 commented on GitHub (Jun 7, 2023):
I can't really understand what you are saying. Sorry.
@urobasa commented on GitHub (Jun 7, 2023):
We will wait for the release and clarification of the documentation for use.
close issue