On 02 Sep 2016, at 11:50, Nick Jones
> wrote:
On 2 Sep 2016, at 9:28, William Josefsson wrote:
[..]
Is there any cleanup of volumes entries with deleted=1, or is it
normal these old entries lay around? thx will
There’s a
On 2 Sep 2016, at 9:28, William Josefsson wrote:
[..]
Is there any cleanup of volumes entries with deleted=1, or is it
normal these old entries lay around? thx will
There’s a timely blog post from Matt Fischer on exactly that subject:
http://www.mattfischer.com/blog/?p=744
His comment
There is ‘cinder-manage db purge’ to delete entries which are marked as deleted.
I never tried it (and suggest to start with a copy of the db before touching
the prod
ones). We usually do not purge databases unless we hit an issue.
Cheers,
Arne
> On 02 Sep 2016, at 10:28, William Josefsson
Thanks everyone for your replies! I did a safe select first to make
sure there was only one match. than I updated deleted=1 for that
service which seem to work. Now 'cinder service-list' shows the right
output.
I notice in DB 'volumes', there are plenty of old volume entries, long
ago deleted,
Just be careful with LIMIT x on your servers if you have replicated mysql
databases. At least under older versions of mysql this can lead to broken
replication as the results of the query performed on the master and on the
slave are not guaranteed to be the same.
On 9/1/16, 9:51 AM, "Nick Jones" wrote:
On 1 Sep 2016, at 15:36, Jonathan D. Proulx wrote:
> On Thu, Sep 01, 2016 at 04:25:25PM +0300, Vladimir Prokofev wrote:
> :I've used direct database update to achive this in Mitaka:
> :use cinder;
On 1 Sep 2016, at 15:36, Jonathan D. Proulx wrote:
On Thu, Sep 01, 2016 at 04:25:25PM +0300, Vladimir Prokofev wrote:
:I've used direct database update to achive this in Mitaka:
:use cinder;
:update services set deleted = '1' where ;
I belive the official way is:
cinder-manage service
Hello William,
if you changed the cinder host name you need also to reflect this
change in the database for the existing volumes.
in mysql you have to do something like:
update volumes set host='newhostname#DEFAULT' where host =
'oldhostname#DEFAULT';
update volumes set host='newhostname' where
On Thu, Sep 01, 2016 at 04:25:25PM +0300, Vladimir Prokofev wrote:
:I've used direct database update to achive this in Mitaka:
:use cinder;
:update services set deleted = '1' where ;
I belive the official way is:
cinder-manage service remove
Which probably more or less does the same thing...
I've used direct database update to achive this in Mitaka:
use cinder;
update services set deleted = '1' where ;
So far I didn't encounter any negative consequences of this method.
2016-09-01 16:06 GMT+03:00 William Josefsson :
> Hi,
>
> I changed a hostname on my
Hi,
I changed a hostname on my cinder node, and now I can see two entries
in 'cinder service-list'.
How do I delete the old entry, there is no 'cinder service-delete'? In
meantime, I have disabled the old service.
Google mention cinder-manage, but I don't have that tool available on
my server
11 matches
Mail list logo