VCA-LCM relationship not working
Bug #1890419 reported by
Eduardo Sousa
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical-OSM |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
While deploying Charmed OSM, I faced a problem with the CMR between VCA and LCM, where the data from the VCA is not being passed. This results in the LCM pod not starting because it cannot access the VCA, with the error that the N2VC Certificate is wrongly padded.
I'm deploying using FCE 2.6, Juju 2.7.8, VCA charm revision 6 and LCM charm revision 43.
Note: the workaround I'm using is by not specifying the CMR between LCM and VCA and by passing the VCA values as config values to the LCM charm.
Revision history for this message
| David (davigar15) wrote | #1 |
| Changed in canonical-osm: | |
| status: | New → Won't Fix |
To post a comment you must log in.
This is related to the way we used to deploy the VCA (in a charm), and we related that to LCM and MON.
The VCA shouldn't be deployed inside a charm. Instead, the proper config params should be passed to LCM and MON in order for them to be able to connect to the VCA.