Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Load Balancer activation results in Cannot read properties #7359

Closed
flibbi2 opened this issue Feb 5, 2024 · 2 comments
Closed

Load Balancer activation results in Cannot read properties #7359

flibbi2 opened this issue Feb 5, 2024 · 2 comments
Assignees

Comments

@flibbi2
Copy link

flibbi2 commented Feb 5, 2024

Are you using XOA or XO from the sources?

XO from the sources

Which release channel?

stable

Provide your commit number

aaffe

Describe the bug

Trying to test load-balancer function in newly created test-cluster.
If I try to use the cluster with no own values filled up, the load-balancer seemed to work. Not sure if it is because the configured limit is not reached or because no value is configured by myself. See screenshots attached.

Error message

Feb  5 17:49:00 xo-ce xo-server[473]: 2024-02-05T17:49:00.003Z xo:load-balancer DEBUG Execute plans!
Feb  5 17:49:00 xo-ce xo-server[473]: 2024-02-05T17:49:00.032Z xo:load-balancer DEBUG performance: Try to optimize Host (bfb023e8-0dd5-4d60-9087-e6a2fdef6d0e).
Feb  5 17:49:00 xo-ce xo-server[473]: 2024-02-05T17:49:00.032Z xo:load-balancer DEBUG performance: Available destinations: 608c17c0-1e2b-4bd1-ada0-65ef59b2678b,e70f1f28-9289-4ba5-9c25-f75e0d69d4b9.
Feb  5 17:49:00 xo-ce xo-server[473]: [WARN] scheduled function: TypeError: Cannot read properties of undefined (reading 'high')
Feb  5 17:49:00 xo-ce xo-server[473]:     at /opt/xo/xo-builds/xen-orchestra-202402051628/packages/xo-server-load-balancer/src/performance-plan.js:181:87
Feb  5 17:49:00 xo-ce xo-server[473]:     at Generator.next (<anonymous>)
Feb  5 17:49:00 xo-ce xo-server[473]:     at asyncGeneratorStep (/opt/xo/xo-builds/xen-orchestra-202402051628/packages/xo-server-load-balancer/src/performance-plan.js:4:42)
Feb  5 17:49:00 xo-ce xo-server[473]:     at _next (/opt/xo/xo-builds/xen-orchestra-202402051628/packages/xo-server-load-balancer/src/performance-plan.js:4:42)
Feb  5 17:49:00 xo-ce xo-server[473]:     at AsyncResource.runInAsyncScope (node:async_hooks:203:9)
Feb  5 17:49:00 xo-ce xo-server[473]:     at cb (/opt/xo/xo-builds/xen-orchestra-202402051628/node_modules/bluebird/js/release/util.js:355:42)
Feb  5 17:49:00 xo-ce xo-server[473]:     at tryCatcher (/opt/xo/xo-builds/xen-orchestra-202402051628/node_modules/bluebird/js/release/util.js:16:23)
Feb  5 17:49:00 xo-ce xo-server[473]:     at Promise._settlePromiseFromHandler (/opt/xo/xo-builds/xen-orchestra-202402051628/node_modules/bluebird/js/release/promise.js:547:31)
Feb  5 17:49:00 xo-ce xo-server[473]:     at Promise._settlePromise (/opt/xo/xo-builds/xen-orchestra-202402051628/node_modules/bluebird/js/release/promise.js:604:18)
Feb  5 17:49:00 xo-ce xo-server[473]:     at Promise._settlePromise0 (/opt/xo/xo-builds/xen-orchestra-202402051628/node_modules/bluebird/js/release/promise.js:649:10)
Feb  5 17:49:00 xo-ce xo-server[473]:     at Promise._settlePromises (/opt/xo/xo-builds/xen-orchestra-202402051628/node_modules/bluebird/js/release/promise.js:729:18)
Feb  5 17:49:00 xo-ce xo-server[473]:     at _drainQueueStep (/opt/xo/xo-builds/xen-orchestra-202402051628/node_modules/bluebird/js/release/async.js:93:12)
Feb  5 17:49:00 xo-ce xo-server[473]:     at _drainQueue (/opt/xo/xo-builds/xen-orchestra-202402051628/node_modules/bluebird/js/release/async.js:86:9)
Feb  5 17:49:00 xo-ce xo-server[473]:     at Async._drainQueues (/opt/xo/xo-builds/xen-orchestra-202402051628/node_modules/bluebird/js/release/async.js:102:5)
Feb  5 17:49:00 xo-ce xo-server[473]:     at Immediate.Async.drainQueues [as _onImmediate] (/opt/xo/xo-builds/xen-orchestra-202402051628/node_modules/bluebird/js/release/async.js:15:14)
Feb  5 17:49:00 xo-ce xo-server[473]:     at processImmediate (node:internal/timers:476:21)
Feb  5 17:49:00 xo-ce xo-server[473]:     at process.callbackTrampoline (node:internal/async_hooks:128:17)
Feb  5 17:49:26 xo-ce systemd[1]: Started Checkmk agent (PID 461/UID 998).

To reproduce

Set values and fill up host. Setup loadbalancer to performance mode.

Expected behavior

Migrate VMs

Screenshots

grafik grafik

Node

18.19.0

Hypervisor

xcp-ng 8.2.1

Additional context

No response

@olivierlambert
Copy link
Member

Hi @flibbi2

I see you closed the issue, is that on purpose?

@flibbi2 flibbi2 reopened this Feb 5, 2024
@flibbi2
Copy link
Author

flibbi2 commented Feb 5, 2024

I thought it was a configuration failure, but unfortunately the issue is still there, so I've reopened the issue. So it's still on purpose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants