HttpException: 503: Server Error (Focal/Ussuri)

Bug #1900019 reported by Hybrid512
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Charms Deployment Guide
Fix Released
High
Peter Matulis
OpenStack Masakari Charm
Invalid
Undecided
Unassigned

Bug Description

Hi,

I'm trying to deploy Masakari on a working Focal/Ussuri Openstack bundle.
I tried many times and whatever I try, I end up with a running Openstack cluster (every features like images, servers, volumes, ...) are working but as soon as I'm trying "segement" actions, nothing work and I get this error :

HttpException: 503: Server Error for url: http://192.168.211.24:15868/v1/343e2d906a9d4d8eb3f5347264c8ff83/segments, The server is currently unavailable. Please try again at a later time.: The Keystone service is temporarily unavailable.: 503 Service Unavailable

Just to say, Keystone is perfectly working as the whole Openstack platform is working properly, only Masakari fails.

I tried with both "stable" (3) Masakari charm and "-next" (26) one, both same result.

Here is a snippet of my bundle :

applications:

  masakari-monitors:
    charm: cs:masakari-monitors

  masakari-hacluster:
    charm: cs:hacluster
    options:
      maas_url: *maas_url
      maas_credentials: *maas_credentials

  pacemaker-remote:
    charm: cs:pacemaker-remote
    options:
      enable-stonith: True
      enable-resources: False

  masakari:
    charm: cs:masakari
    num_units: 3
    to:
    - lxd:0
    - lxd:1
    - lxd:2

relations:
- - nova-compute:juju-info
  - masakari-monitors:container
- - masakari:ha
  - masakari-hacluster:ha
- - keystone:identity-credentials
  - masakari-monitors:identity-credentials
- - nova-compute:juju-info
  - pacemaker-remote:juju-info
- - masakari-hacluster:pacemaker-remote
  - pacemaker-remote:pacemaker-remote
- - masakari:identity-service
  - keystone:identity-service
- - masakari:shared-db
  - mysql-innodb-cluster:shared-db
- - masakari:amqp
  - rabbitmq-server:amqp

Best regards

Revision history for this message
Aurelien Lourot (aurelien-lourot) wrote :

Hi Hybrid512, thanks for reporting! Could it be that your bundle is lacking nova-cloud-controller? I was able to reproduce the issue by deploying a simple bundle with no nova-cloud-controller. Thanks!

Revision history for this message
Hybrid512 (walid-moghrabi) wrote :

Hi Aurelien,

My bundle has nova-cloud-controller deployed so this shouldn't be related

Revision history for this message
Aurelien Lourot (aurelien-lourot) wrote :

The issue turned out to be a missing relation:

  - - 'vault:certificates'
    - 'masakari:certificates'

Thanks Hybrid512 for having figured it out. I think the Masakari Appendix [0] should at least point to the Cert Appendix [1] as this is IMHO quite hard to figure out that such a relation is needed.

0: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-masakari.html
1: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-certificate-management.html

Changed in charm-masakari:
status: New → Invalid
Revision history for this message
Hybrid512 (walid-moghrabi) wrote :

Yes, I confirm, adding the relation fixed the issue.
Dumb one but there were nothing really trivial to guess that this was the root cause of my issue.
Please, fix the documentation, that will avoid more newbies like me to fall in the trap ;)

Changed in charm-deployment-guide:
assignee: nobody → Peter Matulis (petermatulis)
importance: Undecided → High
status: New → Triaged
Changed in charm-deployment-guide:
status: Triaged → In Progress
Revision history for this message
Peter Matulis (petermatulis) wrote :
Changed in charm-deployment-guide:
status: In Progress → Fix Released
Changed in charm-deployment-guide:
milestone: none → 21.04
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.