[pve-devel] [PATCH-SERIES] correctly handle warnings status

[Fabian Ebner <f.ebner@proxmox.com>]

There's a few places where we use the logic "OK" if and only if no error for a
task status, but this is no longer true now that we also support ending in a
warnings status (not yet used by anything, but the feature is there).

Everything depends on the first patch and depedency bumps for pve-common
are needed across the board.


pve-common:

Fabian Ebner (1):
  tools: add upid_status_is_error function

 src/PVE/Tools.pm | 8 ++++++++
 1 file changed, 8 insertions(+)


pve-manager:

Fabian Ebner (4):
  api/cli: tasks: don't treat warnings status as an error status
  nodes: startall: correctly handle warning status for delayed task
  cli: pveam: remove unused private sub
  cli tools: correctly handle warnings status

 PVE/API2/Nodes.pm  | 2 +-
 PVE/API2/Tasks.pm  | 5 ++++-
 PVE/CLI/pveam.pm   | 6 ------
 PVE/CLI/pveceph.pm | 2 +-
 PVE/CLI/pvenode.pm | 7 +++++--
 PVE/CLI/vzdump.pm  | 2 +-
 6 files changed, 12 insertions(+), 12 deletions(-)


pve-storage:

Fabian Ebner (1):
  api: content: correctly handle warnings status for delayed task

 PVE/API2/Storage/Content.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


pve-container:

Fabian Ebner (1):
  pct: correctly handle warnings task status

 src/PVE/CLI/pct.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


qemu-server:

Fabian Ebner (2):
  cli tools: correctly handle warnings task status
  api: update vm: correctly handle warnings status for delayed task

 PVE/API2/Qemu.pm     | 2 +-
 PVE/CLI/qm.pm        | 2 +-
 PVE/CLI/qmrestore.pm | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

-- 
2.20.1