Invalid service_key_path causes crash in neutron service

Bug #1707872 reported by Sanket Sudake
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Openstack Omni
Fix Released
Undecided
Sanket Sudake

Bug Description

GCE service should be initialized out of neutron service start path so that service should not crash at startup if service_key is not at correct path.

Changed in omni:
assignee: nobody → Sanket Sudake (ssudake21)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to omni (master)

Fix proposed to branch: master
Review: https://review.openstack.org/489586

Changed in omni:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to omni (master)

Reviewed: https://review.openstack.org/489586
Committed: https://git.openstack.org/cgit/openstack/omni/commit/?id=8d58fd2f16cf37dee0d0c687dddda7515074d446
Submitter: Jenkins
Branch: master

commit 8d58fd2f16cf37dee0d0c687dddda7515074d446
Author: Sanket <email address hidden>
Date: Tue Aug 1 17:57:58 2017 +0530

    Create GCE Service outside Neutron service start path

    Creating gce client inside Neutron service start causes neutron-server
    crash if service_key is not there at mentioned path. Neutron service
    should not crash at start if service key is not there.

    Change-Id: I8e0f8b150c60d55d71846face217d5213b5df9b7
    Closes-Bug: #1707872

Changed in omni:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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