Designate

devstack procedure fails due to missing proxy_http

Bug #1999019 reported by Nobuto Murata
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
Fix Released
Undecided
Nobuto Murata

Bug Description

In the latest developer documentation:
https://docs.openstack.org/designate/latest/contributor/devstack.html
there is a config for the minimal environment for Designate as follows.

# Disable all services except core ones
disable_all_services
enable_service rabbit mysql key

This actually fails to proxy designate API requests.

$ export OS_CLOUD=devstack
$ openstack zone list
Failed to contact the endpoint at http://192.168.122.56/dns for discovery. Fallback to using that endpoint as the base url.
Unknown

$ openstack catalog list
+-----------+----------+------------------------------------------+
| Name | Type | Endpoints |
+-----------+----------+------------------------------------------+
| designate | dns | RegionOne |
| | | public: http://192.168.122.56/dns |
| | | |
| keystone | identity | RegionOne |
| | | public: http://192.168.122.56/identity |
| | | |
+-----------+----------+------------------------------------------+

$ curl http://192.168.122.56/dns
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator at
 webmaster@localhost to inform them of the time this error occurred,
 and the actions you performed just before this error.</p>
<p>More information about this error may be available
in the server error log.</p>
<hr>
<address>Apache/2.4.52 (Ubuntu) Server at 192.168.122.56 Port 80</address>
</body></html>

$ tail -n1 /var/log/apache2/error.log
[Wed Dec 07 06:38:47.104798 2022] [proxy:warn] [pid 36930:tid 140187724146240] [client 192.168.122.56:38606] AH01144: No protocol handler was valid for the URL /dns (scheme 'http'). If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.

Nobuto Murata (nobuto)
Changed in designate:
assignee: nobody → Nobuto Murata (nobuto)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to designate (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/designate/+/866834

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

Reviewed: https://review.opendev.org/c/openstack/designate/+/866834
Committed: https://opendev.org/openstack/designate/commit/04321d3324c0c290c79cc22df38ea5a767e05687
Submitter: "Zuul (22348)"
Branch: master

commit 04321d3324c0c290c79cc22df38ea5a767e05687
Author: Nobuto Murata <email address hidden>
Date: Wed Dec 7 17:20:14 2022 +0900

    Make sure proxy_http is always loaded for devstack

    With the minimal Designate deployment with devstack, keystone module
    doesn't load proxy_http so Designate API requests may fail. Explicitly
    enable the module to make sure the apache2 setup always works for
    Designate.

    Closes-Bug: #1999019
    Change-Id: I1fc02225b6676b68137245df2279340f215221f4

Changed in designate:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/designate 16.0.0.0rc1

This issue was fixed in the openstack/designate 16.0.0.0rc1 release candidate.

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.