Calico-node readiness probe fails with SLES 15 SP1 nodes on Azure

Expected Behavior

Calico v3.8.2 to run successfully on SLES 15 SP1 on Azure.
Is it expected calico to be running on SLES? This OS is not listed as a OS that is expected to be working well here
Current Behavior

calico-node Pod readiness probe fails on the nodes that the calico-typha pod is not running.
Possible Solution

Steps to Reproduce (for bugs)

Create a vanilla Kubernetes cluster with SLES 15 SP1 on Azure with at least 2 worker nodes.
Install the calico in a similar manner to https://github.com/kubernetes/kubernetes/tree/v1.15.4/cluster/addons/calico-policy-controller.
Ensure that the calico pod rediness probe fails with:

$ k -n kube-system describe po calico-node-d2khj
Events:
  Type     Reason     Age                 From                                                             Message
  ----     ------     ----                ----                                                             -------
  Warning  Unhealthy  49m (x18 over 52m)  kubelet, my-vm-suse-85865bcf77-scwkj  Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503

k -n kube-system logs calico-node-d2khj
2019-11-05 16:00:50.113 [INFO][8] startup.go 256: Early log level set to info
2019-11-05 16:00:50.113 [INFO][8] startup.go 272: Using NODENAME environment for node name
2019-11-05 16:00:50.113 [INFO][8] startup.go 284: Determined node name: my-vm--local-az-worker-suse-85865bcf77-scwkj
2019-11-05 16:00:50.114 [INFO][8] k8s.go 219: Using host-local IPAM
2019-11-05 16:00:50.114 [INFO][8] startup.go 316: Checking datastore connection
2019-11-05 16:00:50.203 [INFO][8] startup.go 340: Datastore connection verified
2019-11-05 16:00:50.203 [INFO][8] startup.go 95: Datastore is ready
2019-11-05 16:00:50.322 [INFO][8] startup.go 530: FELIX_IPV6SUPPORT is false through environment variable
2019-11-05 16:00:50.368 [INFO][8] startup.go 181: Using node name: my-vm-suse-85865bcf77-scwkj
2019-11-05 16:00:50.395 [INFO][22] k8s.go 219: Using host-local IPAM
CALICO_NETWORKING_BACKEND is none - no BGP daemon running
Calico node started successfully
2019-11-05 16:56:41.721 [ERROR][45] sync_client.go 260: Failed to read from server address="<IP_ADDRESS>:5473" connID=0x0 error=EOF type=""
2019-11-05 16:56:43.721 [FATAL][45] daemon.go 641: Exiting. reason="Connection to Typha failed"
2019-11-05 16:56:45.041 [ERROR][6241] daemon.go 446: Failed to connect to Typha. Retrying... error=dial tcp <IP_ADDRESS>:5473: connect: connection refused
2019-11-05 16:57:24.130 [ERROR][6241] sync_client.go 260: Failed to read from server address="<IP_ADDRESS>:5473" connID=0x0 error=read tcp <IP_ADDRESS>:65454-><IP_ADDRESS>:5473: i/o timeout type=""
2019-11-05 16:57:26.131 [FATAL][6241] daemon.go 641: Exiting. reason="Connection to Typha failed"
2019-11-05 16:57:56.469 [ERROR][6354] sync_client.go 260: Failed to read from server address="<IP_ADDRESS>:5473" connID=0x0 error=read tcp <IP_ADDRESS>:32838-><IP_ADDRESS>:5473: i/o timeout type=""
2019-11-05 16:57:58.469 [FATAL][6354] daemon.go 641: Exiting. reason="Connection to Typha failed"
2019-11-05 16:58:28.719 [ERROR][6435] sync_client.go 260: Failed to read from server address="<IP_ADDRESS>:5473" connID=0x0 error=read tcp <IP_ADDRESS>:32996-><IP_ADDRESS>:5473: i/o timeout type=""
2019-11-05 16:58:30.719 [FATAL][6435] daemon.go 641: Exiting. reason="Connection to Typha failed"
2019-11-05 16:59:00.964 [ERROR][6516] sync_client.go 260: Failed to read from server address="<IP_ADDRESS>:5473" connID=0x0 error=read tcp <IP_ADDRESS>:33134-><IP_ADDRESS>:5473: i/o timeout type=""
2019-11-05 16:59:02.964 [FATAL][6516] daemon.go 641: Exiting. reason="Connection to Typha failed"
2019-11-05 16:59:33.221 [ERROR][6597] sync_client.go 260: Failed to read from server address="<IP_ADDRESS>:5473" connID=0x0 error=read tcp <IP_ADDRESS>:33290-><IP_ADDRESS>:5473: i/o timeout type=""
2019-11-05 16:59:35.222 [FATAL][6597] daemon.go 641: Exiting. reason="Connection to Typha failed"

Context

As this cluster is running on Azure, the following environment variables are used
FELIX_IPINIPENABLED=false
CALICO_NETWORKING_BACKEND=none
CALICO_IPV4POOL_IPIP=Never

Some details about the nodes:
$ k get node -o wide
NAME                          STATUS   ROLES    AGE    VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                              KERNEL-VERSION           CONTAINER-RUNTIME
my-vm-suse-85865bcf77-rns74   Ready    <none>   140m   v1.15.4   <IP_ADDRESS>    <none>        SUSE Linux Enterprise Server 15 SP1   4.12.14-197.21-default   docker://19.3.1
my-vm-suse-85865bcf77-scwkj   Ready    <none>   140m   v1.15.4   <IP_ADDRESS>    <none>        SUSE Linux Enterprise Server 15 SP1   4.12.14-197.21-default   docker://19.3.1

The very same cluster setup works fine if the OS is Ubuntu 18.04 or CoreOS 2135.6.0.
Your Environment

Calico version - v3.8.2
Orchestrator version (e.g. kubernetes, mesos, rkt): v1.15.4
Operating System and version:

$ cat /etc/os-release
NAME="SLES"
VERSION="15-SP1"
VERSION_ID="15.1"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP1"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp1"

Link to your project (optional):

We have disabled typha, which should mean that calico-node pods now talks directly with k8s API server instead of going through typha. The result is that the cluster is fully functional now, it even has passed the k8s conformance tests.

A few more findings.
This behaviour is observed on Google Cloud Platform, as well.
I have created another cluster that has 2 SUSE nodes, 2 CoreOS nodes and calico-typha is enabled.

When typha is running on a SUSE node I observe:

the calico-node on the same SUSE node has a successful readiness probe.
the calico-node on the other SUSE node has a failing readiness probe.
the calico-nodes on the CoreOS nodes have a successful readiness probe.

When typha is running on a CoreOS node I observe:

the calico-nodes on every node have a successful readiness probe.

Where should I dig further, calico, typha or both?

@caseydavenport / @fasaxc  can you provide feedback on this one?

SLES isn't one of the distros that we actively test with.  I'd recommend sticking to one of our supported platforms (Ubuntu/RH/Centos).  Failing that, look for different routing/iptables set-up on SLES that's blocking that traffic.

@fasaxc thanks for the reply.

I'd suggest looking at kube-proxy status and logs since it sets up the routing for the kubernetes service for typha, I am guessing that might be broken on SLES and that is why the nodes running on nodes without typha are not going ready.

@tmjd Actually, we bypass kube-proxy for accessing typha.  Felix loads the service endpoints from the API server directly and picks one to connect to.  That avoids relying on kube-proxy for bootstrapping Calico.
Typha is a host-networked pod, check that your iptables policy on SLES allows traffic to the host from the other hosts on Typha's port.

I do not see any issues in the kube-proxy logs.
The communication from node to typha seems to be open
$  nc -v -z <IP_ADDRESS> 5473
<IP_ADDRESS>: inverse host lookup failed: Unknown host
(UNKNOWN) [<IP_ADDRESS>] 5473 (?) open

$  mtr -P 5473 -T -w <IP_ADDRESS>
Start: 2019-11-12T16:51:50+0000
HOST: local-az-worker-suse-84f78947bf-hlsbt Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- <IP_ADDRESS>                                            0.0%    10    1.1   1.0   0.8   1.3   0.1

$ mtr --tcp  --port 5473 --report --report-cycles 10 <IP_ADDRESS>
Start: 2019-11-12T16:55:33+0000
HOST: local-az-w Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- <IP_ADDRESS>               0.0%    10    0.9   0.9   0.7   1.1   0.1

$ telnet <IP_ADDRESS> 5473
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS>.
Escape character is '^]'.
^]
telnet> Connection closed.

