RHOSP13- R5.0.2-284: vrouter process status alarm not getting generated

[alok kumar]

In RHOSP13 setup vrouter process status alarm not getting generated.

Test case: test_vrouter_process_status_alarms

contrail tag: rhel-queens-5.0-284

Tried stopping vrouter docker manually too and don't see alarm getting generated for this.

setup Info:

undercloud host: nodei21
undercloud IP: 192.168.122.68

(undercloud) [stack@queensa ~]$ openstack server list
+--------------------------------------+--------------------------------+--------+------------------------+----------------+---------------------+
| ID | Name | Status | Networks | Image | Flavor |
+--------------------------------------+--------------------------------+--------+------------------------+----------------+---------------------+
| 5b94158d-356e-4e32-b2c9-6a59e87c6014 | overcloud-contrailcontroller-1 | ACTIVE | ctlplane=192.168.24.6 | overcloud-full | contrail-controller |
| f79cbb44-fd6d-4b4f-b2c6-0affbb114a85 | overcloud-contrailcontroller-0 | ACTIVE | ctlplane=192.168.24.19 | overcloud-full | contrail-controller |
| 22a76b77-1c05-4c15-bdf8-992df0b42100 | overcloud-novacompute-0 | ACTIVE | ctlplane=192.168.24.14 | overcloud-full | compute |
| 471c7803-f1ce-4cb6-ac34-856a74bb62c7 | overcloud-novacompute-1 | ACTIVE | ctlplane=192.168.24.11 | overcloud-full | compute |
| 896f8761-3290-4025-8aa8-08fdd627c980 | overcloud-controller-0 | ACTIVE | ctlplane=192.168.24.18 | overcloud-full | control |
| 4e28dcc0-6263-412b-8a79-144ad40e179d | overcloud-controller-2 | ACTIVE | ctlplane=192.168.24.16 | overcloud-full | control |
| a7410241-d8fa-4ee4-91c6-7367c5092cee | overcloud-novacompute-2 | ACTIVE | ctlplane=192.168.24.13 | overcloud-full | compute |
| 42ee730d-de37-4eeb-a910-720f8e558b7b | overcloud-contrailcontroller-2 | ACTIVE | ctlplane=192.168.24.12 | overcloud-full | contrail-controller |
| aa05fab9-79ee-4265-b6b8-054a02632cac | overcloud-controller-1 | ACTIVE | ctlplane=192.168.24.9 | overcloud-full | control |
+--------------------------------------+--------------------------------+--------+------------------------+----------------+---------------------+

[Sundaresan Rajangam (srajanga)]

Did you check if the NodeStatus UVE was updated by nodemgr?

Please provide http://<analytics-ip>:8081/analytics/uves/vrouter/<hostname>?flat

If the status is not updated, check the introspect of the vrouter-nodemgr - http://<vrouter-ip>:8102/Snh_SandeshUVECacheReq?x=NodeStatus

[alok kumar (kalok)]

I had mentioned setup details so Dev team can get any details required to debug further and setup was available for quite sometime.
Just marking the bug incomplete which was reproducible in rerun in a particular setup does not make any sense.
setup is reimaged for dpdk sanity and in this setup I'm hitting some another issue (cmd timeout)while running this test.

Can provide the required information when able to test it again.

[alok kumar (kalok)]

The bug was seen with kernel mode compute and now setup is with dpdk compute where the issue is not reproducible.
Alarm is getting generated when agent is stopped, verified it manually.

current setup is locked to debug other issues so I can't provision the setup with kernel mode right now to reproduce this issue.
so closing the bug for now and need to revisit if seen again.