Juniper Openstack

upgrade: 3.2 to 4.0 neutron-server not running after upgrade

Bug #1694857 reported by Shweta Naik
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R4.0
Invalid
High
Shweta Naik
Juniper Openstack r4.0.1.0 "r4.0.1.0"
Trunk
Invalid
High
Shweta Naik
Juniper Openstack r4.1.0.0-fcs "r4.1"

Bug Description

base image: 3.2 build 38 mitaka
upgraded to : 4.0 build 16 mitaka

have both openstacj and contrail HA in the cluster

after upgrade from 3.2 to 4.0 neutron-server was not running in any of the openstack nodes.

root@server1:/etc/rabbitmq# dpkg -l | grep neutron-server
ii neutron-server 2:8.3.0-0ubuntu1.1~cloud0 all Neutron is a virtual network service for Openstack – server

attaching the neutron-server.log from one of the openstack nodes.

FYI : had manually started the service at the end

Revision history for this message
Shweta Naik (stnaik) wrote :
Revision history for this message
Jeba Paulaiyan (jebap) wrote :

Release notes:

     After upgrade of cluster running R3.2 to R4.0, sometimes the neutron server process does not get started automatically.

Workaround: Start neutron server explicitly after upgrade

tags: added: provisioning releasenote
removed: blocker
Soumil Kulkarni (soumilk)
information type: Proprietary → Public
Revision history for this message
Dheeraj Gautam (dgautam) wrote :

Confirmed with Reporter, this is not seen with build R4.0-20. Re-assigning back to reporter to confirm and close.

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

Other bug subscribers

Remote bug watches

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