Netbox plugin: Error code 400 - Error: Bad Request

mavoff

@sorry Olivier I'm not sure what you mean by isolate the dependency so I won't be able to use fuse for mounts?
Has the arm fix branch been merged?

olivierlambert

I mean to remove the dep/package so you can build. The branch is not rebased on master since 1093 commits. You can try to do it by yourself and see if you can build after rebasing it.

About merging it: sadly, we do not have the resources to check/investigate and solve build issue on any other platform than x86 at the moment. I prepared a Arm instance for Florent last year, but we have many other things with a higher priority right now. However, contributions are welcome

mavoff

@olivierlambert as you know I'm not a developer and cannot contribute with code or fixes.
Thanks...

mavoff

Screenshot 2023-10-24 at 10.45.12.png

XO up to date now

plugin.test
{
  "id": "netbox"
}
{
  "originalUrl": "https://fw-dea12.domain.tld:8143/api/extras/custom-fields/",
  "url": "https://fw-dea12.domain.tld:8143/api/extras/custom-fields/",
  "data": {
    "method": "GET",
    "path": "/extras/custom-fields/"
  },
  "message": "400 Bad Request",
  "name": "Error",
  "stack": "Error: 400 Bad Request
    at Object.assertSuccess (/opt/xen-orchestra/node_modules/http-request-plus/index.js:162:19)
    at httpRequestPlus (/opt/xen-orchestra/node_modules/http-request-plus/index.js:217:22)
    at httpRequest (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:146:26)
    at Netbox.#request (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:183:18)
    at Netbox.#checkCustomFields (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:203:26)
    at Netbox.test (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:106:5)
    at default.testPlugin (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/plugins.mjs:285:5)
    at Xo.test (file:///opt/xen-orchestra/packages/xo-server/src/api/plugin.mjs:109:3)
    at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:417:20)"
}

Still giving the same 400 bad request error

Danp

@maverick said in Netbox plugin: Error code 400 - Error: Bad Request:

XO up to date now

Something appears to be wrong because the version of xo=server is way off (should be 5.124.0)

pdonias

Nice catch @Danp
@maverick, maybe you forgot to restart xo-server?

mavoff

@pdonias thank you for your reply.

I restarted the whole server before actually testing.

the screenshot above was immediately after the build but before the reboot. Was focused on the commit.
Then rebooted, tested, error.

Screenshot 2023-10-24 at 14.58.03.png

olivierlambert

Okay so now at least you are on a right build

pdonias

