barbican-api, instead of designate-api, is stopped when running designate-api by http + mod_wsgi
Bug #1982794 reported by
Takashi Kajinami
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| puppet-designate |
Fix Released
|
Critical
|
Takashi Kajinami | ||
Bug Description
Because of the wrong parameter used in api.pp, when we run Designate API by httpd + mod_wsgi, barbican-api service is stopped instead of designate-api in case puppet-designate is used with puppet-barbican.
| Changed in puppet-designate: | |
| importance: | Undecided → High |
| assignee: | nobody → Takashi Kajinami (kajinamit) |
| description: | updated |
| description: | updated |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to puppet-designate (master) | #1 |
| Changed in puppet-designate: | |
| status: | New → In Progress |
| Changed in puppet-designate: | |
| importance: | High → Critical |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to puppet-designate (master) | #2 |
| Changed in puppet-designate: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/puppet-designate 21.0.0 | #3 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/