Pool is connected but Unknown pool

[Tristis Oris]

Nothing was changed with this pool for a long. But today it suddenly became Unknown pool.
It still available via client, everything works as usual.
Before we start try to fix it:

no updates, no reboots.

If migrate VM at client, i can see hostnames and tasks at XO.

-restart toolstack
-restart each host
-remove pool from XO and add again
-change pool master
-updates also installed

but nothing help with it.

hosts:
build 2022-02-11
8.2

XO
xo-server 5.101.0
xo-web 5.102.0
Xen Orchestra, commit 82df6

[olivierlambert]

@Tristis-Oris said in Pool is connected but Unknown pool:

82df6

As usual for XO community, I would first update to latest master commit and rebuild.

[Tristis Oris]

@olivierlambert i'm updated just yesterday evening after newsletter)

now:
xo-server 5.101.0
xo-web 5.102.0
Xen Orchestra, commit d8e01

problem still exist.

[olivierlambert]

Try to re-clone in another folder, rebuild and try again to see if the result is similar. Alternatively, try with an XOA up to date.

[Tristis Oris]

@olivierlambert created new VM, fresh install XO, import config.

commit d8e01

but pool still Unknown.

[olivierlambert]

And with XOA Free?

[Tristis Oris]

@olivierlambert do you mean trial mode? https://xen-orchestra.com/docs/installation.html#xoa not sure, never try it.

[Tristis Oris]

got it.

xo-server 5.80.0
xo-web 5.84.0

pool available, no problem.

[olivierlambert]

No need for a trial, XOA Free 100% up to date will be enough

Please register your XOA to get updates up to the latest version

[Tristis Oris]

@olivierlambert so since it works at XOA, what to do now?
Is it because some difference at codebase?

[olivierlambert]

Your freshly deploy XOA is outdated. You need to register it to be able to download latest updates. Otherwise, it's not relevant to compare both.

[Tristis Oris]

@olivierlambert
Current version: 5.73.1 - XOA build: 20210823

• node: 16.14.2
• npm: 8.12.1
• xen-orchestra-upload-ova: 0.1.4
• xo-server: 5.100.1
• xo-server-telemetry: 0.5.0
• xo-server-xoa: 0.14.0
• xo-web-free: 5.101.1
• xoa-cli: 0.31.0
• xoa-updater: 0.43.1

pool available.

[Tristis Oris]

also i tried to reset configuration on test copy.

    redis-cli
    FLUSHALL
    systemctl restart xo-server.service

then manually add this pool to empty system. Problem still exist.

[olivierlambert]

@Tristis-Oris Okay now try to switch to latest branch (update and retry)

[Tristis Oris]

@olivierlambert
commit 6cbce, again reset DB - pool still unknown.

also i restore XO from backup 27 aug.
Xen Orchestra, commit b89e7
xo-server 5.100.1
xo-web 5.101.1

pool available.
then updated to commit 6cbce > again unknown pool.

[olivierlambert]

1. Try with XOA latest
2. Alternatively, try to find the exact commit that make your failing when you connect.

[Tristis Oris]

@olivierlambert

1. yes, im finally on latest step by step.
   Current version: 5.74.0 - XOA build: 20210823

• node: 16.14.2
• npm: 8.12.1
• xen-orchestra-upload-ova: 0.1.4
• xo-server: 5.101.0
• xo-server-telemetry: 0.5.0
• xo-server-xoa: 0.15.0
• xo-web-free: 5.102.0
• xoa-cli: 0.31.0
• xoa-updater: 0.43.1

pooll is unknown.

2. i restored latest working backup i have. commit c1846, Aug 25.
   so it broken between 25-31 aug.
   any advise how to update for certain commit?

[Tristis Oris]

@olivierlambert got it. we modifed update script from sources to update for certain commit.

problem happens on this one.
https://github.com/vatesfr/xen-orchestra/commit/4dc7575d5bed3851a800840897f1ae3e19f224b8

0 MathieuRA committed to vatesfr/xen-orchestra

feat(xo-web/storage): display SR used for the HA state files (#6384)

Fixes #6339

[olivierlambert]

Thanks. Pinging @julien-f about this

[julien-f]

Thank you for your reports, we have pinpointed the issue and we'll fix it soon

https://github.com/vatesfr/xen-orchestra/pull/6404

MathieuRA opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server): handle unfetched VDIs in pool.$ha_statefiles #6404