ConvoyPanel/panel v4.7.0-rc.3

on GitHub

Added

• A server whose installation failed can now be retried. The "Install failed" screen was a dead end that only said to
  contact an administrator; it now offers the reinstall form, and the API accepts a reinstall for a server in that
  state. Every other blocked state, such as suspended, still refuses it.
• The "Installing", "Restoring Backup" and "Restoring Snapshot" screens now update by themselves. They check the
  server every few seconds and move on once the work is done, with a spinning icon to show they're live; before, they
  stayed put until the page was refreshed.

Changed

• Deleting a server and keeping its virtual machine are now separate actions. Delete always removes everything --
  backups (including locked ones), the virtual machine on the node, and the server's entry in Convoy -- and when the
  virtual machine is already gone from the node, it simply removes the Convoy entry. Disconnect, a new button next
  to it, replaces the "Do not purge VM and related files" checkbox: it removes the server from Convoy and leaves the
  virtual machine and its backups on the node. The API is unchanged; DELETE with no_purge still disconnects.

Fixed

• Fixed reinstalling a server while its node couldn't be reached being taken as "there's no VM": the reinstall then
  skipped removing the old VM and failed later on its taken VMID. It now fails straight away with the node's error, so
  it can just be retried.
• Fixed every error from Proxmox filling the log with three copies of the same stack trace -- about 256 lines per error,
  every few seconds while a page polled a server whose VM was gone. An error is now logged once, with one trace, and its
  message is Proxmox's own ("Proxmox returned 500: Configuration file ... does not exist").
• Fixed reinstalling a server whose VM no longer exists failing every time. Reinstall stopped and deleted the old VM
  first, and Proxmox answers both with "does not exist" when a previous install died before or during the clone. It
  now skips straight to building when there is no VM.
• Fixed a failed reinstall of an already-failed server staying on "Installing" forever instead of going back to
  "Install failed". The failure handler wrote through the copy of the server captured when the reinstall started, and
  when that copy already read "install_failed" the write was skipped as a no-op.
• Fixed deleting a server failing, over and over, when its virtual machine was already gone from the node or it had a
  locked backup. A failed delete can now also be retried, or the server disconnected, straight from the "Failed to
  Delete" screen, and a server stuck on "Deleting" can be disconnected.
• Fixed a delete treating any error from Proxmox as "the virtual machine is gone". Only Proxmox's own "does not exist"
  counts now, so a node that is briefly unreachable can no longer get a server removed from Convoy while its virtual
  machine keeps running.
• Fixed a server's jobs getting permanently stuck after one slow request to Proxmox. The locks that keep two jobs of the
  same kind from running on a server at once never expired, so a job the queue killed for running past its time limit
  left its lock behind for good: every later job of that kind for the server -- including the force-stop that reinstall
  and delete start with -- failed instantly until the lock was cleared from Redis by hand. Locks now expire shortly
  after their job's time limit, a job that finds one held waits and retries, and the power and password jobs' time
  limits no longer fall below a single Proxmox request.
• Fixed failing jobs retrying with no pause. A job whose request to Proxmox failed was retried at once, again and
  again, until it ran out of time -- thousands of requests a minute against a node that was already struggling. Jobs
  now wait a few seconds, then longer, between retries.
• Fixed opening a server that has been deleted showing "Something went wrong" with "No query results for model
  [Convoy\Models\Server]". It now shows "Server not found" with a way back to the server list, and the API names a
  missing record in plain words ("This server could not be found. It may have been deleted."). Deleted nodes and users
  in the admin area, which used to break the page outright, now get the same screen.

SHA256 Checksum

bb6eeedc6d01b2ad69f6631ea8546f7f56a449f16bd6c32fe3b2cb926f7d75db  panel.tar.gz