29095499371
80%
master: 79%

Ran 10 Jul 2026 01:18PM UTC

Jobs 1

Files 34

Run time 1min

Badge

Embed ▾

Committed 10 Jul 2026 01:17PM UTC coverage: 80.459%. First build

Build # 29095499371

Build Type

push

github

Committed by

gthvn1

Commit Message

start SM service after dbsync to avoid startup deadlock

message-switch only removes a message from the org.xen.xapi.storage queue once
it has been acked. If we are stuck in a SM call (e.g. DP.destroy that never
returns), restarting the XAPI will fail. The issue is that the message will be
redilevered early when XAPI starts and the call will takes the per-VDI lock
again. When XAPI will try to sync its database, it will call
refresh_local_vdi_activations that will block in stat_vdi because the lock for
the VDI is already taken.

So this patch moves the registers of the queue (Storage_access.start) after the
synchronisation of the XAPI database. Pending messages remains in the queue. Of
course the problem with the VDI is still there but XAPI can now start.

Signed-off-by: Guillaume Thouvenin <guillaume.thouvenin@vates.tech>

Coverage Stats

3504 of 4355 relevant lines covered (80.46%)

0.8 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	python3.11 - 29095499371.1	10 Jul 2026 01:18PM UTC	34	80.46	GitHub Action Run

xcp-ng / xen-api / 29095499371
80%
master: 79%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 29095499371

xcp-ng / xen-api / 29095499371 80% master: 79%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 29095499371

xcp-ng / xen-api / 29095499371
80%
master: 79%

README BADGES
x