Current Ubuntu Trusty kernel `linux-image-generic-lts-xenial`,
backported from Xenial, introduced a regressiong with our
10G Extreme Networks switch - sometimes the link negotiation
fails.
This was not a problem with the previous 4.4 kernel we used,
4.4.0-45-generic (current is 4.4.0-47-generic), so pin it until
upstream fixes the rootcause.
Since the local mirror only contains the new kernel, bring back
access to public Ubuntu repos (only for this pod).
NOTE: Our admin interface is on a PCI NIC, so we will keep
using the new (faulty) kernel for bootstrap image.
See [1] for full problem description.
[1] https://jira.opnfv.org/browse/ARMBAND-168
Change-Id: I39505013804620f1b910169492e895a637d20de2
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
(cherry picked from commit
08c3f00d26b3d2df6fdd66385cf5cda8c2e9d9e7)
extra_priority: null
type: custom_repo_configuration
value:
- - name: ubuntu
+ - name: ubuntu-local
priority: null
section: main
suite: trusty
type: deb
uri: http://10.20.0.2:8080/mirrors/ubuntu/
+ - name: ubuntu
+ priority: null
+ section: main universe multiverse
+ suite: trusty
+ type: deb
+ uri: http://ports.ubuntu.com/
+ - name: ubuntu-updates
+ priority: null
+ section: main universe multiverse
+ suite: trusty-updates
+ type: deb
+ uri: http://ports.ubuntu.com/
+ - name: ubuntu-security
+ priority: null
+ section: main universe multiverse
+ suite: trusty-security
+ type: deb
+ uri: http://ports.ubuntu.com/
- name: mos
priority: 1050
section: main restricted
linux-firmware-nonfree
- linux-headers-generic-lts-xenial
+ linux-headers-4.4.0-45-generic
- linux-image-generic-lts-xenial
+ linux-image-4.4.0-45-generic
lvm2