In the process of diagnosing an Ansible OpenStack multi-node build problem, I
came across the following dnsmasq-dhcp errors in syslog.
-- snip --
Feb 28 20:25:06 xh3 dnsmasq-dhcp[1956]: not giving name
aio1-designate-container-f182826f to the DHCP lease of 10.255.255.226 because
the name exists
I've been chasing a problems with a build for some days now and would greatly
appreciate any pointers the community can offer.
The build is built of three nodes (infra+storage+compute) each of which is a
KVM virtual machine.
After installation everything seems fine. However, after rebooting the
at area rather
than the connection failure itself.
On a side note - this sounds like it may well be a bug with SSL certs in
rabbitmq in OpenStack-Ansible, I'd love to get that fixed if that is the case!
Hope that helps though.
Andy
On 6 March 2017 at 15:38, Lawrence J. Albinson
mailto:la
OpenStack family) within the openstack-ansible framework without branching the
repo and making modifications?
WIth apologies in advance in the event that I have overlooked the essential
piece of documentation on how to do this.
Kind regards, Lawrence
Lawrence J Albinson
hosts such as:
www.fred.organisation.com.<http://www.fred.organisation.com.> .
(The designate back-end is Bind9.)
Any pointers about how to do this would be very gratefully received.
Kind regards, Lawrence
Lawrence J Al
Hi Andy,
As ever, many thanks for the prompt reply. I'm going to work up a patch
proposal and submit it as soon as possible.
Kind regards, Lawrence
From: Andy McCrae
Sent: 20 June 2017 14:15
To: OpenStack Development Mailing List (not for usage questions)
Subjec
. Is there a reason for this?
Kind regards, Lawrence
Lawrence J Albinson
From: Graham Hayes
Sent: 20 June 2017 13:01
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [openstack-ansible][designate][bind9] Looking for
ways to limit users to
45-ffac7ce3ebbd']
Before I go searching through the Neutron source, does anyone know if this is a
'hole' in the Neutron API and, if so, has it been fixed after the commit point
being used by openstack-ansible tag 15.1.3.
Kind regards,
, Lawrence
From: Graham Hayes
Sent: 27 June 2017 16:14
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [openstack-ansible][neutron][designate] Failure
trying to set dns_domain from command line
On 27/06/17 15:01, Lawrence J. Albinson wrote:
> Hello Coll
uring OpenStack Networking for integration with an external
DNS service'.
and covering:
[default]
external_dns_driver = designate
[designate]
url = etc
Kind regards, Lawrence
On 27/06/17 16:57, Graham Hayes wrote:
> On 27/06/17 16:36, Lawrence J. Albinson wrote:
stack/openstack-ansible-os_neutron/blob/master/templates/neutron.conf.j2#L5
I'm curious to know why this is.
Kind regards, Lawrence
Lawrence J Albinson
__
OpenStack Development Mailing List (not for usage questions)
U
On 30/06/17 16:12, Graham Hayes wrote:
> On 30/06/17 13:29, Lawrence J. Albinson wrote:
>> Good Afternoon Colleagues,
>>
>> I've been working to incorporate dynamic dns/designate updating from
>> neutron and nova within an OpenStack-Ansible built environment.
>
's the documentation:
https://docs.openstack.org/ocata/networking-guide/config-dns-int.html
Regards
On Fri, Jun 30, 2017 at 2:43 PM, Lawrence J. Albinson
mailto:lawre...@ljalbinson.com>> wrote:
On 30/06/17 16:12, Graham Hayes wrote:
> On 30/06/17 13:29, Lawrence J. Albinson w
nvironment is working fine at 15.1.3.
I've turned up nothing with searches. Any help greatly appreciated.
Kind regards, Lawrence
Lawrence J Albinson
__
OpenStack Development Mailing List (not for usage questions)
Unsubsc
, Lawrence J. Albinson
mailto:lawre...@ljalbinson.com>> wrote:
Dear Colleagues,
Before I go problem hunting, has anyone seen openstack-ansible builds failing
at release 15.1.5 at the following point:
TASK [lxc_container_create : Create localhost config] **
with the erro
#x27;.
As ever, any help would be very gratefully received.
Kind regards, Lawrence
Lawrence J Albinson
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
the expected instance id)
It seems that this is a bug in libvirt that is fixed in the centos/rhel world.
The hypervisor 'compute1' is built with 16.04.2 LTS and fully updated.
Does anyone know of a fix in the ubuntu/debian world?
Or should I be raising thi
Dear Colleagues,
I have just noticed that the short-form tempest run at the end of an
openstack-ansible installation is failing with the following error:
TASK [os_tempest : Ensure tempest image] ***
Thursday 07 September 2017 19:29:12 +0100 (0:00:07.251)
Just noticed that I left off the OSA version which is 15.1.7.
From: Lawrence J. Albinson
Sent: 08 September 2017 10:57
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [openstack-ansible][tempest] "Ensure tempest
Dear colleagues,
I have recently moved my environment over to openstack-ansible 16.0.8 and when
I run tempest testing as the last step of the deployment it is failing with the
following errors logged in daemon.log on the compute server.
Before I use up more time looking into the details of libv
20 matches
Mail list logo
