Unfortunately I fell into the same trap. My system - although locked - installed 7.6 final but did not upgrade the Kernel.
Cleaning the yum cache helped. But know with the new Kernel the system still seem to have issues such as
Chron / logrotate creates files with xxx.log.1 instead of xxx.log-20181217
The system in bridge mode does not show the external IP in diagnostics
I need to reboot my switch everytime I restart nethserver (seems to be someting strange with the network interface)
TLS Handshake and log-on to Nextcloud (14.04) takes much longer as before.
I’m running NS as a Guest in HyperV 16.
May be it is just a misconfiguration or do I need to add additional repros? Does it make sense to investigate further or is there an easy way to go back to NS 7.5.
If any issue is caused by the latest kernel you don’t need to downgrade the whole system: just select the previous kernel at the system boot prompt to make a quick test.
I can’t reproduce it on a 7.6 here…
I don’t know how this can be related with the upgrade.
Isn’t there usually (at least in 7.5) in the menue on the left side an entry Virtual Host?
I can’t find any more.
Furthermore, I had one virtual host for my nextcloud. I can not reach nextcloud with the host name anymore - it routes to the nethserver screen "Congratulations your NS installation is up and runnig. The IP addess of the server x.x.x.x/nextcloud does work.
same problem here on hyper-v 2016 and 2012-r2.
vm was locked, unlocked today to upgrade to 7.6.
With the new kernel ther are problems on eth, booting using previous one seems ok… i’ll do some other test but not today
I’m dealing with the same issue. I’ve booted into the old kernel, but can’t reinstall the integration services because it’s not my most recent kernel, and can’t install them while on the newest kernel because it says that kernel is not supported.
I tested a fresh install of nethserver 7.6 from ISO into a new hyper V 2016 Gen 2 Guest.
Same problem - NS does not get a connection on green interface.
Also verified that the HyperV Host has the latest Intel Nic dirvers.
Not sure if this is a HW issue. If so then may be the Intel NICs.
The fresh NS install from ISO was on a Supermicro X10srm, E5-2628V4, i350 NICs
I copied the same VM to a HP DL380p Gen8 with E5-2650L V2, i350 NICs.
It’s hard to search the error given yum update does not work (issues to resolve the mirrors; network not reachable; ) which prevents me from adding tools and other modules or the linux integration services.
From time to time I can resolve the mirrors with nslookup. ifconfig looks good.
Can’t test proxmox nor vmware.
I’m not a linux guy and reached an end and will wait unitl a new kernel will be released.
Good news: Microsoft released LIS 4.2.8 on Jan 14th which according to the release notes seem to solve my Kernel issues under HyperV16. I tried with my fresh installed test nhs 7.6 virtual machine which now gets an internet connection with Kernel 3.10.0-957.1.3.el7.x86_64. I can now run yum update and log into the Web UI.
I’m going to further test before I apply to production but looks good for now.
without LIS no connection no fun (at least on my HyperV16).
To Install LIS 4.2.8 download the ISO from MS and attached it as CDROM to the NS virtual maschine and mount it after boot.
mount /dev/cdrom /media
cd /media
In case you already have an old version installed then remove it from NS.
./uninstall.sh
Update to the latest kernel 3.10.0-957.1.3 and reboot to ensure the kernel is active.
In case you can not ssh into NS anymore then use Hyper-V Manager and connect from there to the NS virtual machine.
Mount CDROM/iso again.
./install.sh
reboot (and detach cdrom).
You should be done.
I will no longer update the kernel from the software center since it most probably will damage the system until the corresponding LIS package is available.
May be the developers can add a checkbox so that we can deselect the update of the kernel.
