Hide Forgot
Description of problem: Created new record - BIND backend is not updated Log: 2016-01-26 13:04:41.360 16477 WARNING designate.mdns.notify [req-1d4b5b0b-ec10-4e28-9a67-8425ceeb07cb - - - - -] Got lower serial for 'example2.com.' to '172.16.20.12:53'. Expected:'1453830531'. Got:'1453829115'.Retries left='4' Version-Release number of selected component (if applicable): Liberty [root@overcloud-controller-0 ~]# rpm -qa| grep desig openstack-designate-sink-1.0.0-0.2.0b3.el7ost.noarch openstack-designate-api-1.0.0-0.2.0b3.el7ost.noarch openstack-designate-mdns-1.0.0-0.2.0b3.el7ost.noarch openstack-designate-pool-manager-1.0.0-0.2.0b3.el7ost.noarch openstack-designate-common-1.0.0-0.2.0b3.el7ost.noarch openstack-designate-agent-1.0.0-0.2.0b3.el7ost.noarch python-designate-1.0.0-0.2.0b3.el7ost.noarch python-designateclient-1.5.0-1.el7ost.noarch openstack-designate-central-1.0.0-0.2.0b3.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1.Install designate 2.Create server , domain, record . ( designate server-create --name $(hostname)., designate domain-create --name example1.com. --email root , designate record-create --name server1.example1.com. --type A --data 1.2.3.4 domainid ) 3. execute dig request for the record ( dig +short -p 53 @localhostIP or dnshostIP server1.example1.com A ) 4. See logs and BIND DB Actual results: Dig reply fails Expected results: Dig reply should be successful Additional info:
Designate is unsupported at this level, closing this bug.