| factory repo, should it be used or not? [message #53268] |
Fri, 11 May 2018 08:31  |
javii
Messages: 6
Registered: October 2016
|
Junior Member |
From: 185.210.75*
|
|
Hi, I noticed latest version (openvz-iso-7.0.7-359.iso) comes with factory repo enabled, but in the factory.repo says it is only for developers.
What should we do?
Thank you!
|
|
|
|
|
|
|
|
|
|
|
|
| Re: factory repo, should it be used or not? [message #53300 is a reply to message #53299] |
Tue, 22 May 2018 13:21  |
vaverin
Messages: 682
Registered: September 2005
|
Senior Member |
From: *virtuozzo.com
|
|
Hmm,
I'm not sure that I understand your question correctly.
Let's take look at
https://download.openvz.org/virtuozzo/factory/x86_64/os/repo view/
I see here our new kernel, guest tools, dispatcher, criu, libvirt, vzctl and anaconda,
and I do not see here any packages directly retrieved from the latest CentOS 7.
We should not break original CentOS7 functionality (at least I hope so),
but our own packages included into factory are not well tested.
|
|
|
|
|
|
| Re: factory repo, should it be used or not? [message #53310 is a reply to message #53300] |
Fri, 25 May 2018 18:47 |
TomvB
Messages: 25
Registered: July 2017
Location: Netherlands
|
Junior Member |
From: 185.92.69*
|
|
vaverin wrote on Tue, 22 May 2018 15:21Hmm,
I'm not sure that I understand your question correctly.
Let's take look at
https://download.openvz.org/virtuozzo/factory/x86_64/os/repo view/
I see here our new kernel, guest tools, dispatcher, criu, libvirt, vzctl and anaconda,
and I do not see here any packages directly retrieved from the latest CentOS 7.
We should not break original CentOS7 functionality (at least I hope so),
but our own packages included into factory are not well tested.
I have one machine with the following error:
May 23 21:33:26 ovz7 kernel: BUG: unable to handle kernel paging request at 00000000ffffffec
<freeze / downtime>
May 25 21:29:55 ovz7 journal: Runtime journal is using 8.0M (max allowed 150.0M, trying to leave 2.3G free of 15.6G available → current limit 150.0M).
Is this the dev-kernel? The machine sometimes freezes with this kernel bug.
3.10.0-693.21.1.vz7.47.4 #1 SMP Sat Apr 28 11:48:07 MSK 2018 x86_64 x86_64 x86_64 GNU/Linux
I'm testing: 3.10.0-693.21.1.vz7.46.7 now.
[Updated on: Fri, 25 May 2018 19:23] Report message to a moderator |
|
|
|
|
|
| Re: factory repo, should it be used or not? [message #53335 is a reply to message #53306] |
Mon, 04 June 2018 01:22 |
websavers
Messages: 13
Registered: March 2018
Location: Halifax, NS
|
Junior Member |
From: *eastlink.ca
|
|
websavers wrote on Thu, 24 May 2018 23:13vaverin wrote on Fri, 11 May 2018 09:33Dear javii,
it is our fail,
factory repository should be disabled in stable branch.
We're going to release updated version soon,
right now please disable factory repo manually.
To confirm, /etc/yum.repos.d has (among others):
- factory.repo
- openvz.repo
- vzlinux.repo
We are to disable everything in factory.repo as well as any entry with factory in the name (like virtuozzolinux-factory) found in vzlinux.repo -- does that sound accurate?
Since we never got a response from Virtuozzo devs (despite the factory repo being enabled being their screw-up) here's what fixes it:
yum-config-manager --disable factory
yum-config-manager --disable virtuozzolinux-openvz-factory
yum-config-manager --disable virtuozzolinux-factory
yum distribution-synchronization
Then reboot the node to ensure it boots into the new (security patched) kernel. The yum distribution-synchronization command will both install the newest kernel release and ensure all packages are no longer from factory.
[Updated on: Mon, 04 June 2018 01:23] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Login
Home
