re-stack with redis failed. unstack doesn't kill redis-server

Bug #1706862 reported by Omer Anson
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
DragonFlow
Fix Released
Low
Dima Kuznetsov

Bug Description

When using df-redis-server, running stack, unstack, stack, fails.

When using df-redis-server, stack creates redis server nodes. unstack should remove them. The next stack should create them anew. However, unstack doesn't remove the servers, and therefore stack fails when trying to create them anew.

Revision history for this message
Omer Anson (omer-anson) wrote :

Set to low for the following reasons:
1. Only affects devstack and developers
2. Workaround exists: After unstack, run: killall -9 redis-server.

Dima Kuznetsov (dimakuz)
Changed in dragonflow:
status: New → Confirmed
assignee: nobody → Dima Kuznetsov (dimakuz)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to dragonflow (master)

Reviewed: https://review.openstack.org/490452
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=9373238dab9a43bec01c99e986d977069e12eb30
Submitter: Jenkins
Branch: master

commit 9373238dab9a43bec01c99e986d977069e12eb30
Author: Dima Kuznetsov <email address hidden>
Date: Thu Aug 3 15:10:18 2017 +0300

    Devstack: fix redis unstack shutdown

    [1] moved REMOTE_DB_IP definition to after sourcing redis_driver. This
    causes REDIS_SERVER_LIST to be initialized incorrectly

    [1] - https://review.openstack.org/#/c/476401/

    Change-Id: Ifb705e3ded209603813a61e4d40be126ab7fc971
    Closes-Bug: #1706862

Changed in dragonflow:
status: Confirmed → Fix Released
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.