[Bug 1798891] Re: [SRU] octavia-api won't start by default

[Brian Murray]

Hello Corey, or anyone else affected,

Accepted octavia into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/octavia/3.0.0-0ubuntu3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: octavia (Ubuntu Cosmic)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1798891

Title:
  [SRU] octavia-api won't start by default

Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Triaged
Status in octavia package in Ubuntu:
  Fix Committed
Status in octavia source package in Cosmic:
  Fix Committed
Status in octavia source package in DD-Series:
  Triaged

Bug description:
  [Impact]

  After installing octavia-api the systemd unit fails to start:

  Failed 'systemctl status octavia-api' output shows:

  error: unrecognized arguments: --http-socket [::]:9876 --ini
  /etc/octavia/octavia-api-uwsgi.ini

  The problem is that init files are configured with UWSGI options but
  the binary being run is not uwsgi. See full output:
  https://paste.ubuntu.com/p/WHQk2y2F84/

  [Test Case]
  1) sudo apt install octavia-api
  2) watch systemctl status octavia-api  # watch to ensure it doesn't fail
  3) curl 127.0.0.1:9876 # should return something like [1], not [2]

  [1] {"versions": [{"id": "v1", "status": "DEPRECATED", "updated":
  "2014-12-11T00:00:00Z", "links": [{"href": "http://127.0.0.1:9876/v1",
  "rel": "self"}]}, {"id": "v2.0", "status": "SUPPORTED", "updated":
  "2016-12-11T00:00:00Z", "links": [{"href": "http://127.0.0.1:9876/v2",
  "rel": "self"}]}, {"id": "v2.1", "status": "SUPPORTED", "updated":
  "2018-04-20T00:00:00Z", "links": [{"href": "http://127.0.0.1:9876/v2",
  "rel": "self"}]}, {"id": "v2.2", "status": "CURRENT", "updated":
  "2018-07-31T00:00:00Z", "links": [{"href": "http://127.0.0.1:9876/v2",
  "rel": "self"}]}]}

  [2] curl: (7) Failed to connect to 127.0.0.1 port 9876: Connection
  refused

  [Regression Potential]
  Low. The provided fix only touches the octavia-api and is using the standard approach that OpenStack has historically used to start a service which is to use the service's /usr/bin/<service>-api file which in the case of octavia is using wsgiref.simple_server to host the API WSGI server. Ideally we'll like to run the API under an apache2 server but that switch seems more appropriate in a development cycle than a stable cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1798891/+subscriptions