@maverick What version of the Netbox plugin do you see in the UI? (/#/settings/plugins?s=netbox)

mavoff

@pdonias said in Netbox plugin: Error code 400 - Error: Bad Request:

/#/settings/plugins?s=netbox

Netbox 1.3.0

pdonias

@maverick Thanks, that seems correct. So you're getting the exact same error as before when you test the plugin? Now that you're up-to-date, you should get more information in the full error log.

mavoff

@pdonias

Hi there and thank you for your reply.
Well, the error messages aren't exactly equal so to say.

In the image below you can see the result of testing before the XO update was completed (namely the Oct 24 11:11 test was made after update BEFORE reboot/xo restart and 11:16 was after).
So the error message does change slightly.

Screenshot 2023-10-25 at 11.19.14.png

Oct 24, 11:11

plugin.test
{
  "id": "netbox"
}
{
  "code": 400,
  "url": "https://fw-dea12.domain.tld:8143/api/virtualization/cluster-types/",
  "data": {
    "method": "POST",
    "path": "/virtualization/cluster-types/",
    "body": {
      "name": "[TMP] Xen Orchestra Netbox plugin test - 5qz91pafh",
      "slug": "xo-test-5qz91pafh",
      "description": "This type has been created by Xen Orchestra's Netbox plugin test. If it hasn't been properly deleted, you may delete it manually."
    }
  },
  "message": "Bad Request",
  "name": "Error",
  "stack": "Error: Bad Request
    at onResponse (/opt/xen-orchestra/node_modules/http-request-plus/index.js:255:21)
    at AsyncResource.runInAsyncScope (node:async_hooks:199:9)
    at cb (/opt/xen-orchestra/node_modules/bluebird/js/release/util.js:355:42)
    at tryCatcher (/opt/xen-orchestra/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (node:internal/timers:464:21)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

And Oct 24, 11:16:

plugin.test
{
  "id": "netbox"
}
{
  "originalUrl": "https://fw-dea12.domain.tld:8143/api/extras/custom-fields/",
  "url": "https://fw-dea12.domain.tld:8143/api/extras/custom-fields/",
  "data": {
    "method": "GET",
    "path": "/extras/custom-fields/"
  },
  "message": "400 Bad Request",
  "name": "Error",
  "stack": "Error: 400 Bad Request
    at Object.assertSuccess (/opt/xen-orchestra/node_modules/http-request-plus/index.js:162:19)
    at httpRequestPlus (/opt/xen-orchestra/node_modules/http-request-plus/index.js:217:22)
    at httpRequest (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:146:26)
    at Netbox.#request (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:183:18)
    at Netbox.#checkCustomFields (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:203:26)
    at Netbox.test (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:106:5)
    at default.testPlugin (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/plugins.mjs:285:5)
    at Xo.test (file:///opt/xen-orchestra/packages/xo-server/src/api/plugin.mjs:109:3)
    at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:417:20)"
}

pdonias

@maverick It's weird because the error log should have more fields. Are you able to access this URL from a browser where you're logged in your Netbox? https://fw-dea12.domain.tld:8143/api/extras/custom-fields/

mavoff

@pdonias hi there sorry for the late reply.

If I open said link on the browser I get: Screenshot 2023-10-26 at 16.54.47.png

pdonias

@maverick Please make sure that you're logged in by going to https://fw-dea12.domain.tld:8143/ first.

mavoff

@pdonias

Just to say that yes the link is accessible.

HTTP 200 OK
Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "count": 1,
    "next": null,
    "previous": null,
    "results": [
        {
            "id": 1,
            "url": "https://fw-dea12.domain.tld/api/extras/custom-fields/1/",
            "display": "UUID",
            "content_types": [
                "virtualization.cluster",
                "virtualization.virtualmachine",
                "virtualization.vminterface"
            ],
            "type": {
                "value": "longtext",
                "label": "Text (long)"
            },
            "object_type": null,
            "data_type": "string",
            "name": "uuid",
            "label": "UUID",
            "group_name": "",
            "description": "Object UUID",
            "required": false,
            "search_weight": 1000,
            "filter_logic": {
                "value": "exact",
                "label": "Exact"
            },
            "ui_visibility": {
                "value": "read-write",
                "label": "Read/Write"
            },
            "default": null,
            "weight": 100,
            "validation_minimum": null,
            "validation_maximum": null,
            "validation_regex": "",
            "choices": [],
            "created": "2023-10-17T12:20:53.892582Z",
            "last_updated": "2023-10-17T12:21:47.628430Z"
        }
    ]
}

Logged in

pdonias

@maverick This is for the URL https://fw-dea12.domain.tld/api/extras/custom-fields/1/, right? What about https://fw-dea12.domain.tld/api/extras/custom-fields/?

If that works too, could you run this from the machine that hosts your XO?
Replace <TOKEN> with the token that you put in the Netbox plugin configuration:

curl -skv -H "Content-Type: application/json" -H "Authorization: Token <TOKEN>" "https://fw-dea12.domain.tld/api/extras/custom-fields/"

mavoff

@pdonias ok I get a correct answer from inside but from outside I'm getting this bad request. The curl gets to the ssl certificate on the net box host, but throws the 400 bad request, when doing from outside the firewall.

When testing locally, it works.

Let me look this over! Thanks!