#Ubuntu 14.04.2 failed update update#
#Ubuntu 14.04.2 failed update code#

#Ubuntu 14.04.2 failed update update#

When i update the default ttl to 30 seconds, I got more failures util I got the response with TTL 30

#Ubuntu 14.04.2 failed update code#

The result of running this code is as followed: Print socket.getaddrinfo('kubernetes', '443') This is the code i used to test import socket I'm using python socket.getaddrinfo to resolve the service name, using socket.gethostbyname works around this issue since it only queries the A records. I tried to use the same client code in Ubuntu 18.04 which can resolve the service name every time. My ubuntu 14.04 client failed to resolve service name when I got a response with TTL less than the minimun TTL value in SOA field(response with IPv6 result, no IPv6 address resolved). Which kernel version can we expect the fix to be in? I checked the backports-kernels' change logs up to and including the currentВ linux-image-4.9.0-0.bpo.3-amd64 but haven't found any evidence of fixes regarding this issue to be included until now.I have a K8S 1.14 cluster setup with CoreDNS 1.5.0 as default DNS server. hv_storvsc vmbus_0_1: stor pkt ffff8802f93ac3c0 autosense data valid - len 18 hv_storvsc vmbus_0_1: cmd 0x28 scsi status 0x2 srb status 0x82 The Linux SCSI layer does not automatically adjust these parameters. sd 2:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. hv_storvsc vmbus_0_1: stor pkt ffff8802f710f200 autosense data valid - len 18 hv_storvsc vmbus_0_1: cmd 0x2a scsi status 0x2 srb status 0x82 Whereas Debian Jessie shows the dreaded messages and sometimes timeouts during nightly backups and remounts R/O. (Bonus question: Is this something to worry about?) sd 2:0:0:0: Sense Key : Illegal Request We also have some CentOS based guests running without issues from what we've seen.ДЄt least our Ubuntu instances only show the following: We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. We see the same errors on both.ДЄs a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other.

Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. This relates to the VSS 'Windows Server Backup' process that kicks off at midnight on the host and finishes an hour and half later. Sense: Changed operating definitionДЄpr 30 01:23:26 balticnetworkstraining kernel: sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters.ДЄpr 30 01:23:26 balticnetworkstraining kernel: hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82ДЄpr 30 01:23:26 balticnetworkstraining kernel: hv_storvsc vmbus_0_4: stor pkt ffff88006eb6c700 autosense data valid - len 18ДЄpr 30 01:23:26 balticnetworkstraining kernel: storvsc: Sense Key : Unit Attention ДЄpr 30 01:23:26 balticnetworkstraining kernel: storvsc: Add. Sense: Changed operating definitionДЄpr 30 00:02:01 balticnetworkstraining kernel: sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. Must reboot the Ubuntu guest to get the file system to mount RW again.ДЄpr 30 00:02:01 balticnetworkstraining kernel: storvsc: Sense Key : Unit Attention ДЄpr 30 00:02:01 balticnetworkstraining kernel: storvsc: Add.

On a random Basis, the file system will be mounted Read-Only due to a 'disk error' (which really isn't the case here). We're running various version of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.