[page #281] - advise to include kernel upgrade options in config/instances.yaml

[tkaagent]

It would be beneficial to include kernel upgrade option for Centos7.6, as with .10.0-957.el7.x86_64 vRouters will not come up; in restarting loop:

[root@cent222 tmp]# contrail-status
Pod      Service   Original Name           Original Version  State       Id            Status                        
         rsyslogd                          1912-32           running     e99abd431b32  Up 41 minutes                  
vrouter  agent     contrail-vrouter-agent  1912-32           restarting  ee984ef0f998  Restarting (1) 41 seconds ago  
vrouter  nodemgr   contrail-nodemgr        1912-32           running     b7d97f6d7141  Up 40 minutes                  
WARNING: container with original name '' have Pod or Service empty. Pod: '' / Service: 'rsyslogd'. Please pass NODE_TYPE with pod name to container's env
vrouter driver is not PRESENT but agent pod is present
== Contrail vrouter ==
nodemgr: active
agent: inactive
[root@cent222 tmp]# 

[root@cent222 tmp]# docker logs vrouter_vrouter-agent_1
INFO: agent started in kernel mode
Device "vhost0" does not exist.
cat: /sys/class/net/vhost0/address: No such file or directory
INFO: creating vhost0 for nic mode: nic: ens224, mac=00:50:56:a6:38:a6
              total        used        free      shared  buff/cache   available
Mem:            31G        628M         28G        9.2M        2.3G         30G
Swap:            0B          0B          0B
              total        used        free      shared  buff/cache   available
Mem:            31G        593M         30G        9.3M        503M         30G
Swap:            0B          0B          0B
INFO: load vrouter kernel module, options=''
modprobe: FATAL: Module vrouter not found.
WARNING: failed to load vrouter driver
vhost_create: Unknown error -95
Error registering NetLink client: No such file or directory (2)
Error registering NetLink client: No such file or directory (2)
Cannot find device "vhost0"
Cannot find device "vhost0"
FATAL: failed to init vhost0
INFO: agent started in kernel mode
Device "vhost0" does not exist.
cat: /sys/class/net/vhost0/address: No such file or directory
INFO: creating vhost0 for nic mode: nic: ens224, mac=00:50:56:a6:38:a6
              total        used        free      shared  buff/cache   available
Mem:            31G        621M         30G        9.3M        518M         30G
Swap:            0B          0B          0B
              total        used        free      shared  buff/cache   available
Mem:            31G        600M         30G        9.3M        470M         30G
Swap:            0B          0B          0B
INFO: load vrouter kernel module, options=''
modprobe: FATAL: Module vrouter not found.
WARNING: failed to load vrouter driver
vhost_create: Unknown error -95
Error registering NetLink client: No such file or directory (2)
Error registering NetLink client: No such file or directory (2)
Cannot find device "vhost0"
Cannot find device "vhost0"
FATAL: failed to init vhost0
INFO: agent started in kernel mode
Device "vhost0" does not exist.
cat: /sys/class/net/vhost0/address: No such file or directory

After upgrade to 3.10.0-1062.9.1.el7.x86_64 vRouters will be up:

[root@cent222 ~]# docker ps | grep vrou
a908ebbfb15d        hub.juniper.net/contrail/contrail-nodemgr:1912.32             "/entrypoint.sh /bin…"   7 minutes ago       Up 7 minutes                            vrouter_nodemgr_1
a8cb4ded7f02        hub.juniper.net/contrail/contrail-vrouter-agent:1912.32       "/entrypoint.sh /usr…"   7 minutes ago       Up 7 minutes                            vrouter_vrouter-agent_1
[root@cent222 ~]# 


Example below [ **UPGRADE_KERNEL: true** ]
[root@cent111 contrail-ansible-deployer]# cat config/instances.yaml
global_configuration:
  CONTAINER_REGISTRY: hub.juniper.net/contrail
  REGISTRY_PRIVATE_INSECURE: True
  CONTAINER_REGISTRY_USERNAME: xxxxxx
  CONTAINER_REGISTRY_PASSWORD: xxxxxx  
provider_config:
  bms:
    ssh_pwd: xxxxxx
    ssh_user: root
    ntpserver: 0.north-america.pool.ntp.org
    domainsuffix: local
instances:
  bms1:
    provider: bms
    ip: 192.168.100.201
    roles:
        analytics:
        analytics_alarm:
        analytics_database:
        analytics_snmp:
        config:
        config_database:
        control:
        k8s_master:
        kubemanager:
        webui:
  bms2:
    provider: bms
    ip: 192.168.100.202
    roles:
        k8s_node:
        vrouter:
          VROUTER_GATEWAY: 10.10.10.100
  bms3:
    provider: bms
    ip: 192.168.100.203
    roles:
        k8s_node:
        vrouter:
          VROUTER_GATEWAY: 10.10.10.200
contrail_configuration:
  CLOUD_ORCHESTRATOR: kubernetes
  CONTRAIL_VERSION: 1912.32
  UPGRADE_KERNEL: true
  RABBITMQ_NODE_PORT: 5673
  VROUTER_GATEWAY: 10.10.10.100
  CONTROLLER_NODES: 192.168.100.201
  CONTROL_NODES: 10.10.10.201
  KUBERNETES_API_NODES: 10.10.10.201
  KUBERNETES_API_SERVER: 10.10.10.201

[pinggit]

thanks @tkaagent . great tip!
I checked my setup with "old" kernel (957) it works fine.

$ uname -a
Linux cent333 3.10.0-957.10.1.el7.x86_64 #1 SMP Mon Mar 18 15:06:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

so I'm not quite sure why it does not work for you. but giving that "new" kernel (1062) works for you (with the exact config you gave), let's leave the issue as is for now.