$ nmap <IP_ADDRESS> -p 5473 -Pn
Starting Nmap 7.70 ( https://nmap.org ) at 2019-11-12 17:01 UTC
Nmap scan report for <IP_ADDRESS>
Host is up.

PORT     STATE    SERVICE
5473/tcp filtered apsolab-tags

Nmap done: 1 IP address (1 host up) scanned in 2.19 seconds

Note, nmap output is identical to a cluster with CoreOS nodes. So I think that there is connectivity between the calico-node and calico-typha.
Let me provide some logs from the VM that is not hosting the Calico Typha.
calico-typha logs
2019-11-12 15:47:45.122 [INFO][6] sync_server.go 373: New connection connID=0x144 port=5473
2019-11-12 15:47:45.122 [INFO][6] sync_server.go 531: Per-connection goroutine started client=<IP_ADDRESS>:46700 connID=0x144
2019-11-12 15:47:45.127 [INFO][6] sync_server.go 656: Received Hello message from client. client=<IP_ADDRESS>:46700 connID=0x144 msg=syncproto.MsgClientHello{Hostname:"local-az-worker-suse-84f78947bf-hlsbt", Info:"Revision: a161671c667ac33d85736944e9aa069995498911; Build date: ", Version:"v3.8.2", SyncerType:"felix"}
2019-11-12 15:47:45.127 [INFO][6] sync_server.go 561: Waiting for messages from client client=<IP_ADDRESS>:46700 connID=0x144
2019-11-12 15:47:45.127 [INFO][6] sync_server.go 825: Starting to send snapshot to client client=<IP_ADDRESS>:46700 connID=0x144 seqNo=0x7 status=in-sync thread="kv-sender"
2019-11-12 15:47:45.128 [INFO][6] sync_server.go 859: Finished sending snapshot to client client=<IP_ADDRESS>:46700 connID=0x144 numKeys=79 seqNo=0x7 status=in-sync thread="kv-sender"
2019-11-12 15:47:45.128 [INFO][6] sync_server.go 726: Status update to send. client=<IP_ADDRESS>:46700 connID=0x144 newStatus=in-sync thread="kv-sender"
2019-11-12 15:48:15.130 [INFO][6] sync_server.go 609: Failed to read from client client=<IP_ADDRESS>:46700 connID=0x144 error=EOF thread="read"
2019-11-12 15:48:15.130 [INFO][6] sync_server.go 602: Read goroutine finished client=<IP_ADDRESS>:46700 connID=0x144 thread="read"
2019-11-12 15:48:15.130 [INFO][6] sync_server.go 589: Asked to stop by Context. client=<IP_ADDRESS>:46700 connID=0x144
2019-11-12 15:48:15.130 [INFO][6] sync_server.go 555: Stopping pong check ticker. client=<IP_ADDRESS>:46700 connID=0x144
2019-11-12 15:48:15.130 [INFO][6] sync_server.go 903: Context was canceled. error=context canceled
2019-11-12 15:48:15.130 [INFO][6] sync_server.go 888: Stopping ping ticker client=<IP_ADDRESS>:46700 connID=0x144 thread="pinger"
2019-11-12 15:48:15.130 [INFO][6] sync_server.go 884: Pinger goroutine shut down. client=<IP_ADDRESS>:46700 connID=0x144 thread="pinger"
2019-11-12 15:48:15.131 [INFO][6] sync_server.go 518: Client connection shutting down. client=<IP_ADDRESS>:46700 connID=0x144
2019-11-12 15:48:15.131 [INFO][6] jittered_ticker.go 57: Stopping jittered ticker
2019-11-12 15:48:15.131 [INFO][6] jittered_ticker.go 57: Stopping jittered ticker
2019-11-12 15:48:15.457 [INFO][6] sync_server.go 755: Getting next Breadcrumb canceled by context. client=<IP_ADDRESS>:46700 connID=0x144 error=context canceled thread="kv-sender"
2019-11-12 15:48:15.457 [INFO][6] sync_server.go 708: KV-sender goroutine shutting down client=<IP_ADDRESS>:46700 connID=0x144 thread="kv-sender"
2019-11-12 15:48:15.457 [INFO][6] sync_server.go 711: KV-sender goroutine finished client=<IP_ADDRESS>:46700 connID=0x144 thread="kv-sender"
2019-11-12 15:48:15.457 [INFO][6] sync_server.go 527: Client connection shut down. client=<IP_ADDRESS>:46700 connID=0x144
2019-11-12 15:48:15.457 [INFO][6] sync_server.go 401: Connection handler finished error=context canceled
2019-11-12 15:48:17.501 [INFO][6] sync_server.go 348: Accepted from <IP_ADDRESS>:46850 port=5473

calico-node logs
2019-11-12 15:47:44.549 [INFO][19004] logutils.go 82: Early screen log level set to info
2019-11-12 15:47:44.549 [INFO][19004] daemon.go 138: Felix starting up GOMAXPROCS=2 buildDate="" gitCommit="a161671c667ac33d85736944e9aa069995498911" version="v3.8.2"
2019-11-12 15:47:44.549 [INFO][19004] daemon.go 156: Loading configuration...
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "ipv6support"="false"
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "felixhostname"="local-az-worker-suse-84f78947bf-hlsbt"
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "ipinipenabled"="false"
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "typhak8sservicename"="calico-typha"
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "natportrange"="32768:65535"
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "etcdcertfile"=""
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "logseverityscreen"="info"
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "etcdscheme"=""
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "defaultendpointtohostaction"="ACCEPT"
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "etcdaddr"=""
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "datastoretype"="kubernetes"
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "etcdkeyfile"=""
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "healthenabled"="true"
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "ipinipmtu"="1440"
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "etcdendpoints"=""
2019-11-12 15:47:44.551 [INFO][19004] env_var_loader.go 40: Found felix environment variable: "etcdcafile"=""
2019-11-12 15:47:44.551 [INFO][19004] daemon.go 179: Loading config file: /etc/calico/felix.cfg
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 243: Merging in config from environment variable: map[felixhostname:local-az-worker-suse-84f78947bf-hlsbt healthenabled:true ipinipmtu:1440 etcdendpoints: ipv6support:false typhak8sservicename:calico-typha etcdcertfile: etcdaddr: datastoretype:kubernetes etcdcafile: natportrange:32768:65535 logseverityscreen:info etcdscheme: etcdkeyfile: ipinipenabled:false defaultendpointtohostaction:ACCEPT]
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 252: Ignoring empty configuration parameter. Use value 'none' if your intention is to explicitly disable the default value. name="etcdcertfile" source=environment variable
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 252: Ignoring empty configuration parameter. Use value 'none' if your intention is to explicitly disable the default value. name="etcdaddr" source=environment variable
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 252: Ignoring empty configuration parameter. Use value 'none' if your intention is to explicitly disable the default value. name="etcdcafile" source=environment variable
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 252: Ignoring empty configuration parameter. Use value 'none' if your intention is to explicitly disable the default value. name="etcdscheme" source=environment variable
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 252: Ignoring empty configuration parameter. Use value 'none' if your intention is to explicitly disable the default value. name="etcdkeyfile" source=environment variable
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 252: Ignoring empty configuration parameter. Use value 'none' if your intention is to explicitly disable the default value. name="etcdendpoints" source=environment variable
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 324: Parsing value for FelixHostname: local-az-worker-suse-84f78947bf-hlsbt (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 360: Parsed value for FelixHostname: local-az-worker-suse-84f78947bf-hlsbt (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 324: Parsing value for HealthEnabled: true (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 360: Parsed value for HealthEnabled: true (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 324: Parsing value for IpInIpMtu: 1440 (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 360: Parsed value for IpInIpMtu: 1440 (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 324: Parsing value for TyphaK8sServiceName: calico-typha (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 360: Parsed value for TyphaK8sServiceName: calico-typha (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 324: Parsing value for DatastoreType: kubernetes (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 360: Parsed value for DatastoreType: kubernetes (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 324: Parsing value for NATPortRange: 32768:65535 (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 360: Parsed value for NATPortRange: 32768:65535 (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 324: Parsing value for LogSeverityScreen: info (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 360: Parsed value for LogSeverityScreen: INFO (from environment variable)
2019-11-12 15:47:44.552 [INFO][19004] config_params.go 324: Parsing value for IpInIpEnabled: false (from environment variable)
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 360: Parsed value for IpInIpEnabled: false (from environment variable)
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 324: Parsing value for Ipv6Support: false (from environment variable)
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 360: Parsed value for Ipv6Support: false (from environment variable)
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 324: Parsing value for DefaultEndpointToHostAction: ACCEPT (from environment variable)
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 360: Parsed value for DefaultEndpointToHostAction: ACCEPT (from environment variable)
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 243: Merging in config from config file: map[MetadataAddr:None LogFilePath:None LogSeverityFile:None LogSeveritySys:None]
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 324: Parsing value for DatastoreType: kubernetes (from environment variable)
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 360: Parsed value for DatastoreType: kubernetes (from environment variable)
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 324: Parsing value for NATPortRange: 32768:65535 (from environment variable)
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 360: Parsed value for NATPortRange: 32768:65535 (from environment variable)
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 324: Parsing value for LogSeverityScreen: info (from environment variable)
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 360: Parsed value for LogSeverityScreen: INFO (from environment variable)
2019-11-12 15:47:44.553 [INFO][19004] config_params.go 324: Parsing value for IpInIpEnabled: false (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 360: Parsed value for IpInIpEnabled: false (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 324: Parsing value for FelixHostname: local-az-worker-suse-84f78947bf-hlsbt (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 360: Parsed value for FelixHostname: local-az-worker-suse-84f78947bf-hlsbt (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 324: Parsing value for HealthEnabled: true (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 360: Parsed value for HealthEnabled: true (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 324: Parsing value for IpInIpMtu: 1440 (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 360: Parsed value for IpInIpMtu: 1440 (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 324: Parsing value for TyphaK8sServiceName: calico-typha (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 360: Parsed value for TyphaK8sServiceName: calico-typha (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 324: Parsing value for DefaultEndpointToHostAction: ACCEPT (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 360: Parsed value for DefaultEndpointToHostAction: ACCEPT (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 324: Parsing value for Ipv6Support: false (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 360: Parsed value for Ipv6Support: false (from environment variable)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 324: Parsing value for MetadataAddr: None (from config file)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 341: Value set to 'none', replacing with zero-value: "".
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 360: Parsed value for MetadataAddr:  (from config file)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 324: Parsing value for LogFilePath: None (from config file)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 341: Value set to 'none', replacing with zero-value: "".
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 360: Parsed value for LogFilePath:  (from config file)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 324: Parsing value for LogSeverityFile: None (from config file)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 341: Value set to 'none', replacing with zero-value: "".
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 360: Parsed value for LogSeverityFile:  (from config file)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 324: Parsing value for LogSeveritySys: None (from config file)
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 341: Value set to 'none', replacing with zero-value: "".
2019-11-12 15:47:44.554 [INFO][19004] config_params.go 360: Parsed value for LogSeveritySys:  (from config file)
2019-11-12 15:47:44.555 [INFO][19004] health.go 225: Health enabled.  Starting server. host="localhost" port=9099
2019-11-12 15:47:44.555 [INFO][19004] config_params.go 428: Encap disabled, disabling node poll (if KDD is in use).
2019-11-12 15:47:44.555 [INFO][19004] daemon.go 211: Connecting to datastore datastore="kubernetes"
2019-11-12 15:47:44.557 [INFO][19004] k8s.go 219: Using host-local IPAM
2019-11-12 15:47:44.557 [INFO][19004] daemon.go 218: Created datastore client
2019-11-12 15:47:44.645 [INFO][19004] daemon.go 771: Loaded ready flag kind="ClusterInformation" name="default" ready=true
2019-11-12 15:47:44.690 [INFO][19004] daemon.go 751: No config of this type kind="FelixConfiguration" name="node.local-az-worker-suse-84f78947bf-hlsbt"
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 243: Merging in config from datastore (global): map[ClusterGUID:5075b44df893404da853f337a40d18a1 ClusterType:k8s,bgp,kdd,typha CalicoVersion:v3.8.2 LogSeverityScreen:Info ReportingIntervalSecs:0]
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 324: Parsing value for DatastoreType: kubernetes (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 360: Parsed value for DatastoreType: kubernetes (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 324: Parsing value for NATPortRange: 32768:65535 (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 360: Parsed value for NATPortRange: 32768:65535 (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 324: Parsing value for LogSeverityScreen: info (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 360: Parsed value for LogSeverityScreen: INFO (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 324: Parsing value for IpInIpEnabled: false (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 360: Parsed value for IpInIpEnabled: false (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 324: Parsing value for FelixHostname: local-az-worker-suse-84f78947bf-hlsbt (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 360: Parsed value for FelixHostname: local-az-worker-suse-84f78947bf-hlsbt (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 324: Parsing value for HealthEnabled: true (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 360: Parsed value for HealthEnabled: true (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 324: Parsing value for IpInIpMtu: 1440 (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 360: Parsed value for IpInIpMtu: 1440 (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 324: Parsing value for TyphaK8sServiceName: calico-typha (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 360: Parsed value for TyphaK8sServiceName: calico-typha (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 324: Parsing value for DefaultEndpointToHostAction: ACCEPT (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 360: Parsed value for DefaultEndpointToHostAction: ACCEPT (from environment variable)
2019-11-12 15:47:44.714 [INFO][19004] config_params.go 324: Parsing value for Ipv6Support: false (from environment variable)
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 360: Parsed value for Ipv6Support: false (from environment variable)
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 324: Parsing value for LogSeveritySys: None (from config file)
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 341: Value set to 'none', replacing with zero-value: "".
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 360: Parsed value for LogSeveritySys:  (from config file)
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 324: Parsing value for MetadataAddr: None (from config file)
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 341: Value set to 'none', replacing with zero-value: "".
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 360: Parsed value for MetadataAddr:  (from config file)
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 324: Parsing value for LogFilePath: None (from config file)
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 341: Value set to 'none', replacing with zero-value: "".
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 360: Parsed value for LogFilePath:  (from config file)
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 324: Parsing value for LogSeverityFile: None (from config file)
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 341: Value set to 'none', replacing with zero-value: "".
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 360: Parsed value for LogSeverityFile:  (from config file)
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 324: Parsing value for ReportingIntervalSecs: 0 (from datastore (global))
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 360: Parsed value for ReportingIntervalSecs: 0s (from datastore (global))
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 324: Parsing value for ClusterGUID: 5075b44df893404da853f337a40d18a1 (from datastore (global))
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 360: Parsed value for ClusterGUID: 5075b44df893404da853f337a40d18a1 (from datastore (global))
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 324: Parsing value for ClusterType: k8s,bgp,kdd,typha (from datastore (global))
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 360: Parsed value for ClusterType: k8s,bgp,kdd,typha (from datastore (global))
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 324: Parsing value for CalicoVersion: v3.8.2 (from datastore (global))
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 360: Parsed value for CalicoVersion: v3.8.2 (from datastore (global))
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 324: Parsing value for LogSeverityScreen: Info (from datastore (global))
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 360: Parsed value for LogSeverityScreen: INFO (from datastore (global))
2019-11-12 15:47:44.715 [INFO][19004] config_params.go 363: Skipping config value for LogSeverityScreen from datastore (global); already have a value from environment variable
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 243: Merging in config from datastore (per-host): map[IpInIpTunnelAddr:<IP_ADDRESS>]
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 324: Parsing value for Ipv6Support: false (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 360: Parsed value for Ipv6Support: false (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 324: Parsing value for DefaultEndpointToHostAction: ACCEPT (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 360: Parsed value for DefaultEndpointToHostAction: ACCEPT (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 324: Parsing value for FelixHostname: local-az-worker-suse-84f78947bf-hlsbt (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 360: Parsed value for FelixHostname: local-az-worker-suse-84f78947bf-hlsbt (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 324: Parsing value for HealthEnabled: true (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 360: Parsed value for HealthEnabled: true (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 324: Parsing value for IpInIpMtu: 1440 (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 360: Parsed value for IpInIpMtu: 1440 (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 324: Parsing value for TyphaK8sServiceName: calico-typha (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 360: Parsed value for TyphaK8sServiceName: calico-typha (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 324: Parsing value for DatastoreType: kubernetes (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 360: Parsed value for DatastoreType: kubernetes (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 324: Parsing value for NATPortRange: 32768:65535 (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 360: Parsed value for NATPortRange: 32768:65535 (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 324: Parsing value for LogSeverityScreen: info (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 360: Parsed value for LogSeverityScreen: INFO (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 324: Parsing value for IpInIpEnabled: false (from environment variable)
2019-11-12 15:47:44.716 [INFO][19004] config_params.go 360: Parsed value for IpInIpEnabled: false (from environment variable)
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 324: Parsing value for MetadataAddr: None (from config file)
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 341: Value set to 'none', replacing with zero-value: "".
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 360: Parsed value for MetadataAddr:  (from config file)
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 324: Parsing value for LogFilePath: None (from config file)
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 341: Value set to 'none', replacing with zero-value: "".
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 360: Parsed value for LogFilePath:  (from config file)
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 324: Parsing value for LogSeverityFile: None (from config file)
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 341: Value set to 'none', replacing with zero-value: "".
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 360: Parsed value for LogSeverityFile:  (from config file)
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 324: Parsing value for LogSeveritySys: None (from config file)
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 341: Value set to 'none', replacing with zero-value: "".
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 360: Parsed value for LogSeveritySys:  (from config file)
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 324: Parsing value for IpInIpTunnelAddr: <IP_ADDRESS> (from datastore (per-host))
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 360: Parsed value for IpInIpTunnelAddr: <IP_ADDRESS> (from datastore (per-host))
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 324: Parsing value for ReportingIntervalSecs: 0 (from datastore (global))
2019-11-12 15:47:44.717 [INFO][19004] config_params.go 360: Parsed value for ReportingIntervalSecs: 0s (from datastore (global))
2019-11-12 15:47:44.718 [INFO][19004] config_params.go 324: Parsing value for ClusterGUID: 5075b44df893404da853f337a40d18a1 (from datastore (global))
2019-11-12 15:47:44.718 [INFO][19004] config_params.go 360: Parsed value for ClusterGUID: 5075b44df893404da853f337a40d18a1 (from datastore (global))
2019-11-12 15:47:44.718 [INFO][19004] config_params.go 324: Parsing value for ClusterType: k8s,bgp,kdd,typha (from datastore (global))
2019-11-12 15:47:44.718 [INFO][19004] config_params.go 360: Parsed value for ClusterType: k8s,bgp,kdd,typha (from datastore (global))
2019-11-12 15:47:44.718 [INFO][19004] config_params.go 324: Parsing value for CalicoVersion: v3.8.2 (from datastore (global))
2019-11-12 15:47:44.719 [INFO][19004] config_params.go 360: Parsed value for CalicoVersion: v3.8.2 (from datastore (global))
2019-11-12 15:47:44.719 [INFO][19004] config_params.go 324: Parsing value for LogSeverityScreen: Info (from datastore (global))
2019-11-12 15:47:44.719 [INFO][19004] config_params.go 360: Parsed value for LogSeverityScreen: INFO (from datastore (global))
2019-11-12 15:47:44.719 [INFO][19004] config_params.go 363: Skipping config value for LogSeverityScreen from datastore (global); already have a value from environment variable
2019-11-12 15:47:44.719 [INFO][19004] config_params.go 428: Encap disabled, disabling node poll (if KDD is in use).
2019-11-12 15:47:44.720 [INFO][19004] k8s.go 219: Using host-local IPAM
2019-11-12 15:47:44.744 [INFO][19004] daemon.go 1022: Found Typha ClusterIP. clusterIP="<IP_ADDRESS>"
2019-11-12 15:47:44.744 [INFO][19004] daemon.go 1029: Found Typha service port. port=v1.ServicePort{Name:"calico-typha", Protocol:"TCP", Port:5473, TargetPort:intstr.IntOrString{Type:1, IntVal:0, StrVal:"calico-typha"}, NodePort:31939}
2019-11-12 15:47:44.744 [INFO][19004] health.go 222: Health enabled.  Server is already running. host="localhost" port=9099
2019-11-12 15:47:44.744 [INFO][19004] daemon.go 286: Successfully loaded configuration. GOMAXPROCS=2 buildDate="" config=&config.Config{UseInternalDataplaneDriver:true, DataplaneDriver:"calico-iptables-plugin", DatastoreType:"kubernetes", FelixHostname:"local-az-worker-suse-84f78947bf-hlsbt", EtcdAddr:"<IP_ADDRESS>:2379", EtcdScheme:"http", EtcdKeyFile:"", EtcdCertFile:"", EtcdCaFile:"", EtcdEndpoints:[]string(nil), TyphaAddr:"", TyphaK8sServiceName:"calico-typha", TyphaK8sNamespace:"kube-system", TyphaReadTimeout:30000000000, TyphaWriteTimeout:10000000000, TyphaKeyFile:"", TyphaCertFile:"", TyphaCAFile:"", TyphaCN:"", TyphaURISAN:"", Ipv6Support:false, IgnoreLooseRPF:false, IptablesBackend:"legacy", RouteRefreshInterval:90000000000, IptablesRefreshInterval:90000000000, IptablesPostWriteCheckIntervalSecs:1000000000, IptablesLockFilePath:"/run/xtables.lock", IptablesLockTimeoutSecs:0, IptablesLockProbeIntervalMillis:50000000, IpsetsRefreshInterval:10000000000, MaxIpsetSize:1048576, XDPRefreshInterval:90000000000, PolicySyncPathPrefix:"", NetlinkTimeoutSecs:10000000000, MetadataAddr:"", MetadataPort:8775, OpenstackRegion:"", InterfacePrefix:"cali", InterfaceExclude:[]*regexp.Regexp{(*regexp.Regexp)(0xc000467900)}, ChainInsertMode:"insert", DefaultEndpointToHostAction:"ACCEPT", IptablesFilterAllowAction:"ACCEPT", IptablesMangleAllowAction:"ACCEPT", LogPrefix:"calico-packet", LogFilePath:"", LogSeverityFile:"", LogSeverityScreen:"INFO", LogSeveritySys:"", VXLANEnabled:false, VXLANPort:4789, VXLANVNI:4096, VXLANMTU:1410, IPv4VXLANTunnelAddr:net.IP(nil), VXLANTunnelMACAddr:"", IpInIpEnabled:false, IpInIpMtu:1440, IpInIpTunnelAddr:net.IP{0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xff, 0xff, 0x64, 0x60, 0x1, 0x1}, ReportingIntervalSecs:0, ReportingTTLSecs:90000000000, EndpointReportingEnabled:false, EndpointReportingDelaySecs:1000000000, IptablesMarkMask:0xffff0000, DisableConntrackInvalidCheck:false, HealthEnabled:true, HealthPort:9099, HealthHost:"localhost", PrometheusMetricsEnabled:false, PrometheusMetricsPort:9091, PrometheusGoMetricsEnabled:true, PrometheusProcessMetricsEnabled:true, FailsafeInboundHostPorts:[]config.ProtoPort{config.ProtoPort{Protocol:"tcp", Port:0x16}, config.ProtoPort{Protocol:"udp", Port:0x44}, config.ProtoPort{Protocol:"tcp", Port:0xb3}, config.ProtoPort{Protocol:"tcp", Port:0x94b}, config.ProtoPort{Protocol:"tcp", Port:0x94c}, config.ProtoPort{Protocol:"tcp", Port:0x1a0a}, config.ProtoPort{Protocol:"tcp", Port:0x1a0b}}, FailsafeOutboundHostPorts:[]config.ProtoPort{config.ProtoPort{Protocol:"udp", Port:0x35}, config.ProtoPort{Protocol:"udp", Port:0x43}, config.ProtoPort{Protocol:"tcp", Port:0xb3}, config.ProtoPort{Protocol:"tcp", Port:0x94b}, config.ProtoPort{Protocol:"tcp", Port:0x94c}, config.ProtoPort{Protocol:"tcp", Port:0x1a0a}, config.ProtoPort{Protocol:"tcp", Port:0x1a0b}}, KubeNodePortRanges:[]numorstring.Port{numorstring.Port{MinPort:0x7530, MaxPort:0x7fff, PortName:""}}, NATPortRange:numorstring.Port{MinPort:0x8000, MaxPort:0xffff, PortName:""}, NATOutgoingAddress:net.IP(nil), UsageReportingEnabled:true, UsageReportingInitialDelaySecs:300000000000, UsageReportingIntervalSecs:86400000000000, ClusterGUID:"5075b44df893404da853f337a40d18a1", ClusterType:"k8s,bgp,kdd,typha", CalicoVersion:"v3.8.2", ExternalNodesCIDRList:[]string(nil), DebugMemoryProfilePath:"", DebugCPUProfilePath:"/tmp/felix-cpu-<timestamp>.pprof", DebugDisableLogDropping:false, DebugSimulateCalcGraphHangAfter:0, DebugSimulateDataplaneHangAfter:0, sourceToRawConfig:map[config.Source]map[string]string{0x4:map[string]string{"typhak8sservicename":"calico-typha", "datastoretype":"kubernetes", "natportrange":"32768:65535", "logseverityscreen":"info", "ipinipenabled":"false", "felixhostname":"local-az-worker-suse-84f78947bf-hlsbt", "healthenabled":"true", "ipinipmtu":"1440", "ipv6support":"false", "defaultendpointtohostaction":"ACCEPT"}, 0x3:map[string]string{"MetadataAddr":"None", "LogFilePath":"None", "LogSeverityFile":"None", "LogSeveritySys":"None"}, 0x1:map[string]string{"CalicoVersion":"v3.8.2", "LogSeverityScreen":"Info", "ReportingIntervalSecs":"0", "ClusterGUID":"5075b44df893404da853f337a40d18a1", "ClusterType":"k8s,bgp,kdd,typha"}, 0x2:map[string]string{"IpInIpTunnelAddr":"<IP_ADDRESS>"}}, rawValues:map[string]string{"ReportingIntervalSecs":"0", "CalicoVersion":"v3.8.2", "Ipv6Support":"false", "NATPortRange":"32768:65535", "MetadataAddr":"None", "LogSeverityFile":"None", "IpInIpTunnelAddr":"<IP_ADDRESS>", "DatastoreType":"kubernetes", "LogFilePath":"None", "FelixHostname":"local-az-worker-suse-84f78947bf-hlsbt", "IpInIpMtu":"1440", "LogSeverityScreen":"info", "IpInIpEnabled":"false", "ClusterType":"k8s,bgp,kdd,typha", "DefaultEndpointToHostAction":"ACCEPT", "HealthEnabled":"true", "TyphaK8sServiceName":"calico-typha", "LogSeveritySys":"None", "ClusterGUID":"5075b44df893404da853f337a40d18a1"}, Err:error(nil), IptablesNATOutgoingInterfaceFilter:"", SidecarAccelerationEnabled:false, XDPEnabled:false, GenericXDPEnabled:false} gitCommit="a161671c667ac33d85736944e9aa069995498911" version="v3.8.2"
2019-11-12 15:47:44.744 [INFO][19004] driver.go 43: Using internal (linux) dataplane driver.
2019-11-12 15:47:44.745 [INFO][19004] driver.go 85: Calculated iptables mark bits acceptMark=0x10000 endpointMark=0xfff00000 endpointMarkNonCali=0x100000 passMark=0x20000 scratch0Mark=0x40000 scratch1Mark=0x80000
2019-11-12 15:47:44.745 [INFO][19004] int_dataplane.go 238: Creating internal dataplane driver. config=intdataplane.Config{Hostname:"local-az-worker-suse-84f78947bf-hlsbt", IPv6Enabled:false, RuleRendererOverride:rules.RuleRenderer(nil), IPIPMTU:1440, VXLANMTU:1410, IgnoreLooseRPF:false, MaxIPSetSize:1048576, IptablesBackend:"legacy", IPSetsRefreshInterval:10000000000, RouteRefreshInterval:90000000000, IptablesRefreshInterval:90000000000, IptablesPostWriteCheckInterval:1000000000, IptablesInsertMode:"insert", IptablesLockFilePath:"/run/xtables.lock", IptablesLockTimeout:0, IptablesLockProbeInterval:50000000, XDPRefreshInterval:90000000000, NetlinkTimeout:10000000000, RulesConfig:rules.Config{IPSetConfigV4:(*ipsets.IPVersionConfig)(0xc0003a4be0), IPSetConfigV6:(*ipsets.IPVersionConfig)(0xc0003a4cd0), WorkloadIfacePrefixes:[]string{"cali"}, IptablesMarkAccept:0x10000, IptablesMarkPass:0x20000, IptablesMarkScratch0:0x40000, IptablesMarkScratch1:0x80000, IptablesMarkEndpoint:0xfff00000, IptablesMarkNonCaliEndpoint:0x100000, KubeNodePortRanges:[]numorstring.Port{numorstring.Port{MinPort:0x7530, MaxPort:0x7fff, PortName:""}}, KubeIPVSSupportEnabled:false, OpenStackMetadataIP:net.IP(nil), OpenStackMetadataPort:0x2247, OpenStackSpecialCasesEnabled:false, VXLANEnabled:false, VXLANPort:4789, VXLANVNI:4096, IPIPEnabled:false, IPIPTunnelAddress:net.IP{0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xff, 0xff, 0x64, 0x60, 0x1, 0x1}, VXLANTunnelAddress:net.IP(nil), IptablesLogPrefix:"calico-packet", EndpointToHostAction:"ACCEPT", IptablesFilterAllowAction:"ACCEPT", IptablesMangleAllowAction:"ACCEPT", FailsafeInboundHostPorts:[]config.ProtoPort{config.ProtoPort{Protocol:"tcp", Port:0x16}, config.ProtoPort{Protocol:"udp", Port:0x44}, config.ProtoPort{Protocol:"tcp", Port:0xb3}, config.ProtoPort{Protocol:"tcp", Port:0x94b}, config.ProtoPort{Protocol:"tcp", Port:0x94c}, config.ProtoPort{Protocol:"tcp", Port:0x1a0a}, config.ProtoPort{Protocol:"tcp", Port:0x1a0b}}, FailsafeOutboundHostPorts:[]config.ProtoPort{config.ProtoPort{Protocol:"udp", Port:0x35}, config.ProtoPort{Protocol:"udp", Port:0x43}, config.ProtoPort{Protocol:"tcp", Port:0xb3}, config.ProtoPort{Protocol:"tcp", Port:0x94b}, config.ProtoPort{Protocol:"tcp", Port:0x94c}, config.ProtoPort{Protocol:"tcp", Port:0x1a0a}, config.ProtoPort{Protocol:"tcp", Port:0x1a0b}}, DisableConntrackInvalid:false, NATPortRange:numorstring.Port{MinPort:0x8000, MaxPort:0xffff, PortName:""}, IptablesNATOutgoingInterfaceFilter:"", NATOutgoingAddress:net.IP(nil)}, IfaceMonitorConfig:ifacemonitor.Config{InterfaceExcludes:[]*regexp.Regexp{(*regexp.Regexp)(0xc000467900)}}, StatusReportingInterval:0, ConfigChangedRestartCallback:(func())(0x1464ab0), PostInSyncCallback:(func())(0x144b060), HealthAggregator:(*health.HealthAggregator)(0xc0005e3410), DebugSimulateDataplaneHangAfter:0, ExternalNodesCidrs:[]string(nil), XDPEnabled:false, XDPAllowGeneric:false, SidecarAccelerationEnabled:false, LookPathOverride:(func(string) (string, error))(nil)}
2019-11-12 15:47:44.745 [INFO][19004] rule_defs.go 294: Creating rule renderer. config=rules.Config{IPSetConfigV4:(*ipsets.IPVersionConfig)(0xc0003a4be0), IPSetConfigV6:(*ipsets.IPVersionConfig)(0xc0003a4cd0), WorkloadIfacePrefixes:[]string{"cali"}, IptablesMarkAccept:0x10000, IptablesMarkPass:0x20000, IptablesMarkScratch0:0x40000, IptablesMarkScratch1:0x80000, IptablesMarkEndpoint:0xfff00000, IptablesMarkNonCaliEndpoint:0x100000, KubeNodePortRanges:[]numorstring.Port{numorstring.Port{MinPort:0x7530, MaxPort:0x7fff, PortName:""}}, KubeIPVSSupportEnabled:false, OpenStackMetadataIP:net.IP(nil), OpenStackMetadataPort:0x2247, OpenStackSpecialCasesEnabled:false, VXLANEnabled:false, VXLANPort:4789, VXLANVNI:4096, IPIPEnabled:false, IPIPTunnelAddress:net.IP{0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xff, 0xff, 0x64, 0x60, 0x1, 0x1}, VXLANTunnelAddress:net.IP(nil), IptablesLogPrefix:"calico-packet", EndpointToHostAction:"ACCEPT", IptablesFilterAllowAction:"ACCEPT", IptablesMangleAllowAction:"ACCEPT", FailsafeInboundHostPorts:[]config.ProtoPort{config.ProtoPort{Protocol:"tcp", Port:0x16}, config.ProtoPort{Protocol:"udp", Port:0x44}, config.ProtoPort{Protocol:"tcp", Port:0xb3}, config.ProtoPort{Protocol:"tcp", Port:0x94b}, config.ProtoPort{Protocol:"tcp", Port:0x94c}, config.ProtoPort{Protocol:"tcp", Port:0x1a0a}, config.ProtoPort{Protocol:"tcp", Port:0x1a0b}}, FailsafeOutboundHostPorts:[]config.ProtoPort{config.ProtoPort{Protocol:"udp", Port:0x35}, config.ProtoPort{Protocol:"udp", Port:0x43}, config.ProtoPort{Protocol:"tcp", Port:0xb3}, config.ProtoPort{Protocol:"tcp", Port:0x94b}, config.ProtoPort{Protocol:"tcp", Port:0x94c}, config.ProtoPort{Protocol:"tcp", Port:0x1a0a}, config.ProtoPort{Protocol:"tcp", Port:0x1a0b}}, DisableConntrackInvalid:false, NATPortRange:numorstring.Port{MinPort:0x8000, MaxPort:0xffff, PortName:""}, IptablesNATOutgoingInterfaceFilter:"", NATOutgoingAddress:net.IP(nil)}
2019-11-12 15:47:44.745 [INFO][19004] rule_defs.go 304: Workload to host packets will be accepted.
2019-11-12 15:47:44.745 [INFO][19004] rule_defs.go 318: filter table allowed packets will be accepted immediately.
2019-11-12 15:47:44.745 [INFO][19004] rule_defs.go 326: mangle table allowed packets will be accepted immediately.
2019-11-12 15:47:44.748 [INFO][19004] feature_detect.go 110: Updating detected iptables features features=iptables.Features{SNATFullyRandom:true, MASQFullyRandom:true, RestoreSupportsLock:true} iptablesVersion=1.8.2 kernelVersion=4.12.14
2019-11-12 15:47:44.748 [INFO][19004] table.go 444: Looked up iptables command backendMode="legacy" candidates=[]string{"iptables-legacy-restore", "iptables-restore"} command="iptables-legacy-restore" ipVersion=0x4 saveOrRestore="restore"
2019-11-12 15:47:44.748 [INFO][19004] table.go 444: Looked up iptables command backendMode="legacy" candidates=[]string{"iptables-legacy-save", "iptables-save"} command="iptables-legacy-save" ipVersion=0x4 saveOrRestore="save"
2019-11-12 15:47:44.749 [INFO][19004] table.go 444: Looked up iptables command backendMode="legacy" candidates=[]string{"iptables-legacy-restore", "iptables-restore"} command="iptables-legacy-restore" ipVersion=0x4 saveOrRestore="restore"
2019-11-12 15:47:44.749 [INFO][19004] table.go 444: Looked up iptables command backendMode="legacy" candidates=[]string{"iptables-legacy-save", "iptables-save"} command="iptables-legacy-save" ipVersion=0x4 saveOrRestore="save"
2019-11-12 15:47:44.750 [INFO][19004] table.go 444: Looked up iptables command backendMode="legacy" candidates=[]string{"iptables-legacy-restore", "iptables-restore"} command="iptables-legacy-restore" ipVersion=0x4 saveOrRestore="restore"
2019-11-12 15:47:44.750 [INFO][19004] table.go 444: Looked up iptables command backendMode="legacy" candidates=[]string{"iptables-legacy-save", "iptables-save"} command="iptables-legacy-save" ipVersion=0x4 saveOrRestore="save"
2019-11-12 15:47:44.750 [INFO][19004] table.go 444: Looked up iptables command backendMode="legacy" candidates=[]string{"iptables-legacy-restore", "iptables-restore"} command="iptables-legacy-restore" ipVersion=0x4 saveOrRestore="restore"
2019-11-12 15:47:44.750 [INFO][19004] table.go 444: Looked up iptables command backendMode="legacy" candidates=[]string{"iptables-legacy-save", "iptables-save"} command="iptables-legacy-save" ipVersion=0x4 saveOrRestore="save"
2019-11-12 15:47:44.750 [INFO][19004] route_table.go 158: Calculated interface name regexp regex="^cali.*"
2019-11-12 15:47:44.750 [INFO][19004] int_dataplane.go 360: Checking if we need to clean up the VXLAN device
2019-11-12 15:47:44.751 [WARNING][19004] int_dataplane.go 362: Failed to query VXLAN device error=Link not found
2019-11-12 15:47:44.751 [INFO][19004] int_dataplane.go 386: XDP acceleration disabled.
2019-11-12 15:47:44.789 [WARNING][19004] int_dataplane.go 392: Failed to cleanup preexisting XDP state error=failed to load BPF program (/tmp/felix-bpf-658800079): stat /sys/fs/bpf/calico/xdp/prefilter_v1_calico_tmp_A: no such file or directory
2019-11-12 15:47:44.793 [INFO][19004] ipsets.go 119: Queueing IP set for creation family="inet" setID="all-ipam-pools" setType="hash:net"
2019-11-12 15:47:44.793 [INFO][19004] ipsets.go 119: Queueing IP set for creation family="inet" setID="masq-ipam-pools" setType="hash:net"
2019-11-12 15:47:44.793 [INFO][19004] int_dataplane.go 542: Registering to report health.
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-failsafe-in" ipVersion=0x4 table="raw"
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-failsafe-out" ipVersion=0x4 table="raw"
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-PREROUTING" ipVersion=0x4 table="raw"
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-OUTPUT" ipVersion=0x4 table="raw"
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-FORWARD" ipVersion=0x4 table="filter"
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-INPUT" ipVersion=0x4 table="filter"
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-wl-to-host" ipVersion=0x4 table="filter"
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-failsafe-in" ipVersion=0x4 table="filter"
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-OUTPUT" ipVersion=0x4 table="filter"
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-failsafe-out" ipVersion=0x4 table="filter"
2019-11-12 15:47:44.794 [INFO][19004] int_dataplane.go 687: IPIP disabled. Not starting tunnel update thread.
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-PREROUTING" ipVersion=0x4 table="nat"
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-POSTROUTING" ipVersion=0x4 table="nat"
2019-11-12 15:47:44.794 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-OUTPUT" ipVersion=0x4 table="nat"
2019-11-12 15:47:44.795 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-failsafe-in" ipVersion=0x4 table="mangle"
2019-11-12 15:47:44.795 [INFO][19004] table.go 475: Queueing update of chain. chainName="cali-PREROUTING" ipVersion=0x4 table="mangle"
2019-11-12 15:47:44.795 [INFO][19004] daemon.go 300: Connect to the dataplane driver.
2019-11-12 15:47:44.795 [INFO][19004] daemon.go 350: Connecting to Typha. addr="<IP_ADDRESS>:5473"
2019-11-12 15:47:44.795 [INFO][19004] sync_client.go 70:  requiringTLS=false
2019-11-12 15:47:44.795 [INFO][19004] daemon.go 372: Created Syncer syncer=<nil>
2019-11-12 15:47:44.795 [INFO][19004] calc_graph.go 110: Creating calculation graph, filtered to hostname local-az-worker-suse-84f78947bf-hlsbt
2019-11-12 15:47:44.795 [INFO][19004] dispatcher.go 68: Registering listener for type model.WorkloadEndpointKey: (dispatcher.UpdateHandler)(0x132e4a0)
2019-11-12 15:47:44.795 [INFO][19004] dispatcher.go 68: Registering listener for type model.HostEndpointKey: (dispatcher.UpdateHandler)(0x132e4a0)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.WorkloadEndpointKey: (dispatcher.UpdateHandler)(0x132e580)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.HostEndpointKey: (dispatcher.UpdateHandler)(0x132e580)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.WorkloadEndpointKey: (dispatcher.UpdateHandler)(0x132e370)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.HostEndpointKey: (dispatcher.UpdateHandler)(0x132e370)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.PolicyKey: (dispatcher.UpdateHandler)(0x132e370)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.ProfileRulesKey: (dispatcher.UpdateHandler)(0x132e370)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.ProfileLabelsKey: (dispatcher.UpdateHandler)(0x132e370)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.ProfileTagsKey: (dispatcher.UpdateHandler)(0x132e370)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.ProfileTagsKey: (dispatcher.UpdateHandler)(0x1289640)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.ProfileLabelsKey: (dispatcher.UpdateHandler)(0x1289640)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.WorkloadEndpointKey: (dispatcher.UpdateHandler)(0x1289640)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.HostEndpointKey: (dispatcher.UpdateHandler)(0x1289640)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.NetworkSetKey: (dispatcher.UpdateHandler)(0x1289640)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.PolicyKey: (dispatcher.UpdateHandler)(0x132e7d0)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.WorkloadEndpointKey: (dispatcher.UpdateHandler)(0x132e7d0)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.HostEndpointKey: (dispatcher.UpdateHandler)(0x132e7d0)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.HostIPKey: (dispatcher.UpdateHandler)(0x132e6f0)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.IPPoolKey: (dispatcher.UpdateHandler)(0x132e6f0)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.GlobalConfigKey: (dispatcher.UpdateHandler)(0x132e610)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.HostConfigKey: (dispatcher.UpdateHandler)(0x132e610)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.ReadyFlagKey: (dispatcher.UpdateHandler)(0x132e610)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.ProfileLabelsKey: (dispatcher.UpdateHandler)(0x132e920)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.HostIPKey: (dispatcher.UpdateHandler)(0x132e9b0)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.WorkloadEndpointKey: (dispatcher.UpdateHandler)(0x132e9b0)
2019-11-12 15:47:44.796 [INFO][19004] dispatcher.go 68: Registering listener for type model.HostEndpointKey: (dispatcher.UpdateHandler)(0x132e9b0)
2019-11-12 15:47:44.797 [INFO][19004] dispatcher.go 68: Registering listener for type model.HostConfigKey: (dispatcher.UpdateHandler)(0x132e9b0)
2019-11-12 15:47:44.797 [INFO][19004] daemon.go 443: Starting the Typha connection
2019-11-12 15:47:44.797 [INFO][19004] sync_client.go 169: Starting Typha client
2019-11-12 15:47:44.797 [INFO][19004] sync_client.go 70:  requiringTLS=false
2019-11-12 15:47:44.797 [INFO][19004] sync_client.go 218: Connecting to Typha. address="<IP_ADDRESS>:5473" connID=0x0 type=""
2019-11-12 15:47:44.798 [INFO][19004] int_dataplane.go 774: Started internal iptables dataplane driver loop
2019-11-12 15:47:44.798 [INFO][19004] int_dataplane.go 784: Will refresh IP sets on timer interval=1m30s
2019-11-12 15:47:44.798 [INFO][19004] int_dataplane.go 794: Will refresh routes on timer interval=1m30s
2019-11-12 15:47:44.798 [INFO][19004] int_dataplane.go 1219: Started internal status report thread
2019-11-12 15:47:44.798 [INFO][19004] int_dataplane.go 1221: Process status reports disabled
2019-11-12 15:47:44.798 [INFO][19004] iface_monitor.go 89: Interface monitoring thread started.
2019-11-12 15:47:44.798 [INFO][19004] iface_monitor.go 96: Subscribed to netlink updates.
2019-11-12 15:47:44.801 [INFO][19004] int_dataplane.go 589: Linux interface state changed. ifaceName="lo" state="up"
2019-11-12 15:47:44.801 [INFO][19004] int_dataplane.go 622: Linux interface addrs changed. addrs=set.mapSet{"<IP_ADDRESS>":set.empty{}, "::1":set.empty{}} ifaceName="lo"
2019-11-12 15:47:44.801 [INFO][19004] int_dataplane.go 589: Linux interface state changed. ifaceName="eth0" state="up"
2019-11-12 15:47:44.801 [INFO][19004] int_dataplane.go 622: Linux interface addrs changed. addrs=set.mapSet{"<IP_ADDRESS>":set.empty{}, "fe80::20d:3aff:fea9:8a6b":set.empty{}} ifaceName="eth0"
2019-11-12 15:47:44.801 [INFO][19004] int_dataplane.go 622: Linux interface addrs changed. addrs=set.mapSet{"<IP_ADDRESS>":set.empty{}, "fe80::42:1eff:fee2:e90d":set.empty{}} ifaceName="docker0"
2019-11-12 15:47:44.801 [INFO][19004] int_dataplane.go 589: Linux interface state changed. ifaceName="cali94829a5722f" state="up"
2019-11-12 15:47:44.801 [INFO][19004] sync_client.go 233: Connected to Typha. address="<IP_ADDRESS>:5473" connID=0x0 type=""
2019-11-12 15:47:44.802 [INFO][19004] async_calc_graph.go 229: Starting AsyncCalcGraph
2019-11-12 15:47:44.802 [INFO][19004] daemon.go 472: Started the processing graph
2019-11-12 15:47:44.802 [INFO][19004] daemon.go 832: Reading from dataplane driver pipe...
2019-11-12 15:47:44.802 [INFO][19004] sync_client.go 268: Started Typha client main loop address="<IP_ADDRESS>:5473" connID=0x0 type=""
2019-11-12 15:47:44.802 [INFO][19004] async_calc_graph.go 134: AsyncCalcGraph running
2019-11-12 15:47:44.802 [INFO][19004] int_dataplane.go 622: Linux interface addrs changed. addrs=set.mapSet{"fe80::ecee:eeff:feee:eeee":set.empty{}} ifaceName="cali94829a5722f"
2019-11-12 15:47:44.803 [INFO][19004] int_dataplane.go 835: Received interface update msg=&intdataplane.ifaceUpdate{Name:"lo", State:"up"}
2019-11-12 15:47:44.803 [INFO][19004] int_dataplane.go 835: Received interface update msg=&intdataplane.ifaceUpdate{Name:"eth0", State:"up"}
2019-11-12 15:47:44.803 [INFO][19004] int_dataplane.go 835: Received interface update msg=&intdataplane.ifaceUpdate{Name:"cali94829a5722f", State:"up"}
2019-11-12 15:47:44.803 [INFO][19004] daemon.go 565: No driver process to monitor
2019-11-12 15:47:44.803 [INFO][19004] int_dataplane.go 850: Received interface addresses update msg=&intdataplane.ifaceAddrsUpdate{Name:"lo", Addrs:set.mapSet{"<IP_ADDRESS>":set.empty{}, "::1":set.empty{}}}
2019-11-12 15:47:44.803 [INFO][19004] hostip_mgr.go 84: Interface addrs changed. update=&intdataplane.ifaceAddrsUpdate{Name:"lo", Addrs:set.mapSet{"::1":set.empty{}, "<IP_ADDRESS>":set.empty{}}}
2019-11-12 15:47:44.803 [INFO][19004] ipsets.go 119: Queueing IP set for creation family="inet" setID="this-host" setType="hash:ip"
2019-11-12 15:47:44.804 [INFO][19004] int_dataplane.go 850: Received interface addresses update msg=&intdataplane.ifaceAddrsUpdate{Name:"eth0", Addrs:set.mapSet{"<IP_ADDRESS>":set.empty{}, "fe80::20d:3aff:fea9:8a6b":set.empty{}}}
2019-11-12 15:47:44.804 [INFO][19004] hostip_mgr.go 84: Interface addrs changed. update=&intdataplane.ifaceAddrsUpdate{Name:"eth0", Addrs:set.mapSet{"<IP_ADDRESS>":set.empty{}, "fe80::20d:3aff:fea9:8a6b":set.empty{}}}
2019-11-12 15:47:44.804 [INFO][19004] ipsets.go 119: Queueing IP set for creation family="inet" setID="this-host" setType="hash:ip"
2019-11-12 15:47:44.804 [INFO][19004] sync_client.go 325: Server hello message received address="<IP_ADDRESS>:5473" connID=0x0 serverVersion="v3.8.2" type=""
2019-11-12 15:47:44.804 [INFO][19004] int_dataplane.go 850: Received interface addresses update msg=&intdataplane.ifaceAddrsUpdate{Name:"docker0", Addrs:set.mapSet{"<IP_ADDRESS>":set.empty{}, "fe80::42:1eff:fee2:e90d":set.empty{}}}
2019-11-12 15:47:44.804 [INFO][19004] hostip_mgr.go 84: Interface addrs changed. update=&intdataplane.ifaceAddrsUpdate{Name:"docker0", Addrs:set.mapSet{"<IP_ADDRESS>":set.empty{}, "fe80::42:1eff:fee2:e90d":set.empty{}}}
2019-11-12 15:47:44.804 [INFO][19004] ipsets.go 119: Queueing IP set for creation family="inet" setID="this-host" setType="hash:ip"
2019-11-12 15:47:44.805 [INFO][19004] int_dataplane.go 850: Received interface addresses update msg=&intdataplane.ifaceAddrsUpdate{Name:"cali94829a5722f", Addrs:set.mapSet{"fe80::ecee:eeff:feee:eeee":set.empty{}}}
2019-11-12 15:47:44.805 [INFO][19004] hostip_mgr.go 84: Interface addrs changed. update=&intdataplane.ifaceAddrsUpdate{Name:"cali94829a5722f", Addrs:set.mapSet{"fe80::ecee:eeff:feee:eeee":set.empty{}}}
2019-11-12 15:47:44.805 [INFO][19004] int_dataplane.go 820: Received *proto.ConfigUpdate update from calculation graph msg=config:<key:"CalicoVersion" value:"v3.8.2" > config:<key:"ClusterGUID" value:"5075b44df893404da853f337a40d18a1" > config:<key:"ClusterType" value:"k8s,bgp,kdd,typha" > config:<key:"DatastoreType" value:"kubernetes" > config:<key:"DefaultEndpointToHostAction" value:"ACCEPT" > config:<key:"FelixHostname" value:"local-az-worker-suse-84f78947bf-hlsbt" > config:<key:"HealthEnabled" value:"true" > config:<key:"IpInIpEnabled" value:"false" > config:<key:"IpInIpMtu" value:"1440" > config:<key:"IpInIpTunnelAddr" value:"<IP_ADDRESS>" > config:<key:"Ipv6Support" value:"false" > config:<key:"LogFilePath" value:"None" > config:<key:"LogSeverityFile" value:"None" > config:<key:"LogSeverityScreen" value:"info" > config:<key:"LogSeveritySys" value:"None" > config:<key:"MetadataAddr" value:"None" > config:<key:"NATPortRange" value:"32768:65535" > config:<key:"ReportingIntervalSecs" value:"0" > config:<key:"TyphaK8sServiceName" value:"calico-typha" >
2019-11-12 15:47:46.895 [INFO][19004] health.go 178: Overall health status changed lastSummary=&health.HealthReport{Live:true, Ready:false}
2019-11-12 15:47:46.895 [WARNING][19004] health.go 190: Reporter failed readiness checks name="int_dataplane" reporter-state=&health.reporterState{name:"int_dataplane", reports:health.HealthReport{Live:true, Ready:true}, timeout:20000000000, latest:health.HealthReport{Live:true, Ready:false}, timestamp:time.Time{wall:0xbf6ad2e82f9a7e30, ext:272513101, loc:(*time.Location)(0x2b314c0)}}
2019-11-12 15:47:46.895 [WARNING][19004] health.go 190: Reporter failed readiness checks name="async_calc_graph" reporter-state=&health.reporterState{name:"async_calc_graph", reports:health.HealthReport{Live:true, Ready:true}, timeout:20000000000, latest:health.HealthReport{Live:true, Ready:false}, timestamp:time.Time{wall:0xbf6ad2e82fdc2f60, ext:276818301, loc:(*time.Location)(0x2b314c0)}}
2019-11-12 15:48:14.804 [ERROR][19004] sync_client.go 260: Failed to read from server address="<IP_ADDRESS>:5473" connID=0x0 error=read tcp <IP_ADDRESS>:46700-><IP_ADDRESS>:5473: i/o timeout type=""
2019-11-12 15:48:14.805 [INFO][19004] sync_client.go 155: Typha client Context asked us to exit connID=0x0 type=""
2019-11-12 15:48:14.806 [WARNING][19004] daemon.go 592: Felix is shutting down reason="Connection to Typha failed"
2019-11-12 15:48:14.806 [INFO][19004] daemon.go 632: Sleeping to avoid tight restart loop. reason="Connection to Typha failed"
2019-11-12 15:48:16.806 [FATAL][19004] daemon.go 641: Exiting. reason="Connection to Typha failed"

calicoctl-node-status from the container running calico
$ calicoctl node status
Calico process is running.

None of the BGP backend processes (BIRD or GoBGP) are running.

calicoctl-node-status from the node hosting calico-node container
$ calicoctl node status
Calico process is running.

None of the BGP backend processes (BIRD or GoBGP) are running.

calicoctl-get-node from the container running calico
$ calicoctl get node
NAME
local-az-worker-suse-84f78947bf-7hwh9
local-az-worker-suse-84f78947bf-hlsbt

calicoctl-node-checksystem from the container running calico
$ calicoctl node checksystem
Checking kernel version...
                4.12.14-197.21-default                                  OK
Checking kernel modules...
                xt_set                                                  OK
                ip6_tables                                              OK
System meets minimum system requirements to run Calico!

calicoctl-node-diags from the container running calico
diag.tar.gz

In both your original post and the latest, calico-node logs in the connection error show something like <IP_ADDRESS>:46700-><IP_ADDRESS>:5473. Seems like calico-node is coming from the node internal address but for some reason the address calico-node is getting for typha is at (I'm assuming) an external address.

@tmjd thanks for looking into the logs. <IP_ADDRESS> is the internal IP of the node, as you see, and <IP_ADDRESS> is the IP of the ClusterIP Service exposing calico-typha.

@fasaxc why is node trying to connect to the service IP of typha? It should be fetching the endpoints and connecting directly.

That's what I thought but now I check the code it's not what we do.  We do connect to the cluster IP and let kube-proxy do the load balancing.  D'oh!

I don't understand how access from a host (with node on it) to typha can work but access from the node on the same host to typha would fail. The Node pod is ran as hostNetwork so it uses the same network namespace as the host, both are using the service IP, there is no DNS involved.
I think you'll need to try access from both and collect traffic with tcpdump and see where the difference is (where the traffic is being blocked/failing/dropped).

@marwinski and @zanetworker joined into debugging this issue.
It turns out that SUSE by default uses MTU of 9000 which is too high, thus the communication between calico nodes and typha is not reliable(lost packets).
I would like thanks to everybody who took part into this issue.


Create searching_bst.cpp

Description
we want to search for the number, what we’ll do is we’ll start at the root, and then we will compare
the value to be searched with the value of the root if it’s equal we are done with the search if it’s lesser
we know that we need to go to the left subtree because in a binary search tree all the elements in the left
subtree are lesser and all the elements in the right subtree are greater.
Fixes #1556
Replace issue_no with the issue number which is fixed in this PR
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

sir, i made a pr, please check sir @Ayush7614  @Amit366


Connect

How do I put it to appear on phone?

This version is for touchscreen external displays or for in-pc use.
Android version was removed for nova macros for now, you can still use macros created within this app with similar apps like macro deck (recommended).


fix points write panic

fix index out of range risk, log here:
[wal] 2015/10/28 11:39:55 write to index of partition 1 took 3.516488ms
[wal] 2015/10/28 11:40:05 Flush due to idle. Flushing 8 series with 8 points and 424 bytes from partition 1
[wal] 2015/10/28 11:40:05 write to index of partition 1 took 3.126415ms
[wal] 2015/10/28 11:40:15 Flush due to idle. Flushing 8 series with 8 points and 424 bytes from partition 1
[wal] 2015/10/28 11:40:15 write to index of partition 1 took 1.716188ms
[http] 2015/10/28 11:40:25 <IP_ADDRESS> - - [28/Oct/2015:11:40:25 +0800] POST /write HTTP/1.1 400 57 - Mozilla/5.0 (Macintosh; Intel Mac
OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36 9facaff5-7d25-11e5-8001-000000000000 2.522487ms
[wal] 2015/10/28 11:40:25 Flush due to idle. Flushing 8 series with 8 points and 424 bytes from partition 1
[wal] 2015/10/28 11:40:25 write to index of partition 1 took 12.511171ms
[wal] 2015/10/28 11:40:35 Flush due to idle. Flushing 8 series with 8 points and 442 bytes from partition 1
[wal] 2015/10/28 11:40:35 write to index of partition 1 took 7.997816ms
[http] 2015/10/28 11:40:38 <IP_ADDRESS> - - [28/Oct/2015:11:40:38 +0800] POST /write HTTP/1.1 400 45 - Mozilla/5.0 (Macintosh; Intel Mac
OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36 a776548d-7d25-11e5-8002-000000000000 19.391701ms
[wal] 2015/10/28 11:40:45 Flush due to idle. Flushing 8 series with 8 points and 442 bytes from partition 1
[wal] 2015/10/28 11:40:45 write to index of partition 1 took 1.890025ms
[http] 2015/10/28 11:40:50 <IP_ADDRESS> - - [28/Oct/2015:11:40:50 +0800] POST /write HTTP/1.1 200 23 - Mozilla/5.0 (Macintosh; Intel Mac
OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36 af16a5b9-7d25-11e5-8003-000000000000 1.222898ms [pan
ic:runtime error: index out of range]

@oiooj -- can you please run the test suite locally before pushing up any further commits? That way you will get the quickest turnaround when debugging your code.

@otoolep  sure, I have ran the test file.
$ go test points_test.go
ok      command-line-arguments  0.013s

$ go test handler_test.go
ok      command-line-arguments  0.019s

It is right ?

I don't know, depends if you are are in the correct directory.
$ ls
balancer.go       circle-test.sh  cmd                       DOCKER.md  influxql                    Makefile  nightly.sh  README.md  snapshot  test-32bit-docker.sh  uuid
balancer_test.go  circle.yml      CONTRIBUTING.md           errors.go  influxvar.go                meta      package.sh  scripts    statik    tests
build-docker.sh   client          Dockerfile                etc        LICENSE                     models    pkg         services   stress    toml
CHANGELOG.md      cluster         Dockerfile_test_ubuntu32  importer   LICENSE_OF_DEPENDENCIES.md  monitor   QUERIES.md  shared     tcp       tsdb
$ cd models/
$ go test -run TestParsePointNoValue
PASS
ok      github.com/influxdb/influxdb/models     0.001s

will run the test that is failing on Circle.

No problem here, I don't know what's going on.  Always failed on Circle.
Sosara@MBA:~/golang/src/github.com/oiooj/influxdb/models$ go test -run TestParsePointNoValue
PASS
ok      github.com/oiooj/influxdb/models        0.010s

@otoolep fixed , Thanks

Thanks @oiooj.
Can you please rebase and squash the commits, with a single commit?

Can you also add a test case for this? We really need test cases for every change.

rebased the commits , I reviewed handler_test.go source, This is a post and write data request, It's difficult to add a test case.

I believe I follow what this patch fixes, but I'd like a second set of eyes.
@corylanou ?

Yes this appears to make sense.  We should add a test though so that we don't regress.  Once a test is added, +1.  Thanks!

Closing in favour https://github.com/influxdb/influxdb/pull/4625


Anyway to build with Makefiles?

Is there any way that you could provide a build method using Makefiles? that way it would be simpler to build on Linux machines.
Just for the MarchingCubes projects

Unfortunately I don't have a CUDA linux dev setup at hand currently.


Add ausdg.us and alamedaunified.org

ausdg.us - Student Domain for AUSD (Alameda Unified School District)
alamedaunified.org - teacher and faculty domain for AUSD

@Expzr Thank you for your patience while waiting for a review and processing your request. Pull request merged.


selection.transition(transitionInstance) doesn't inherit timing properties

From the selection.transition([name]) docs:

If the name is a transition instance, the returned transition has the same id and name as the specified transition. If a transition with the same id already exists on a selected element, the existing transition is returned for that element. Otherwise, the timing of the returned transition is inherited from the existing transition of the same id on the nearest ancestor of each selected element.

And the example given:
var t = d3.transition()
    .duration(750)
    .ease(d3.easeLinear);

d3.selectAll(".apple").transition(t)
    .style("fill", "red");

d3.selectAll(".orange").transition(t)
    .style("fill", "orange");

My understanding is that the transitions applied to ".orange" and ".apple" elements should inherit the 750ms duration and linear easing from transition t. However, they appear use the d3 default transition properties instead.
See this Fiddle for example.
Am I misunderstanding how to use transition inheritance, or are the docs incorrect?

Actually, as soon as I posted this I went on the hunt for source issue and it seems like this was addressed in https://github.com/d3/d3-transition/issues/40 but those changes are in v4-alpha! I'm still on 3.5.17... Sorry for the noise - closing this.

@bclinkinbeard Transitions are destroyed after they end, so you can’t inherit a transition that’s ended. Thus if you call changed within the first five seconds of page load, it will inherit the five-second duration, but it won’t if you call it after—it’ll fallback to the default duration because the specified transition isn’t found on an ancestor element.
Arguably the bug in that if the specified transition-to-inherit-from is not found, it should throw an Error rather than falling back to the default parameters. That behavior isn’t documented, so it might be reasonable to change it, though I expect some people might be annoyed that there could which worked (albeit incorrectly) is now throwing an error…

Ah, OK, I at least understand it now. I read the docs several times and couldn't really wrap my head around the ancestor/document element stuff.
I guess there is no way to create a reusable transition instance then, because there is no way to create an inert transition? That is what I initially thought transition(t) was doing. Is a factory the best (only?) way to create reusable transitions?

@bclinkinbeard The primary unit of reusability is the function. You can use transition.call to call a function that sets the desired properties on the transition:
function configure(transition) {
  return transition
      .duration(5000)
      .ease(d3.easeLinear);
}

d3.select(document.body)
  .transition()
    .call(configure)
    .style("background-color", "red");

Why doesn't .call() seem to work?

Please be more specific and include a link to an example that demonstrates the issue, preferably on bl.ocks.org. I tested the above examples and they worked fine, and there are unit tests in this repository for transition.call (and likewise selection.call in d3-selection). So just saying something doesn’t work without being specific is unproductive.

Sorry, typing on my phone. Your first example is what I meant by factory so that's 👍. Just curious why call wouldn't work since I thought it can do anything with the selection passed in.

Not sure what you mean; transition.call does work, as shown in my example. Using selection.call would also work, but it always returns the current selection (rather than the return value of the called function), so it can’t easily be used to instantiate a transition and return it for further customization. I’d change the behavior of selection.call to return the return value of the called function but it’d have to wait for D3 5.0.

OK, all clear now. Thanks and sorry again for being vague/short. I should know better than trying to edit and grok JSBins on my phone while out and about. :)


[Windows] "fatal error C1017: invalid integer constant expression" in simd.h

When building a conda package for openimageio on windows, the compilation is failing with:
\src\include\OpenImageIO/simd.h(1789): fatal error C1017: invalid integer constant expression

The build command is
cmake -G "NMake Makefiles" ^
	  -DUSE_FFMPEG=ON ^
	  -DOIIO_BUILD_TOOLS=OFF ^
	  -DOIIO_BUILD_TESTS=OFF ^
	  -DUSE_PYTHON=OFF ^
	  -DUSE_OPENCV=OFF ^
	  -DCMAKE_INSTALL_PREFIX=%LIBRARY_PREFIX% ^
	  -DCMAKE_INSTALL_LIBDIR=lib ^
	  %SRC_DIR%

The compiler in use is MSVC 2015
Versions of dependencies
boost:          1.68.0
ffmpeg:         3.4.2
giflib:         5.1.4
ilmbase:        2.3.0
jpeg:           9c
libpng:         1.6.36
libtiff:        4.0.10
libwebp:        1.0.1
openexr:        2.3.0

I'm not sure why the current line 1789 would produce that error.
Do you know which version of OIIO, possibly even down to which commit hash, was the one you were building?
And do you know what SIMD level or machine it's building for? Like if it's a x86-64, then it's sse2 even if you don't specify sse support.

I've seen this error in the past when trying things like:
#if true (or any define that expands to true or false)
...
#endif
using 0 or 1 instead usually fixes the problem.

Sorry for the inaccuracy. The version that we use is 1.8.9.

#if defined(ILMBASE_VERSION_MAJOR) && ILMBASE_VERSION_MAJOR >= 2

Why is that wrong? Do we think that ILMBASE_VERSION_MAJOR is not defined?

It seems so, in this situation...

This failure occurs on windows when attempting a packaging of openimageio for conda-forge. https://github.com/conda-forge/staged-recipes/pull/7166
I already have a build for another channel, but ilmbase and openexr are packaged differently on conda-forge (they are two well separated packages, while most of the time, windows build are bundle including both.)

So is the problem that it doesn't like
 #if defined(FOO) && FOO >= 2

is not ok even though it appears to be guarded by the defined(FOO) part?
Would it solve this issue to rewrite it like this?
#if defined(ILMBASE_VERSION_MAJOR)
    #if LMBASE_VERSION_MAJOR >= 2
    #endif
#endif

nested rather than compound statements?

But ILMBASE is supposed to be installed. I will do some cmake debugging tomorrow when I can work on a windows machine.
I suspect an issue with the ILMBASE packaging.

The ILMBASE_VERSION_MAJOR should be defined in headers included by OpenEXR/ImathVec.h at the top of my simd.h, so if ilmbase is not installed at all, there should have been a separate failure about not finding the included header.

@SylvainCorlay  Do you have an opinion on what I wrote a couple comments back? Do you think that changing the #if construct slightly as I outlined is likely to help?

@SylvainCorlay Any further thoughts on this?

The OpenEXR installation process should install
include/OpenEXR/IlmBaseConfig.h

and that file should have the macros defined in it. The IlmBase recipe in conda-forge looks good, so if that file is not being written correctly, it's possible there's a bug in IlmBase's autoconf script. I don't have a conda-using system available to me at the moment so I haven't investigated further.

I think everything here is about old versions of OIIO, pre-CMake overhaul of 2019, and old versions of OpenEXR as well. Closing on the assumption that it's probably cleaned up now, and if it weren't more people would be complaining. Please re-open or re-file if it is still a problem on modern versions of everything.


Test: Kube-DNS use kubeadm deploy parameters

Skip some custom parameters, to use the default ones.
Avoid the memory/CPU limits.
Signed-off-by: Eloy Coto<EMAIL_ADDRESS>

This change is

@aanm did you first pull this in? is there a reason to never change it?

@raybejjani what are you talking about exactly? The initial kube-dns file was pulled from here https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/kube-dns/kube-dns.yaml.base


v1.13 Backports 2023-04-12

[ ] #24449 (@MrFreezeex)

Once this PR is merged, you can update the PR labels via:
for pr in 24449; do contrib/backporting/set-labels.py $pr done 1.13; done

or with
make add-labels BRANCH=v1.13 ISSUES=24449

/test-backport-1.13

Wow didn't realize that excluded cidr was not 1.13

yeah I mixed things up, I was sure we backported excluded CIDRs to cilium/cilium v1.13 but that's clearly not the case :sweat:
To avoid dropping some bpf tests I synced them from master (minus the excluded CIDRs bits) in https://github.com/cilium/cilium/pull/24859, I'll rebase this on top of those changes

/test-backport-1.13

/test-backport-1.13

/test-backport-1.13

'Cilium-PR-K8s-1.16-kernel-4.9' failure is expected, we don't support Kernel 4.9 on Cilium v1.13 anymore


np.roll not working in nopython model (CUDA)

Is np.roll currently supported within a cuda.jit function? I get the following error when I call:
np.roll(d, 1) where d is a 1d numpy array. Looks like the overload of np.empty is failing here?
Failed in cuda mode pipeline (step: nopython frontend)
No implementation of function Function(<function roll at 0x7f657cbeeca0>) found for signature:

 >>> roll(array(float32, 1d, C), Literal[int](1))

There are 2 candidate implementations:
      - Of which 2 did not match due to:
      Overload in function 'np_roll': File: numba/np/arraymath.py: Line 2126.
        With argument(s): '(array(float32, 1d, C), int64)':
       Rejected as the implementation raised a specific error:
         TypingError: Failed in nopython mode pipeline (step: nopython frontend)
       No implementation of function Function(<built-in function empty>) found for signature:

        >>> empty(UniTuple(int64 x 1), dtype=dtype(float32))

       There are 4 candidate implementations:
             - Of which 4 did not match due to:
             Overload in function '_OverloadWrapper._build.<locals>.ol_generated': File: numba/core/overload_glue.py: Line 131.
               With argument(s): '(UniTuple(int64 x 1), dtype=dtype(float32))':
              Rejected as the implementation raised a specific error:
                NumbaTypeError: Failed in nopython mode pipeline (step: nopython frontend)
              Only accept returning of array passed into the function as argument
         raised from /home/co1/.conda/envs/superneuro/lib/python3.9/site-packages/numba/core/typed_passes.py:150

       During: resolving callee type: Function(<built-in function empty>)
       During: typing of call at /home/co1/.conda/envs/superneuro/lib/python3.9/site-packages/numba/np/arraymath.py (2133)

       File "../.conda/envs/superneuro/lib/python3.9/site-packages/numba/np/arraymath.py", line 2133:
           def np_roll_impl(a, shift):
               <source elided>
               arr = np.asarray(a)
               out = np.empty(arr.shape, dtype=arr.dtype)
               ^

  raised from /home/co1/.conda/envs/superneuro/lib/python3.9/site-packages/numba/core/typeinfer.py:1086

np.roll is not supported in CUDA. It will be some time before the infrastructure (handling returning a new array from a function) will be available in CUDA. I hope that could be this year, but there's a lot to do to get to that point.

@gmarkall understood, that makes sense. Will resort to a work-around to np.roll until then. Thank you for the clarification!


Pong example: Use blocks for sound resources

Done by using the new feature, dragging the sound resources from the Filesystem dock to the block canvas.
The diff is crazy because resource IDs change all the time, but this is what it looks like now:

I ignored all the resource junk and looked at the generated code diff. Looks about right!


how to get the post requestbody by dynamic ruting？

I just implement a  dynamic ruting  and I need to Verify SQL injection but I only found a way to use RouteLocator, not RouteDefinition  to get the requestBody when I user post method.
how to get the post requestBody by dynamic ruting？
this is my dynamic ruting config:

Thanks for your help；
forgive my poor english；

The filter for getting and modifying the request body is oy available via the Java DSL.

The filter for getting and modifying the request body is oy available via the Java DSL.

Thank you very much！！


[feat] Use PostgreSQL flexible server instead of single server

Single servers are not available in some regions, eg. Frankfurt.

Here is a good comparison:
https://techcommunity.microsoft.com/t5/fasttrack-for-azure/comparison-azure-postgresql-single-server-flexible-server/ba-p/3474966
Some highlights:

"The connection pooler is built-in with flexible server. You can optionally enable it".
You can manually stop the server. Stopped servers will automatically start again after seven days

It is going to be retired: https://learn.microsoft.com/en-us/azure/postgresql/single-server/whats-happening-to-postgresql-single-server


Update the project version to 0.6.0

Signed-off-by: iam-veeramalla<EMAIL_ADDRESS>What type of PR is this?

/kind chore

What does this PR do / why we need it:
Updates the project version to 0.6.0 and generates manifests
Have you updated the necessary documentation?
NA
How to test changes / Special notes to the reviewer:

@iam-veeramalla I discovered that we can generate the serviceMonitor manifest by adding $(KUSTOMIZE) build config/prometheus  to the bundle makefile target
since we will need to generate the serviceMonitor for 0.6 maybe it makes sense to generate that file and add it to this PR


Open swipe options on click on cell

Is there any way to open the swipe options of right swipe by clicking on the cell with keeping the existing behavior.
Any help will appreciated.
Thanks

You can call showSwipe(orientation: .right) from inside of your SwipeTableViewCell.

I want to show it here
func collectionView(_ collectionView: UICollectionView, didSelectItemAt indexPath: IndexPath)
Is it possible?

Can you show me some code snippets for showing the swipe?

Maybe you can try something like this
let cell = collectionView.cellForItem(at: indexPath) as? SwipeCollectionViewCell
cell?.showSwipe(orientation: .right)


Missing padding on My Check-Ins screen

Avoid duplicates

[x] Bug is not mentioned in the FAQ
[x] Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[x] Bug is not already reported in another issue

Describe the bug
Some padding is missing on the Check-In screen while the user is checked in to an event or a location between the duration box and the Check Out Now button.

Device
My QR Codes (has correct padding)
My Check-Ins (has incorrect padding)

1

2

2 with "Small" Font size

As you can see from the screenshots, the exact amount of space that will be between the box and the Checkout button depends on the specific device's configuration, including dpi as well as font size.
Steps to reproduce the issue
Play around with different device configurations on the emulator. Specifically, device "1" is the device profile "Galaxy Nexus" from the Android Emulator toolset, and "2" is the "Pixel 2" preconfiguration.
Expected behavior
Padding should be the same on the My QR Codes screen as on the My Check-Ins screen.

Internal Tracking ID: EXPOSUREAPP-6534

@fynngodau Thanks. Internal Tracking ID: EXPOSUREAPP-6534

Corona-Warn-App Open Source Team

I added new screenshots from the same device with a smaller font size to illustrate that the button can also overlap the duration box on the card. Hence, I think this should be fixed before release.

@fynngodau thanks. added to ticket.

I fixed this in https://github.com/corona-warn-app/cwa-app-android/pull/2826
I wasn't able to get it into 2.0.x though :frowning:

Will be fixed with https://github.com/corona-warn-app/cwa-app-android/pull/2826 by @d4rken.

@d4rken Oh, awesome, thank for the hint. I cherry-picked the commit into CCTG. Closing this issue since it has already been resolved.

@dsarkar / @fynngodau
Could we please re-open this issue since the corresponding fix has not been released yet?
Users keep reporting it and I think most people don't think of looking in the list of closed issues before opening a new issue.

I verified this fixed in the current release 2.1.2.
Pixel 3a, Android 11, CWA 2.1.2

Settings > Display > Advanced
Set Font size to Small
Open CWA
Scroll down to CREATE QR CODE and tap it
Tap NEXT if necessary
Tap + QR CODE
Tap Retail
Enter A in Description and B in Place, Tap SAVE
Tap CHECK IN
Tap ACCEPT if necessary
Tap CHECK IN

The same steps carried out in CWA 2.0.3 result in the CHECK OUT NOW block overlapping the Duration block in the screen "My Check-Ins".

Whilst I was checking this fix, I noticed a new problem which I logged under https://github.com/corona-warn-app/cwa-app-android/issues/3086 "Duration display in Event overflows box with Largest font" which is on the same layout and with the Largest font size.

The padding is still not enough, compared to the My QR Codes view, like seen in the second set of screenshots in my original post.

@fynngodau

The padding is still not enough, compared to the My QR Codes view, like seen in the second set of screenshots in my original post.

I did wonder whether the padding is enough. At least there is no overlap.
So it seems the PR https://github.com/corona-warn-app/cwa-app-android/pull/2826 from @d4rken needs to be revisited for some more tweaking.
It would be good to have feedback about whether a new issue would be cleaner to handle, rather than keeping this one open.

@MikeMcC399 @fynngodau
The issue can stay open for now. The ticket has already been updated.

Corona-Warn-App Open Source Team

@fynngodau
The layout seems to be fixed now. I looked again using CWA 2.19.2

@fynngodau
Perhaps you could take a look to decide if this issue is fixed and can be closed now?

I have just checked the linked Jira issue.
Jira Ticket is flagged as:
Resolution: Wont Fix
Status: Obsolete
Developer comment:

Depending on the font size, the padding is not enough. I will reopen the ticket.

I think padding isn't the right fix, I would suggest a barrier.

The issue does not seem to exist anymore. Set this ticket to completed.

Sorry for my inactivity here, @MikeMcC399, I did check a while ago and it seemed correct now but I forgot to close the issue accordingly. Thanks for closing, @svengabr.


add Network.Moran method

This PR partially addresses #586 by...

adding a Network.Moran method to the code base that was previously only found in the Tutorials;
add tests for the Network.Moran method;
rerunning notebooks.

@slumnitz @knaaptime @jeffcsauer @sjsrey
I am having a tough time diagnosing this failure. Any thoughts/advice/etc. would be super.

new Moran method that calls esda.Moran (originally found in a tutorial)
moran tests passing on macOS & Windows — Python 3.6, 3.7, 3.8, 3.9.
moran tests failing on Ubuntu — Python 3.6, 3.7, 3.8, 3.9.
within esda itself Moran is being successfully tested on all three platform & Python 3.6-8

@slumnitz @knaaptime @jeffcsauer @sjsrey
I am having a tough time diagnosing this failure. Any thoughts/advice/etc. would be super.

new Moran method that calls esda.Moran (originally found in a tutorial)
moran tests passing on macOS & Windows — Python 3.6, 3.7, 3.8, 3.9.
moran tests failing on Ubuntu — Python 3.6, 3.7, 3.8, 3.9.
within esda itself Moran is being successfully tested on all three platform & Python 3.6-8

y values [1263c8b] (observation counts along arcs) and dict sorting [9f02ea1] don't appear to be the problem. Maybe it's something in numpy or scipy.stats that causing this down from within esda... but then again CI is still passing for esda. I'm at a loss.

y values [1263c8b] (observation counts along arcs) and dict sorting [9f02ea1] don't appear to be the problem. Maybe it's something in numpy or scipy.stats that causing this down from within esda... but then again CI is still passing for esda. I'm at a loss.

Could this be a ubuntu specific issue? As you noted, it's passing on macOS and Windows. I can try to spin up a ubuntu vm in a bit and see what's going on

Could this be a ubuntu specific issue? As you noted, it's passing on macOS and Windows. I can try to spin up a ubuntu vm in a bit and see what's going on

Could this be a ubuntu specific issue? As you noted, it's passing on macOS and Windows. I can try to spin up a ubuntu vm in a bit and see what's going on

Yeah, I would be surprised at this point if it wasn't an Ubuntu specific issue.

Could this be a ubuntu specific issue? As you noted, it's passing on macOS and Windows. I can try to spin up a ubuntu vm in a bit and see what's going on

Yeah, I would be surprised at this point if it wasn't an Ubuntu specific issue.

got an Ubuntu machine up. here is a quick gist "demonstrating" incorrect result on Ubuntu.

got an Ubuntu machine up. here is a quick gist "demonstrating" incorrect result on Ubuntu.

@jGaboardi have not fully diagnosed the issue, but identified at least one place within the Moran.py function where calculations start to diverge. Specifically:
 def __calc(self, z):
        zl = slag(self.w, z)
        print(zl[0])

First few numbers from Windows:
0.05280528052805272
11.471452145214515
0.5528052805280528
91.44042904290428

First few numbers from Ubuntu:
0.05280528052805272
9.136413641364133
-0.19719471947194722
29.333388338833892

True divergence in the function might start earlier, that was just the most crucial calculation that jumped out at me as likely being different (lucky guess?).
Here are my watermarks:
Windows:
Last updated: 2021-01-26T21:54:05.283616-06:00

Python implementation: CPython
Python version       : 3.8.3
IPython version      : 7.16.1

Compiler    : MSC v.1924 64 bit (AMD64)
OS          : Windows
Release     : 10
Machine     : AMD64
Processor   : Intel64 Family 6 Model 158 Stepping 9, GenuineIntel
CPU cores   : 8
Architecture: 64bit

Watermark: 2.1.0

esda     : 2.3.6
libpysal : 4.3.0
numpy    : 1.19.0
scipy    : 1.5.1
spaghetti: 1.5.0

Ubuntu:
Last updated: 2021-01-26T14:56:44.334798-06:00

Python implementation: CPython
Python version       : 3.8.7
IPython version      : 7.19.0

Compiler    : GCC 5.4.0 20160609
OS          : Linux
Release     : 4.4.0-19041-Microsoft
Machine     : x86_64
Processor   : x86_64
CPU cores   : 8
Architecture: 64bit

Watermark: 2.1.0

esda     : 2.3.6
numpy    : 1.19.5
scipy    : 1.6.0
spaghetti: 1.5.6
libpysal : 4.3.5

I'll keep looking into it.

@jGaboardi have not fully diagnosed the issue, but identified at least one place within the Moran.py function where calculations start to diverge. Specifically:
 def __calc(self, z):
        zl = slag(self.w, z)
        print(zl[0])

First few numbers from Windows:
0.05280528052805272
11.471452145214515
0.5528052805280528
91.44042904290428

First few numbers from Ubuntu:
0.05280528052805272
9.136413641364133
-0.19719471947194722
29.333388338833892

True divergence in the function might start earlier, that was just the most crucial calculation that jumped out at me as likely being different (lucky guess?).
Here are my watermarks:
Windows:
Last updated: 2021-01-26T21:54:05.283616-06:00

Python implementation: CPython
Python version       : 3.8.3
IPython version      : 7.16.1

Compiler    : MSC v.1924 64 bit (AMD64)
OS          : Windows
Release     : 10
Machine     : AMD64
Processor   : Intel64 Family 6 Model 158 Stepping 9, GenuineIntel
CPU cores   : 8
Architecture: 64bit

Watermark: 2.1.0

esda     : 2.3.6
libpysal : 4.3.0
numpy    : 1.19.0
scipy    : 1.5.1
spaghetti: 1.5.0

Ubuntu:
Last updated: 2021-01-26T14:56:44.334798-06:00

Python implementation: CPython
Python version       : 3.8.7
IPython version      : 7.19.0

Compiler    : GCC 5.4.0 20160609
OS          : Linux
Release     : 4.4.0-19041-Microsoft
Machine     : x86_64
Processor   : x86_64
CPU cores   : 8
Architecture: 64bit

Watermark: 2.1.0

esda     : 2.3.6
numpy    : 1.19.5
scipy    : 1.6.0
spaghetti: 1.5.6
libpysal : 4.3.5

I'll keep looking into it.

@jeffcsauer This is a nice find and we have something more concrete to focus on. Here is a rehash of our convo on gitter for the sake of openness:

... it looks like it may be happening in spatial_lag.lag_spatial()  (aliased as slag) where w.spraseis present, which is itself being built from weights._build_sparse() and uses scipy.sparse.crs_matrix().

@jeffcsauer This is a nice find and we have something more concrete to focus on. Here is a rehash of our convo on gitter for the sake of openness:

... it looks like it may be happening in spatial_lag.lag_spatial()  (aliased as slag) where w.spraseis present, which is itself being built from weights._build_sparse() and uses scipy.sparse.crs_matrix().

Here is a workflow in macOS and ubuntu demonstrating the same difference in the result for esda.Moran.I for the empirical data, but identical results for small, synthetic data.

Here is a workflow in macOS and ubuntu demonstrating the same difference in the result for esda.Moran.I for the empirical data, but identical results for small, synthetic data.


Issue when using module indirectly using Create-React-App and import

I've struggled with this issue for several hours already, so I'm going to summarize my findings so far and maybe there is something you could help me with.
I currently am providing a package to some other users who are using my package using import syntax.
In the package I provide, I'm using require to load the @adobe/css-tools package, as it seemed to me that it supports both import or require.
I've published a very simple library, called css-wrapper-xxx.
In the css-wrapper-xxx library, I simply wrote, in order to compare how lodash and @adobe/css-tools behave :
const adobe = require("@adobe/css-tools");
const lodash = require("lodash");
module.exports = {adobe, lodash};

I then want to use my "css-wrapper-xxx" library from a Create-React-App project, which you can get up and running using following commands :
git clone https://github.com/edi9999/repro-adobe-css-tools.git
cd repro-adobe-css-tools
npm install
npm start
# open browser on localhost:3000/

When I log the values returned by the css-wrapper-xxx library, for some strange reason, the value for "adobe" is a path and not the object that should've been exported.

assets/2071336/563cf962-6ea0-4be0-8e79-2c94a207d79e)
Expected Behaviour
I would expect the require to work
Actual Behaviour
The require (from css-wrapper-xxx) inside then import (from the create-react-app project) returns a string
Notes / Solutions
I'm not sure whether this issue is directly related to css-tools, or if this is a webpack or even a CreateReactApp issue.

It might be linked to this issue :
https://github.com/facebook/create-react-app/issues/11889

The exact same package is working correctly with Vite.JS