designate cli shows the domain was created. BUT, the log show the connection was refused by server

Bug #1494132 reported by Alex Stafeyev
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
Won't Fix
Undecided
Unassigned

Bug Description

We have designate with BIND9 backed configuration. Bind9 was not configured properly
and will refuse connection from designate. I created domain via designate CLI. The designate cli shows the domain was created. BUT, the log show the connection was refused by server.
Error during missconfiguration - Openstack says created, Log says failed

[root@controller ~(keystone_admin)]# designate domain-create --name bind9.com. --email <email address hidden>
 +-------------+--------------------------------------+ | Field | Value | +-------------+--------------------------------------+
 | description | None |
 | created_at | 2015-09-06T13:00:09.000000 |
 | updated_at | None |
 | email | <email address hidden> |
 | ttl | 3600 | | serial | 1441544409 |
 | id | e346e289-8fd8-49f4-openstack-designate-api-2015.1.0-1.el7ost.noarch
openstack-designate-agent-2015.1.0-1.el7ost.noarch
openstack-designate-sink-2015.1.0-1.el7ost.noarch
python-designate-2015.1.0-1.el7ost.noarch
openstack-designate-mdns-2015.1.0-1.el7ost.noarch
python-designateclient-1.2.0-1.el7ost.noarch
openstack-designate-common-2015.1.0-1.el7ost.noarch
openstack-designate-central-2015.1.0-1.el7ost.noarch
openstack-designate-pool-manager-2015.1.0-1.el7ost.noarch8a7b-5001042ea674 |
 | name | bind9.com. |

logs
http://pastebin.com/wLsmEQeg

openstack-designate-api-2015.1.0-1.el7ost.noarch
openstack-designate-agent-2015.1.0-1.el7ost.noarch
openstack-designate-sink-2015.1.0-1.el7ost.noarch
python-designate-2015.1.0-1.el7ost.noarch
openstack-designate-mdns-2015.1.0-1.el7ost.noarch
python-designateclient-1.2.0-1.el7ost.noarch
openstack-designate-common-2015.1.0-1.el7ost.noarch
openstack-designate-central-2015.1.0-1.el7ost.noarch
openstack-designate-pool-manager-2015.1.0-1.el7ost.noarch

Revision history for this message
Tim Simmons (timsim) wrote :

This is a limitation of the v1 API, and thus the v1 client. It doesn't have access to the 'STATE' field, and has no way to know of backend failures.

The v2 CLI plugin to openstack-cli would show the state of the zone in ERROR.

Closing as we can't/won't fix.

Changed in designate:
status: New → Won't Fix
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.