Age | Commit message (Collapse) | Author | Files | Lines |
|
Sync OOM docker versions with docker-manifest.csv commit
a6e05c8c18624a1794abb1d3a3ab879a7a06bcfe
Change-Id: If8df538638670e0f1080d41d40d06de54ab1d93a
Issue-ID: OOM-1053
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Addressing issues like:
- missing property files
- hard-coded ports
- hard-coded ODL passwords
- improper configMap mounts
- incorrect service names
Change-Id: I74726ffedbfc20e164a814ca8777a699b92b3d65
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: SDNC-310
|
|
Change-Id: I2d1ff878c215becc9856af184eb0b11defd75e1d
Issue-ID: OOM-1064
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
This seems to have been broken when the dmaap /
message-router refactor happene.
Change-Id: I09ade07fe5f2eb6d7be0eb1ed29656f6a6761f0a
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: SDNC-308
|
|
DMaaP listener was not trying to connect to the right service name, so
it was failing.
In addition, the pod doesn't wait for the dmaap pod to be up and running
before starting, so I've added that dependency.
Lastly, I removed the config of the DMaaP port from the top level values.yaml
files, as out of the box it's very unlikely this would be changed.
Change-Id: I5a190b39f4f163b020189ac9dd178040f80125cd
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: SDNC-293
|
|
Issue-ID: OOM-906
Change-Id: Ic65127d3981cb0a696c784392cab59fbf06b1e66
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Readiness check version is not sinchronized in many pods
This causing deployment failures.
Issue-ID: OOM-936
Change-Id: Ieef91df17836adcdf24db536440d0a1624a50591
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Change-Id: I9f4d43c2a3f0766b9c8477a180f5a0bd45fde243
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-748
|