contrail-installer breaks R3.2 and (likely) older versions
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenContrail |
New
|
Undecided
|
Unassigned | ||
Bug Description
contrail-installer [1] had a way to build OpenContrail releases other than master for a long time. Seemingly, one just needed to adjust CONTRAIL_BRANCH in the localrc.
This behaviour appears to be broken since commit 6bd1e41, which gets rid of the discovery service. Versions prior to R4.0 still use it, and as contrail-installer doesn't provision or start discovery anymore, thus breaking the setup.
As a workaround, one can connect services manually through the corresponding config file options. This is known not to work for svc-monitor which relies on discovery for analytics-api even if you specify the endpoint manually.
A proper fix would be introduce R3.2 and other R3.x branches in contrail-installer, as it does for R2.20, and revert the commit there. Adjusting README.md (especially, pointing out which OpenStack versions are known to play well with corresponding OpenContrail releases) would also be very helpful.
