https://bugs.launchpad.net/trove/+bug/1705412
tehere you are :)
On 19/07/17 16:15, MCCASLAND, TREVOR wrote:
That’s not right, can you make a bug report here?
https://bugs.launchpad.net/trove/
*From:*magicb...@gmail.com [mailto:magicb...@gmail.com]
*Sent:* Wednesday, July 19, 2017 7:43 AM
*T
Hello All,
Mirantis 7.0
I am trying to keep ntpd down and do a periodic ntpdate against a time
server.
This is because one of the controllers started to drift and services in
that not started to go down.
But it seems that the ntpd daemon comes up after 10 sec every time i stop
it.
Is there a mon
On all of the controllers? crm resource stop clone_p_ntp should do it.
Although I can't imagine why you would want to do this. Time is very
important in OpenStack (and Ceph if you are running it) which it sounds
like you've already found out.
The whole purpose of NTP is to keep your time in sync -
Thanks a lot for the reply, John.
Yes I understand that time is really important for cluster setup, that's
why I was panicking and looking for alternatives when I found time drifting
while ntpd was still on.
So I was planning to do a ``ntpdate w.x.y.z '' every 2 mins in order to
keep time in sync.
Dear Openstack community,
I recently did a deployment of Openstack using kolla-ansible, installation
finished without any error, however I can't assign any floating IP to the
instance.
This is the error message I get form the console.
[root@kolla ~]# openstack server list
+
On Jul 20, 2017, at 7:26 PM, Raja T Nair wrote:
> Thanks a lot for the reply, John.
>
> Yes I understand that time is really important for cluster setup, that's why
> I was panicking and looking for alternatives when I found time drifting while
> ntpd was still on.
> So I was planning to do a
To Brad's point - if your controllers are VM's you might also want to have
a look at Chrony https://chrony.tuxfamily.org/. It's supposed to perform
much better on virtual machines.
___
John Petrini
On Thu, Jul 20, 2017 at 9:20 PM, Brad Knowles
wrote:
> On Jul 20, 2017, at 7:26 PM, Raja T Nair
On 2017-07-21 05:56:48 +0530 (+0530), Raja T Nair wrote:
[...]
> Many other servers sync with this one too. Also only one
> controller had issues with time. Kind of stuck here, as I have no
> idea why one node's ntpd would fail :(
[...]
I've seen this from time to time over the years and it's near
Hi,
That looks very similar to https://bugs.launchpad.net/neutron/+bug/1696889
where if you had the designate driver loaded, you couldn't associate a floating
IP address unless you had network dns names configured.
Not sure if the release of Kolla you are using has the fix in place.
Regards,
D
