@manilx Yes, as written 
Lead Maintainer
Posts
-
RE: Just FYI: current update seams to break NUT dependancies
@FritzGerald workaround
yum update --exclude=net-snmp*This is dangerous.
-
RE: XCP-ng 8.3 updates announcements and testing
Although disabling
ssh-rsais the right thing to do from a security perspective, we'll see what we can do to smoothen the transition. -
RE: XCP-ng 8.3 No Longer Compatible with Older Adaptec RAID Card?
Mentioning also @Team-Hypervisor-Kernel who now manages the drivers.
Maybe it's related to https://github.com/xcp-ng-rpms/microsemi-aacraid/issues/2#issuecomment-3837183087
It looks like the switch to the vendor driver instead of the kernel built-in for 8.3 (initiated by XenServer, and that we followed at the time as it was probably made in order to support newer cards) was not without drawbacks.
-
RE: Remote syslog broken after update/reboot? - Changing it away, then back fixes.
To elaborate: it was already in progress, but delayed due to 1. the fact that I underestimated the impact (I thought we'd overwrite the file only when we'd modify it, not every update the package) and 2. lots of other priorities keeping the team busy.
But it's clearly the reminder, and the help in better diagnosing it, that allowed to have it re-prioritized and (partly, we've mostly bought time to fix it properly, by simply avoiding to touch the file at all at the moment) fixed so fast.
-
RE: Remote syslog broken after update/reboot? - Changing it away, then back fixes.
The fix was already high in the priority list anyway, but I'll try to make sure we don't postpone it more. Had I realized sooner, I would have made it so we'd release it earlier.
According to the package definitions, we even overwrite it each time we update the
xcp-ng-release-configpackage. I'm surprised that we haven't had more support requests.I'll see if we can release a quick fix that just leaves the file alone until we apply the change that will move the remote configuration to its own file.
-
RE: Remote syslog broken after update/reboot? - Changing it away, then back fixes.
@MajorP93 Thanks. That clarifies what happened. I wrongly thought that it was managed in
/etc/rsyslog.conf(which never gets overwritten), but it's in/etc/rsyslog.d/xenserver.conf, which can get overwritten if modified by an update. -
RE: Remote syslog broken after update/reboot? - Changing it away, then back fixes.
@MajorP93 Good to know that you have another pool to update. Then please also save the file prior to updating.