Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Power Supply max power draw is posted as 0

See original GitHub issue

Hey, I have a Dell R740XD inventory file, that when I try to sync, the script for some reason tries to put ‘0’ as maximum power draw, which Netbox does not permit.

2022-10-06 14:17:23,617 - INFO: Updating NetBox 'power port' object 'PS' with data: {'maximum_draw': 0, 'tags': [{'name': 'NetBox-synced'}, {'name': 'Source: my-redfish-example'}], 'custom_fields': {'firmware': '0.00', 'health': 'OK'}}
2022-10-06 14:17:23,617 - DEBUG2: Sending PATCH to 'https://netbox-stage.example.net/api/dcim/power-ports/803/' with data 'b'{"maximum_draw": 0, "tags": [{"name": "NetBox-synced"}, {"name": "Source: my-redfish-example"}], "custom_fields": {"firmware": "0.00", "health": "OK"}}''.
2022-10-06 14:17:24,981 - DEBUG2: Received HTTP Status 400.
2022-10-06 14:17:24,982 - ERROR: NetBox returned: PATCH /api/dcim/power-ports/803/ Bad Request
2022-10-06 14:17:24,982 - ERROR: NetBox returned body: {'maximum_draw': ['Ensure this value is greater than or equal to 1.']}
2022-10-06 14:17:24,982 - ERROR: Request Failed for power port. Used data: {'maximum_draw': 0, 'tags': [{'name': 'NetBox-synced'}, {'name': 'Source: my-redfish-example'}], 'custom_fields': {'firmware': '0.00', 'health': 'OK'}}

The inventory file seems to have the right fields for it:

[...]
"power_supply":[
         {
            "bay":1,
            "capacity_in_watt":800,
            "chassi_ids":[
               1
            ],
            "firmware":"1.00",
            "health_status":"OK",
            "id":"0",
            "input_voltage":229,
            "last_power_output":95,
            "model":"865414-B21",
            "name":"HpeServerPowerSupply",
            "operation_status":"Enabled",
            "part_number":"866730-001",
            "serial":"5WBXU0BLLAV6YM",
            "type":"AC",
            "vendor":"LTEON"
         },
         {
            "bay":2,
            "capacity_in_watt":800,
            "chassi_ids":[
               1
            ],
            "firmware":"1.00",
            "health_status":"OK",
            "id":"1",
            "input_voltage":229,
            "last_power_output":77,
            "model":"865414-B21",
            "name":"HpeServerPowerSupply",
            "operation_status":"Enabled",
            "part_number":"866730-001",
            "serial":"5WBXU0BLLAV6ND",
            "type":"AC",
            "vendor":"LTEON"
         }
      ],
[...]

Netbox v3.2.7, Script latest development- and main-branch

Issue Analytics

State:
Created a year ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

Eldiabolo21commented, Oct 18, 2022

Thank you, this issue is fixed!

0reactions

Eldiabolo21commented, Oct 17, 2022

I can’t really say, as this seem to be more a symptom than the real problem. As I wrote before, the script went through and the power supply issues weren’t a problem any more, when I added the correct serial number to netbox. This leads me to belive there is something wrong with the mechanism of mapping the inventory ID.