Workaround for master temporarily is to remove robot from HELM_APPS in your setenv.bash Until you need something from robot. /michael
From: Michael O'Brien Sent: Tuesday, March 20, 2018 18:46 To: [email protected] Subject: [OOM] master - helm issue specific to robot being addressed in OOM-815 Team, Ran into a deployment issue while investigating workarounds for OOM-813. Looks like we are either missing config or waiting for a container rebuild since around 8 this morning. Since the dynamic master CD systems have been down since Friday (openlab/tlab and azure) because of OOM-813 - they don't pick up this additional breakage. The static CD build (still running on Rancher 1.6.14 before Friday) on AWS did pick it up - the last build that passed healthcheck was 12 hours ago around 7am EDT (GMT-5) http://jenkins.onap.info/job/oom-cd/2422/console The developer of the merged change has been notified - it may be just a merge timing issue. Track the change in https://jira.onap.org/browse/OOM-815 Testing your change in an integration build. Currently master is having issues with an updated version of rancher 1.6.14 that we are looking at - see https://lists.onap.org/pipermail/onap-discuss/2018-March/008706.html so merging your change and testing after the commit is going to be problematic if you have built your kubernetes system post last Friday until we track down a workaround Testing 1.6.13, 1.6.14+kubectl 1.8.9 to start. Michael O'Brien Amdocs Technology 16135955268 55268 [amdocs-a] This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
