Juju Charms Collection
neutron-api package

neutron-api restarts infinitely with eating CPU resource until relations are made

Bug #1505325 reported by Nobuto Murata
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Neutron API Charm
Triaged
Low
Unassigned
neutron-api (Juju Charms Collection)
Invalid
Low
Unassigned
Juju Charms Collection 17.01

Bug Description

How to reproduce:
$ juju deploy cs:trusty/neutron-api && juju set neutron-api openstack-origin='cloud:trusty-kilo' debug=True

Expected result:
neutron-api will be quiet until relations are made

Actual result:
neutron-api restarts infinitely with eating CPU resource (50%-100%) until relations are made

Revision history for this message
Nobuto Murata (nobuto) wrote :
James Page (james-page)
Changed in neutron-api (Juju Charms Collection):
status: New → Triaged
importance: Undecided → Low
milestone: none → 16.01
milestone: 16.01 → 16.04
James Page (james-page)
Changed in neutron-api (Juju Charms Collection):
milestone: 16.04 → 16.07
Edward Hope-Morley (hopem)
tags: added: openstack
Liam Young (gnuoy)
Changed in neutron-api (Juju Charms Collection):
milestone: 16.07 → 16.10
James Page (james-page)
Changed in neutron-api (Juju Charms Collection):
milestone: 16.10 → 17.01
Revision history for this message
Nobuto Murata (nobuto) wrote :

Now with xenial, systemd stops neutron-server service after multiple attempts to start, and juju status says "blocked" appropriately. So no longer eating CPU resources infinitely.

# systemctl status neutron-server.service
● neutron-server.service - OpenStack Neutron Server
   Loaded: loaded (/lib/systemd/system/neutron-server.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Wed 2016-12-21 03:20:12 UTC; 10min ago
  Process: 23607 ExecStart=/etc/init.d/neutron-server systemd-start (code=exited, status=1/FAILURE)
  Process: 23606 ExecStartPre=/bin/chown neutron:neutron /var/lock/neutron /var/log/neutron /var/lib/neutron (code=exited, status=0/SUCCESS)
  Process: 23600 ExecStartPre=/bin/mkdir -p /var/lock/neutron /var/log/neutron /var/lib/neutron (code=exited, status=0/SUCCESS)
 Main PID: 23607 (code=exited, status=1/FAILURE)

Dec 21 03:20:12 juju-bbb18b-0 systemd[1]: neutron-server.service: Unit entered failed state.
Dec 21 03:20:12 juju-bbb18b-0 systemd[1]: neutron-server.service: Failed with result 'exit-code'.
Dec 21 03:20:12 juju-bbb18b-0 systemd[1]: neutron-server.service: Service hold-off time over, scheduling restart.
Dec 21 03:20:12 juju-bbb18b-0 systemd[1]: Stopped OpenStack Neutron Server.
Dec 21 03:20:12 juju-bbb18b-0 systemd[1]: neutron-server.service: Start request repeated too quickly.
Dec 21 03:20:12 juju-bbb18b-0 systemd[1]: Failed to start OpenStack Neutron Server.

James Page (james-page)
Changed in charm-neutron-api:
importance: Undecided → Low
status: New → Triaged
Changed in neutron-api (Juju Charms Collection):
status: Triaged → Invalid
Revision history for this message
Ante Karamatić (ivoks) wrote :

This sounds like 'Fix Released', no?

tags: added: cpe-onsite
removed: cpec
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.