XCP-ng 8.3 betas and RCs feedback 🚀

alex821982

@BenjiReis
Thanks )
But we really have already put 8.2 from iso on it with included fixes, which we gave in another topic.
Therefore, there is no way to check now.
While it was 8.3, I managed to conduct some tests.
Did I understand something wrong or is it quite possible that in some tasks 8.3 is significantly faster on the same hardware than 8.2?

Finallf

New installer and final screen out of sync.

I'm testing 8.3 and the only thing I noticed was when installing it on the LG Flatron w2043s monitor, the image is lost in some stages, the monitor complains that it's out of sync, with the wrong hz.

It is possible to install normally, but the screen is small and located on the straight/low side and not in the center.
Sometimes the final screen with the xcp-ng server information appears, other times the monitor says it is out of sync/wrong hz.

Tested with another monitor of the same model and the error persists.
I believe it is Hz above what the monitor supports.

stormi

@Finallf Have you tried the safe boot option?

ThierryC01

I have upgraded from Xcp-ng 8.2 to 8.3 Beta, performed all patches via XOA. I can connect via ssh and on the XOA host console with the same root password but on the host console, the root password is refused!! Why is that? I need to remap my ISO repository that I can browse in XOA but cannot remap in XOA which is inconvenient by the way but... root password is refused on the main console. That does not make any sense.

ThierryC01

@ThierryC01 Well, it happened that there was some kind of keyboard mismatch. Anyway, why can't we choose or even create a local ISO repository? I will have to dig in and play to mount the already existing local disk containing my ISO files into a folder.

ThierryC01

After upgrading to 8.3. from 8.2, all backups have disappeared, I wanted to restore one VM but nothing is displayed at all. Even after importing the config file from 8.2, it is impossible to restore anything. There is not even a way to browse and direct the system to the location of previous backup files.

stormi

Where were the backups stored? The upgrade doesn't overwrite anything but the system partitions.

ThierryC01

@stormi My backups are stored on a remote SMB share.

ThierryC01

How can we re-attach an existing local SR that cannot be seen by the system? All my ISO files are local (/dev/sdb4) with no way to store them anywhere else.

Xcp-ng attach.png

florent

@ThierryC01 Can you browse the samba mount and check if the data are still there ?
The remote should have a xo-vm-backups folder containing one folder per VM

stormi

Regarding the local ISO SR, you need to mount /dev/sdb4 into a directory named the same as what you had done before the upgrade. The XAPI database should still have knowledge about this location and then be able to see the ISOs (possibly after a reboot, provided you added the mountpoint into fstab so that it's mounted at boot time).

ThierryC01

@florent Yes, all backup folders are present with all the data. All I did was just upgrade Xcp-ng from 8.2 to 8.3. I thought that performing backups before was a good idea... I have the backups but no mean to restore them

The backup page is blank in XOA, as well as the restore page. After importing the config backup, I noticed that the pool name was renamed (???) and only the backup list is displayed and disabled, after enabling all the backups, nothing is shown to restore.

florent

@ThierryC01 the backup aren't linked to the Sr , maybe there is a problem in the XO/Xoa

Can you show me a screenshot of the backup page ? I am not sure we're talking of the same thing

ThierryC01

@florent Sure, here are the screenshots after importing the config.json saved from 8.2 before the upgrade. The backup Jobs page was empty.

Xcp-ng backup_1.png

Xcp-ng backup_2.png

And this is the files on my remote share

Xcp-ng backups.png

florent

@ThierryC01 is the remote connected ? what happen when you click on "refresh backup list" ?

edit : it seems you have multiple remotes, each one with only one vm ?

ThierryC01

@florent Remote is connected all the time, it is a NAS and each VM has its own folder otherwise it is just a mess of mumble jumble folder names that no one knows which VM it is. Refreshing the backup jobs or restore page does nothing.

ThierryC01

@stormi I edited the fstab to mount my ISO SR and it is back online. Next time, I will remember to backup this file too before any upgrade.

florent

@ThierryC01 said in XCP-ng 8.3 beta :

@florent Remote is connected all the time, it is a NAS and each VM has its own folder otherwise it is just a mess of mumble jumble folder names that no one knows which VM it is. Refreshing the backup jobs or restore page does nothing.

ok, that's a first for me
The only way this can work is with multiples remote and job set in XO. Are they still there ? no error ?

ThierryC01

@florent I found the source of the problem, I already had it when I was trying the backup feature in 8.2 and it is with the remote settings: if there is a logon issue, there is no way to edit the password, save and go with it, you have to re-create the remote entirely which is extremely frustrating. For some reason, the password encryption does not behave as expected, when, editing the password, it is replaced by "obfuscated-xxxxxxx unique ID xxxxxxx" so it cannot work.

The message I get when trying to connect to a remote folder or just after editing the password and save
Xcp-ng remote_1.png

The obfuscated password displayed when editing
Xcp-ng remote_3png.png

And the error log for the logon attempt with the correct password:

remote.test
{
  "id": "365964ae-ea3c-41a5-80eb-0c5eb595f01d"
}
{
  "messageName": "session_setup_step2",
  "params": {},
  "message": "STATUS_LOGON_FAILURE (0xC000006D) : The attempted logon is invalid. This is either due to a bad username or authentication information.",
  "code": "STATUS_LOGON_FAILURE",
  "name": "Error",
  "stack": "Error: STATUS_LOGON_FAILURE (0xC000006D) : The attempted logon is invalid. This is either due to a bad username or authentication information.
    at SMB2Forge.request (/etc/xen-orchestra/node_modules/@marsaud/smb2/lib/tools/smb2-forge.js:22:15)
    at /etc/xen-orchestra/node_modules/@marsaud/smb2/lib/tools/smb2-connection.js:108:11
    at Object.<anonymous> (/etc/xen-orchestra/node_modules/@marsaud/smb2/lib/tools/message.js:15:15)
    at Socket.<anonymous> (/etc/xen-orchestra/node_modules/@marsaud/smb2/lib/tools/smb2-forge.js:71:31)
    at Socket.emit (events.js:400:28)
    at Socket.emit (domain.js:475:12)
    at Socket.patchedEmit [as emit] (/etc/xen-orchestra/@xen-orchestra/log/configure.js:118:17)
    at addChunk (internal/streams/readable.js:293:12)
    at readableAddChunk (internal/streams/readable.js:267:9)
    at Socket.Readable.push (internal/streams/readable.js:206:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
    at TCP.callbackTrampoline (internal/async_hooks.js:130:17)"
}

florent

@ThierryC01 the obfuscated- part is added to the data sent to the web client and the logs

But , in theory, editing a remote with a new password will change the password.

You can check the data saved in the XO database by executing yarn xo-server-db ls remote from your xo folder