Introduction

I am attempting to upgrade my installation of Openshift-Ansible from 3.6 to a higher version.

Currently, I'm running the following in an attempt to upgrade to v3.7:

ANSIBLE_HOST_KEY_CHECKING=False ansible-playbook -i hosts -k openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_7/upgrade.yml

I get the following failing task when running:

TASK [Check for invalid namespaces and SDN errors] ***********************************************************************************************************************************************************************
fatal: [10.0.0.51]: FAILED! => {"changed": false, "msg": "Failed to GET hostsubnet.", "results": {"cmd": "/usr/bin/oc get hostsubnet -o json -n default", "results": [{}], "returncode": 1, "stderr": "Unable to connect to the server: dial tcp: lookup docker1.foo.bar on 10.0.0.1:53: no such host\n", "stdout": ""}, "state": "list"}

Details

I've checked out the release-3.9 branch of the openshift-ansible project.

For the sake of brevity, I'll post only the portion of my hosts file which I think are relevant, please let me know if I have left out important details:

[OSEv3:children]
masters
nodes
etcd

openshift_master_cluster_method=native
openshift_master_cluster_hostname=10.0.0.51
openshift_master_cluster_public_hostname=10.0.0.51
osm_cluster_network_cidr=10.168.0.0/13

[masters]
10.0.0.51

[etcd]
10.0.0.51

[nodes]
10.0.0.51 openshift_node_labels="{'region': 'infra','zone': 'default','node-role.kubernetes.io/compute': 'true'}" openshift_schedulable=true
10.0.0.52 openshift_node_labels="{'region': 'infra','zone': 'default','node-role.kubernetes.io/compute': 'true'}"
10.0.0.53 openshift_node_labels="{'region': 'infra','zone': 'default','node-role.kubernetes.io/compute': 'true'}"

I think this error may be due to some sort of name resolution error, I have an /etc/resolv.conf inside 10.0.0.53 with the following contents:

nameserver 10.0.0.1
nameserver 10.0.0.53

If I do nslookup docker1.foo.bar 10.0.0.1, I get a failure to find, which is expected because 10.0.0.1 can't resolve internal network names.

If I do docker1.foo.bar 10.0.0.53, I resolve the name to 10.0.0.51 as expected.

What I've Already Done Before this

Initially, when I ran upgrade.retry as above, I got the following error:

TASK [openshift_excluder : Check the available origin-docker-excluder version is at most of the upgrade target version] **********************************************************************
[DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using `result|version_compare` use `result is version_compare`. This feature will be removed in version 2.9. 
Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
fatal: [docker1.foo.bar]: FAILED! => {"changed": false, "msg": "Available origin-docker-excluder version 3.9.0 is higher than the upgrade target version"}
    ...

So, I've added the following to my inventory file:

enable_excluders=false

Which seems to make the playbook continue past this error, then I hit the error as described above in the Introduction.

Question

How can I upgrade my installation of Openshift-Ansible, or, what is causing my error?

I've done ntpq, then ran associations and received the following:

ind assid status  conf reach auth condition  last_event cnt
===========================================================
  1 12097  c811   yes  none   yes    reject    mobilize  1

From the documentation from man ntp-decode (Peer Status), I've learned that the first digit indicates Status, the second Select, the third Count, and the fourth Code.

I've tried to find the Select Status section of this manual and found the following:

The Select Field displays the current selection status. (The T Field in the following table gives the corresponding tally codes used in the ntpq peers dis-
play.) The values are coded as follows:

+-------------------------+---------------------------------------+--------------------------+-------------------------------------------------------------+
|        Code             |            Message                    |            T             |            Description                                      |
+-------------------------+---------------------------------------+--------------------------+-------------------------------------------------------------+
|        0                |            sel_reject                 |                          |            discarded as not valid (TEST10-TEST13)           |
+-------------------------+---------------------------------------+--------------------------+-------------------------------------------------------------+
|        1                |            sel_falsetick              |            x             |            discarded by intersection algorithm              |
+-------------------------+---------------------------------------+--------------------------+-------------------------------------------------------------+
|        2                |            sel_excess                 |            .             |            discarded by table overflow (not used)           |
+-------------------------+---------------------------------------+--------------------------+-------------------------------------------------------------+
|        3                |            sel_outlyer                |            -             |            discarded by the cluster algorithm               |
+-------------------------+---------------------------------------+--------------------------+-------------------------------------------------------------+
|        4                |            sel_candidate              |            +             |            included by the combine algorithm                |
+-------------------------+---------------------------------------+--------------------------+-------------------------------------------------------------+
|        5                |            sel_backup                 |            #             |            backup (more than tos maxclock sources)          |
+-------------------------+---------------------------------------+--------------------------+-------------------------------------------------------------+
|        6                |            sel_sys.peer               |            *             |            system peer                                      |
+-------------------------+---------------------------------------+--------------------------+-------------------------------------------------------------+
|        7                |            sel_pps.peer               |            o             |            PPS peer (when the prefer peer is valid)         |
+-------------------------+---------------------------------------+--------------------------+-------------------------------------------------------------+

So, what does the 8 digit for Select Status mean?

Introduction

I'm trying to do some work in which I must receive an NTP update from peers but I'm concerned that there isn't any being received. Here's the output of ntpq -np:

     remote           refid      st t when poll reach   delay   offset jitter  
==========================================================================
     239.0.1.1       .MCST.          16 u    -   64    0    0.000    0.000   0.000

Does the fact that the reach, delay, offset are all zeroes means that this host hasn't received any information from peers?

Details

I've also done ntpq, with command associations and received the following:

ind assid status  conf reach auth condition  last_event cnt
===========================================================
  1 12097  c811   yes  none   yes    reject    mobilize  1

Here's my ntp.conf:

driftfile /var/lib/ntp/drift
restrict default kod nomodify notrap nopeer noquery
restrict 127.0.0.1

statsdir /var/log/ntpstats/
logfile /var/log/ntpstats/ntpd.log

tos orphan 4
broadcast 239.0.1.1 key 1 ttl 1        # multicast server
multicastclient 239.0.1.1              # multicast client

keys /etc/ntp/keys
trustedkey 1

Here's the output log at /var/log/ntpstats/ntpd.log:

 2 Jan 16:19:57 ntpd[3554]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
 2 Jan 16:19:57 ntpd[3554]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
 2 Jan 16:19:57 ntpd[3554]: Listen normally on 1 lo 127.0.0.1 UDP 123
 2 Jan 16:19:57 ntpd[3554]: Listen normally on 2 eth0.10 10.3.1.2 UDP 123
 2 Jan 16:19:57 ntpd[3554]: Listen normally on 3 eth0.172 172.20.20.2 UDP 123
 2 Jan 16:19:57 ntpd[3554]: Listening on routing socket on fd #20 for interface updates
 2 Jan 16:19:57 ntpd[3554]: Listen normally on 4 multicast 239.0.1.1 UDP 123
 2 Jan 16:19:57 ntpd[3554]: Joined 239.0.1.1 socket to multicast group 239.0.1.1
 2 Jan 16:19:57 ntpd[3554]: 0.0.0.0 c016 06 restart
 2 Jan 16:19:57 ntpd[3554]: 0.0.0.0 c012 02 freq_set kernel 0.000 PPM
 2 Jan 16:19:57 ntpd[3554]: 0.0.0.0 c011 01 freq_not_set
 2 Jan 16:19:58 ntpd[3554]: io_setbclient: Opened broadcast client on interface #3 eth0.172
 2 Jan 16:19:58 ntpd[3554]: io_setbclient: Opened broadcast client on interface #2 eth0.10
 2 Jan 16:30:35 ntpd[3554]: 0.0.0.0 0614 04 freq_mode

Questions

Question 1

Is my NTP configuration receiving updates? If not, how can it be fixed?

Question 2 (Supplemental/Optional)

From what I understand, a multicast peer indicates that any host in the multicast group can send and receive NTP information from any other host, is this accurate?

Question 3 (Supplemental/Optional)

What do the last 6 lines of the log indicate (alternatively, where can I find documentation which explains)? Of particular interest to me is the following:

0.0.0.0 c012 02 freq_set kernel 0.000 PPM

I don't really understand any part of this. Does 0.0.0.0 indicate some peer behind the multicast address? What does c012 and 02 mean? Isn't this setting the drift time (the clock drifts 0 seconds over 0 seconds)?

Introduction

I'm attempting to set up basic communication with the RIPv2 protocol between two hosts running the BIRD routing daemon.

I've got Host A with an interface enp0 that has address 10.0.1.50/24.
I've got another host Host B with an interface enp1 that has address 10.1.1.25/24. These interfaces are directly connected by cable. I can ping between both machines if I add a static route on both machines.

Configuration Files

I have the following bird.conf on Host A:

protocol kernel {
        learn;                  # Learn all alien routes from the kernel
        persist;                # Don't remove routes on bird shutdown
        scan time 20;           # Scan kernel routing table every 20 seconds
        export all;             # Default is export none
}

protocol device {
    scan time 10;           # Scan interfaces every 10 seconds
}

protocol direct {
        interface "enp0"
}

protocol rip MyRIP {    
    export all;
    import all;
    interface "enp0" { mode multicast;};
}

The bird.conf on Host B is identical except the enp0 is replaced with enp1

Initial Results

After starting the bird daemon on both hosts, I can do a tcpdump -ni enp0 -vv

13:21:41.943537 IP (tos 0xc0, ttl 1, id 4933, offset 0, flags [none], proto UDP (17), length 132)
    10.1.1.25.520 > 224.0.0.9.7742: [udp sum ok] UDP, length 104
13:21:41.943704 IP (tos 0xc0, ttl 1, id 150, offset 0, flags [none], proto UDP (17), length 272)
    10.0.1.50.520 > 224.0.0.9.7742: [bad udp cksum 0xec48 -> 0x1219!] UDP, length 244

I can hop inside the birdcl command-line and run show rip neighbors and get an empty table.

Making it work

If I set the addresses to be on the same subnet, I can run show rip neighbors and I can see 10.0.1.50 in my lists of neighbors.

Wrap-up

How can I get these routers to list each other as neighbors if the two ends of the link aren't on the same subnet?

I must have some sort of incorrect mental picture of how networks work, don't routers need talk to neighbors which aren't on the same subnet all the time?

I'm not hung up on a BIRD-specific answer.