Project

General

Profile

Actions

Bug #37885

open

Proxmox Plugin: "HTTP/1.1 500 storage 'data' is not available on node 'prox01'\r\n"

Added by Mattia Libera 7 months ago. Updated 7 months ago.

Status:
New
Priority:
Urgent
Assignee:
-
Category:
Compute resources
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Today I updated Foreman from 3.9.0 to 3.12.0 (following these steps: 3.9.0>3.9.3>3.10>3.11>3.12)

If I try to create/edit/clone or any other option related to vm on Proxmox, Foreman returns the following error:
Oops, we're sorry but something went wrong Expected([200]) <=> Actual(500 InternalServerError) excon.error.response :body => "{\"data\":null}" ... ... ... :method => "GET" :omit_default_port => false :path => "/api2/json//nodes/prox01/storage/data/content" :port => 8006 :query => "" :reason_phrase => "storage 'data' is not available on node 'prox01'" :remote_ip => "10.11.1.70" :scheme => "https" :status => 500 :status_line => "HTTP/1.1 500 storage 'data' is not available on node 'prox01'\r\n"

'data' storage is defined only on prox02 node and not on prox01. So of course when it asks for "data" content to prox01 node it doesn't exists and it get a 500 error.

Everything worked fine in 3.9.0. The related Proxmox API seems to be the same: https://pve.proxmox.com/pve-docs/api-viewer/index.html#/nodes/{node}/storage

I attach the output of:
- foreman-rake errors:fetch_log request_id=028ecfe7
- foreman-debug


Files

request_id_028ecfe7.log request_id_028ecfe7.log 32.4 KB Mattia Libera, 10/06/2024 06:43 PM
foreman-debug-ZUYzv.tar.xz foreman-debug-ZUYzv.tar.xz 1.05 MB Mattia Libera, 10/06/2024 06:47 PM
Actions

Also available in: Atom PDF