XOA build: unknown

Forza

Hi, Is it normal that XOA says "XOA build: unknown" in the updater?

- node: 12.16.2
- npm: 4.6.1
- xen-orchestra-upload-ova: 0.1.3
- xo-server: 5.59.0
- xo-server-auth-github-enterprise: 0.2.2
- xo-server-auth-google-enterprise: 0.2.2
- xo-server-auth-ldap-enterprise: 0.7.1
- xo-server-auth-saml-enterprise: 0.8.0
- xo-server-backup-reports-enterprise: 0.16.5
- xo-server-telemetry: 0.2.1
- xo-server-transport-email-enterprise: 0.5.0
- xo-server-transport-icinga2-enterprise: 0.1.1
- xo-server-transport-nagios-enterprise: 0.1.1
- xo-server-transport-slack-enterprise: 0.0.0
- xo-server-transport-xmpp-enterprise: 0.1.1
- xo-server-usage-report-enterprise: 0.7.5
- xo-server-xoa: 0.7.0
- xo-web-enterprise: 5.59.0
- xoa-cli: 0.19.0
- xoa-updater: 0.26.0

olivierlambert

This is "normal" if you don't have a latest XOA appliance But it's not a big deal.

Forza

@olivierlambert Do you mean the "Release channel"? I am on "latest" channel.

olivierlambert

No I meant literally "XOA appliance", the whole virtual machine. We update it sometimes You can redeploy it and import config from your current one.

Forza

@olivierlambert Oh, hm. Does it not update itself?

olivierlambert

No. It's on the "OS side" and different than XO program itself. Upgrading an OS directly will lead to various issues (on some deps, eg Redis).

So don't bother about this message or deploy a fresh XOA.

Forza

No Problem. Thanks! Is there a RSS or notification on new XOA releases. Might be worth updating now and then?

olivierlambert

In general, we communicate about new XOA during a new XO release, if it's important to upgrade. Keep an eye on blog posts

Forza

Will do. Just checked on my login on https://xen-orchestra.com/ and there is no version information on the download. XOA is just mentioned like this "Filename: "xoa_unified.xva" Md5sum: 9f6dbcc31f79e1bb700a1ca2b5b4e453". Perhaps add a release date and version number here?

olivierlambert

The information is visible in the build number you have in your XO section. The build number will be visible in the latest appliance once deployed.

Because it's not mandatory to use the last one, we don't track it.

As I said, it's not a problem to update it until we ask people to change it