sources.list on OVH

[carles89]

Hello,

We've 3 servers on OVH, with Proxmox installed from their template.

I see different sources.list files between nodes.

NODE0:

deb http://debian.mirrors.ovh.net/debian/ stretch main contrib
# security updates
deb http://security.debian.org/ stretch/updates main contrib

NODE1:

deb http://debian.mirrors.ovh.net/debian/ stretch main
deb-src http://debian.mirrors.ovh.net/debian/ stretch main

deb http://security.debian.org/ stretch/updates main
deb-src http://security.debian.org/ stretch/updates main

# stretch-updates, previously known as 'volatile'
deb http://debian.mirrors.ovh.net/debian/ stretch-updates main
deb-src http://debian.mirrors.ovh.net/debian/ stretch-updates main

NODE2:

deb http://debian.mirrors.ovh.net/debian stretch main contrib non-free
deb-src http://debian.mirrors.ovh.net/debian stretch main contrib non-free

deb http://security.debian.org/debian-security stretch/updates main
deb-src http://security.debian.org/debian-security stretch/updates main

# stretch-updates, previously known as 'volatile'
deb http://debian.mirrors.ovh.net/debian stretch-updates main
deb-src http://debian.mirrors.ovh.net/debian stretch-updates main

I've modified all sources.list on all servers (as explained here:
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_package_repositories) by adding "contrib" to each line and remove sources lines. Is that OK?

Here is how it looks sources.list on all nodes except NODE2:

deb http://debian.mirrors.ovh.net/debian/ stretch main contrib

deb http://debian.mirrors.ovh.net/debian/ stretch-updates main contrib
# security updates
deb http://security.debian.org/ stretch/updates main contrib

On NODE2, there's a line which contains "non-free" repo. Should I leave it? Is it necessary for Proxmox to work? If I leave it, can it create any package inconsesty?

Thank you

PS: pve-enterprise is OK in all nodes, stored on /etc/apt/sources.list.d

 

[carles89]

Hello again,

On Node2, I see that the only packages installed from non-free are amd64-microcode and intel-microcode.


On the other nodes, these packages are not installed.

So, anyone can confirm that this configuration is correct, or should I install intel-microcode on all servers?

On NODE0 and NODE1:

deb http://debian.mirrors.ovh.net/debian/ stretch main contrib

deb http://debian.mirrors.ovh.net/debian/ stretch-updates main contrib
# security updates
deb http://security.debian.org/ stretch/updates main contrib

On NODE2 (the same as 0 and 1 but with non-free, in order to keep intel-microcode updated)

deb http://debian.mirrors.ovh.net/debian stretch main contrib non-free

deb http://security.debian.org/debian-security stretch/updates main contrib

# stretch-updates, previously known as 'volatile'
deb http://debian.mirrors.ovh.net/debian stretch-updates main contrib

Also, here are the processors for each node:

NODE0: 16 x Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz
NODE1: 16 x Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz
NODE2: 16 x Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz

I'm going to update all nodes from 5.2 to 5.4 this weekend.

Thank you

 

[BobhWasatch]

I have non-free in sources.list for the Intel microcode package. It caused no problem during the upgrade. I think in most cases it will be fine. I say that because most of my non-Proxmox Debian systems have non-free enabled for one reason or another and I've never had a problem.

But what you have installed from there may make a difference.

 

[carles89]

And what about contrib? Does it have any effect on Proxmox? On node1 it was not enabled...

Node 0 was installed with 3.4
Node 1 was installed with 4.4
Node 2 was installed with 5.0

Now all nodes have 5.2. I would like to be sure that all repos are OK before upgrading to 5.4.

Thanks

 

[BobhWasatch]

Maybe someone can give an official answer, but I don't think any of the standard Debian repositories would create a problem. The only exception might be backports, where you have newer versions of stuff that's in the main repos.

But do read the changes file when the upgrade shows them to you! Sometimes config files change format or whatever and cause things to break. Those issues will be documented on that screen so you can be prepared. Then when the upgrade process asks if I want to keep a config file that's been updated by the package I generally say "keep my version" and make a note. I then go back and look at the differences manually before rebooting (the new version will be saved as *.dpkg-dist or *.ucf-dist).

 

[carles89]

Thank you BobhWasatch, I've opened a support ticket sending a system report of all nodes to get an official answer from Proxmox.

Thanks again!