-
@JeffBerntsen @r1 https://cateee.net/lkddb/web-lkddb/NFSD_PNFS.html
"This option enables support for the parallel NFS features of the minor version 1 of the NFSv4 protocol (RFC5661) in the kernel's NFS server." -
Update released for XCP-ng 7.6 :
openvswitch-2.5.3-2.2.3.3.xcpngIt fixes a problem in log rotation introduced by our previous update: rotated logs for
/var/log/ovsdb-server.logwould get rotated themselves, which could lead to the creation of thousands of rotated log files. My mistake.See https://github.com/xcp-ng/xcp/issues/100 and https://xcp-ng.org/forum/topic/1031/too-many-weird-ovsdb-server-log-file
If you had not installed the previous openvswitch update, then there's no hurry to install this specific update. It would just add log rotation of its logs to avoid having them grow too much.
You don't need to reboot your hosts after installing this update, even if Xen Orchestra says so (we haven't given XO knowledge about what update requires an update yet). Unless you are installing kernel or xen updates at the same time, of course.
The update will not clean the extraneous files, so you'll still need to delete them manually (/var/log/ovsdb-server.log.*).
closed OpenVSwitch Logs aren't rotated #100
-
@stormi
upon update, I got a
Transaction check error:
installing package openvswitch-2.5.3-2.2.3.3.xcpng.x86_64 needs 1 inodes on the /var/log filesystemWhich translated that the ovsdb-server logs were too many and had filled up my log storage.
I had to run:
find . -name "ovsdb*" -delete
because rm couldn't handle so many ovsdb log files to delete. -
@nuts23 Thanks for the feedback. Indeed, when the /var/log partition is out of inode, you may need to delete the files before installing the update.
-
-
New update candidates are available to fix the recently disclosed Xen security issues (see http://xenbits.xen.org/xsa/ and https://support.citrix.com/article/CTX246572).
Please test as soon as possible. Objective of the test: make sure that there is no obvious regression. Just tell us that you installed the update candidate, the version of XCP-ng, and whether it works as well as before or not after a reboot.
XCP-ng 7.6
xen-4.7.6-6.4.1.xcpngInstallation of the update candidate:
yum install --enablerepo='xcp-ng-updates_testing' xen-dom0-libs xen-hypervisor xen-tools xen-dom0-tools xen-libsReboot required after the installation.
XCP-ng 7.5
xen-4.7.5-5.8.1.xcpInstallation of the update candidate:
yum install --enablerepo='xcp-ng-updates_testing' xen-dom0-libs xen-hypervisor xen-tools xen-dom0-tools xen-libsReboot required after the installation.
-
Anyone? This update candidate should be as safe as could be and internal tests are OK, but I don't want to push it before I get feedback from a few testers.
-
Updated one host without issue and currently testing.
-
security fix installed. Does it require a reboot of the system?
-
@nuts23 yes
-
@stormi testhost updated, restored some part of our infrastructur (DC, Mail, ...) on local ZFS pool, connected the VMs to a test network. Runs. A bit slow (more vCPU used than the PCPU can delivier), but runs.
-
@stormi said in Updates announcements and testing:
Anyone?
I updated one host in a pool and reboot. It is working as before. Seems no problem. I can't see any diffrence vcpu usage as @borzel say.
-
So far so good .. I haven't noticed any visible change in performance like @borzel but still monitoring.
-
Since there's an update for both XCP-ng 7.5 and 7.6, please all tell me which version you tested
-
@AllooTikeeChaat there was no performance change, was the first use of that test host
@stormi XCP-ng 7.6, just HVM, no PV
-
If all goes well I'll push the updates to everyone on monday. Meanwhile, please go on with the testing if you can.
-
@stormi XCP-ng 7.6
-
Thanks to everyone who tested the update candidate. I've now pushed the security update for XCP-ng 7.6. I'm holding that of XCP-ng 7.5 until at least one person confirms that it's working for them.
-
Sorry been away this weekend .. @stormi XCP-ng 7.6
-
I've installed the updates on a pool. Now every time I migrate a pfSense HVM VM within the pool the console is gone and memory usage is at 100%. I did do the following on the pool master:
yum update xenopsd xenopsd-xc xenopsd-xenlight --enablerepo='xcp-ng-updates_testing'. The package version also differs from other hosts (0.66.0-1.1.xcpngversus0.66.0-1.el7.centos). Would that be the cause?
