machines deployed may have conflict ip with compass server
Bug #1321056 reported by
Jerry Zhao
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Compass |
Fix Committed
|
Undecided
|
Unassigned | ||
Bug Description
management ip is in the same subnet as compass server, ip to start needs to avoid overlap with compass server ip.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to compass-core (master) | #1 |
| Changed in compass: | |
| status: | New → Fix Committed |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit b7e7ad6d99337c9
Author: zhaoxinyu <email address hidden>
Date: Tue May 20 00:43:47 2014 +0000
Bump up mgmt ip start to avoid conflict with compass server
now start from *.*.*.10 but test slaves where compass server
is can be out of 10 so a conflict might happen, so increase
to 50.
pin pycrypto version to 2.0.1 and below
Keystone client grizzly version only work with pycrypto below 2.0.1,
so pin pycrypto to 2.0.1 and below.
Closes-Bug: 1321032
Closes-Bug: 1321056
Change-Id: I2f72937ee128d3