Cannot run fuxi & kuryr-libnetwork together in devstack
Bug #1683852 reported by
hongbin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuxi |
Fix Released
|
Undecided
|
Unassigned | ||
| kuryr-libnetwork |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
If run ./stack with both fuxi and kuryr-libnetwork enabled, the script will fail. At the 'stack' screen, I saw two tabs with 'etcd-server' and one of the etcd process failed because there is already an etcd process running.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to kuryr-libnetwork (master) | #1 |
| Changed in kuryr-libnetwork: | |
| status: | New → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to fuxi (master) | #2 |
| Changed in fuxi: | |
| status: | New → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/fuxi 0.2.0 | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kuryr-libnetwork 0.2.0 | #5 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5c45b19273039df
Author: Hongbin Lu <email address hidden>
Date: Mon Apr 17 18:22:18 2017 -0400
Avoid running more than one etcd process
If both Fuxi and Kuryr-libnetwork are enabled in devstack, the script
will fail since etcd-server was spawned twice. This commit added a
check for existing etcd process and spawn one if not existed.
Closes-Bug: #1683852
Change-Id: Iecef71df1c0b58