@olivierlambert do you know who on XOA side can have a look?

@rvreugde it is really strange... I only have one host on my setup that I'm using for testing and I don't see this behavior... But I see almost every minutes a message in my /var/log/xensource.log saying:
Feb 10 14:55:58 xcp-gthvn1 xapi: [debug||518 HTTPS 10.1.0.100->:::80|host.call_plugin R:dd18d954e8e1|audit] Host.call_plugin host = 'd7f4a210-369a-410e-9c73-4acb59fe5e7c (xcp-gthvn1)'; plugin = 'updater.py' ; fn = 'check_update' args = [ 'hidden' ]
I don't know who is calling this. But for me the file is always released properly. No process that locks the file... Not sure about what to test next. Is there someone on the forum with the same issue?

In fact on my testing host (xcp-ng 8.3) the file is also there. So it looks like it is normal to not delete it. Can you run the command several times? Because on my host even if the file is not deleted I can run the command several times. So I guess that sometimes a process still holds the file and we need to delete it but most of the time the file is just closed and it works.
EDIT: Oh but in fact it looks like by default the update is run by XO so you will see the file that is updated (time is modified each minute on my host). But I'm discovering this plugin and I'm not sure how it is used...

And if you run the command from pool master for pool master you still have an empty list?

xe host-call-plugin host-uuid=20cacce5-ffac-4ace-ac7c-e48f4e6dfc8e plugin=updater.py fn=check_update

Maybe this command must be run from pool master (I'll be surprised...)?

@rvreugde said in Patching XCP-ng via XOA:

xe host-call-plugin host-uuid=20cacce5-ffac-4ace-ac7c-e48f4e6dfc8e plugin=updater.py fn=check_update

Can you try to run the command directly on xcp-080 ?

You can also check if there are some logs in /var/log/updater-plugin.log

Hi,
I don't know this plugin but it looks like at the beginning of the file /etc/xapi.d/plugins/updater.py there is DEFAULT_REPOS = ('xcp-ng-base', 'xcp-ng-updates', 'xcp-ng-linstor') so as new packages are in xcp-ng-updates it should returns a list of new updates.
Maybe for some reason the xcp-ng-updates is not checked by the plugin. To found repos used by the plugin you can try to mimic what the plugins is doing using this piece of python code:

import yum

yum_instance = yum.YumBase()
yum_instance.preconf.debuglevel = 0
yum_instance.preconf.plugins = True
DEFAULT_REPOS = ('xcp-ng-base', 'xcp-ng-updates', 'xcp-ng-linstor')
repos = list(DEFAULT_REPOS)
enabled_repos = yum_instance.repos.listEnabled()
repos = [x.id for x in enabled_repos if x.id in repos]
yum_instance.repos.disableRepo('*')
print("repos checked: {}".format(yum_instance.repos.enableRepo(','.join(repos))))

Do you see xcp-ng-updates in the list of repos checked reported by the script ?

I don't know exactly how it is used in XOA but it looks like it has been merged last week in XO(see https://github.com/vatesfr/xen-orchestra/pull/8144) and I know that Cecile tested it on her setup. So maybe there is a mismatch with the version of XOA you are using?
Otherwise from the point of view of xcp-ng you just need to copy the python file in /etc/xapi.d/plugins/ and there is nothing else to do.

MathieuRA opened this pull request in vatesfr/xen-orchestra

closed feat(xo-server,xo-web/host): replace 2crsi-plugin.py -> ipmitool.py #8144

@stevewest15 Thx for SMlog. I don't see anything suspicious

In the log of the source host I see Oct 14 20:09:06 XCP25 xapi: [error||3 ||storage_migrate] Tapdisk mirroring has failed
Can you also provide /var/log/SMlog that corresponds to the migration time. As it was yesterday maybe you should look in /var/log/SMlog.1
Thx