contrail-topology shown to have "failed" in contrail-status after upgrade from r3.0-2723 to r3.0.1.0-23

Bug #1565169 reported by wenqing liang
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R3.0
Fix Committed
High
ted ghose
Trunk
Fix Committed
High
ted ghose

Bug Description

contrail-topology was shown to have "failed" in contrail-status after an upgrade from r3.0-2723 to r3.0.1.0-23.

contrail-snmp-collector-stdout.log is uploaded to /cs-shared/bugs/1565169 on 10.84.5.112.

root@a5d11e36:/opt/contrail/utils# contrail-status
== Contrail Control ==
supervisor-control: active
contrail-control active
contrail-control-nodemgr active
contrail-dns active
contrail-named active

== Contrail Analytics ==
supervisor-analytics: active
contrail-alarm-gen active
contrail-analytics-api active
contrail-analytics-nodemgr active
contrail-collector active
contrail-query-engine active
contrail-snmp-collector active
contrail-topology failed

== Contrail Config ==
supervisor-config: active
contrail-api:0 active
contrail-config-nodemgr active
contrail-device-manager active
contrail-discovery:0 active
contrail-schema active
contrail-svc-monitor active
ifmap active

== Contrail Web UI ==
supervisor-webui: active
contrail-webui active
contrail-webui-middleware active

== Contrail Database ==
contrail-database: active
supervisor-database: active
contrail-database-nodemgr active
kafka active

== Contrail Support Services ==
supervisor-support-service: active
rabbitmq-server active

root@a5d11e36:/opt/contrail/utils#

wenqing liang (wliang)
information type: Proprietary → Public
wenqing liang (wliang)
description: updated
tags: added: analytics provisioning
removed: contrail-installer
Revision history for this message
Vedamurthy Joshi (vedujoshi) wrote :

Was seen on another upgrade from 3.0 build 34 to 35 as well

05/10/2016 03:50:49 PM [contrail-topology]: SANDESH: CONNECT TO COLLECTOR: True
05/10/2016 03:50:49 PM [contrail-topology]: SANDESH: Logging: LEVEL: [SYS_INFO] -> [SYS_NOTICE]
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/gevent/greenlet.py", line 327, in run
    result = self._run(*self.args, **self.kwargs)
  File "/usr/lib/python2.7/dist-packages/contrail_topology/controller.py", line 38, in get_vrouters
    self.analytic_api.get_vrouters(True)
  File "/usr/lib/python2.7/dist-packages/contrail_topology/analytic_client.py", line 64, in get_vrouters
    self.get_uves('vrouters', refresh=refresh)))
  File "/usr/lib/python2.7/dist-packages/contrail_topology/analytic_client.py", line 54, in get_uves
    self.get_uve_url()))
  File "/usr/lib/python2.7/dist-packages/contrail_topology/analytic_client.py", line 29, in _get_url_json
    raise ConnectionError, "bad request " + url
ConnectionError: bad request http://192.168.1.101:8081/analytics/uves
<Greenlet at 0x7fb7eba1c4b0: <bound method Controller.get_vrouters of <contrail_topology.controller.Controller object at 0x7fb7f0e92910>>> failed with ConnectionError

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/gevent/greenlet.py", line 327, in run
    result = self._run(*self.args, **self.kwargs)
  File "/usr/lib/python2.7/dist-packages/contrail_topology/controller.py", line 68, in get_prouters
    self.analytic_api.get_prouters(True)
  File "/usr/lib/python2.7/dist-packages/contrail_topology/analytic_client.py", line 80, in get_prouters
    self.get_uves('prouters')))
  File "/usr/lib/python2.7/dist-packages/contrail_topology/analytic_client.py", line 54, in get_uves
    self.get_uve_url()))
  File "/usr/lib/python2.7/dist-packages/contrail_topology/analytic_client.py", line 29, in _get_url_json
    raise ConnectionError, "bad request " + url
ConnectionError: bad request http://192.168.1.101:8081/analytics/uves
<Greenlet at 0x7fb7eba1c370: <bound method Controller.get_prouters of <contrail_topology.controller.Controller object at 0x7fb7f0e92910>>> failed with ConnectionError

Traceback (most recent call last):
  File "/usr/bin/contrail-topology", line 9, in <module>
    load_entry_point('contrail-topology==0.1.0', 'console_scripts', 'contrail-topology')()
  File "/usr/lib/python2.7/dist-packages/contrail_topology/main.py", line 18, in main
    controller.run()
  File "/usr/lib/python2.7/dist-packages/contrail_topology/controller.py", line 274, in run
    if self.constnt_schdlr.schedule(self.prouters):
AttributeError: 'Controller' object has no attribute 'prouters'

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/20323
Submitter: ted ghose (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R3.0

Review in progress for https://review.opencontrail.org/20537
Submitter: ted ghose (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/20537
Committed: http://github.org/Juniper/contrail-controller/commit/d100b1fd797849370c036336007f318617fa9aeb
Submitter: Zuul
Branch: R3.0

commit d100b1fd797849370c036336007f318617fa9aeb
Author: Ted Ghose <email address hidden>
Date: Tue May 17 12:24:38 2016 -0700

contrail-topology shown to have "failed"

Connection error is not properly handeled
- Captured exception

Change-Id: I11d125caeb5cfc088bc723c11b7aaa70c8446f93
Closes-Bug: 1565169

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/20323
Committed: http://github.org/Juniper/contrail-controller/commit/7772e8a5c948b86fee7cfb3775ff73619bbbf245
Submitter: Zuul
Branch: master

commit 7772e8a5c948b86fee7cfb3775ff73619bbbf245
Author: Ted Ghose <email address hidden>
Date: Tue May 17 12:24:38 2016 -0700

contrail-topology shown to have "failed"

Connection error is not properly handeled
- Captured exception

Change-Id: I2bc00c64e391bc78d03bff4366d2be9763816db8
Closes-Bug: 1565169

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.