should we open a separate ticket on nexus.onap.org connection reset on push ?
Brian -----Original Message----- From: TIMONEY, DAN Sent: Tuesday, October 02, 2018 3:03 PM To: FREEMAN, BRIAN D <[email protected]>; [email protected]; [email protected]; DRAGOSH, PAM <[email protected]>; [email protected]; [email protected] Cc: LEFEVRE, CATHERINE <[email protected]> Subject: Re: [onap-discuss] [ONAP Helpdesk #61676] gerrit down All, FYI - I hoped to work around this issue by commenting out a module that isn't critical from our build, hoping to reduce load. Didn't help - just moved the problem to someplace else. Here's the error I'm getting: 18:43:05 [INFO] Installing /w/workspace/sdnc-oam-master-merge-java/pom.xml to /w/workspace/sdnc-oam-master-merge-java/admportal/target/nexus-staging/deferred/org/onap/sdnc/oam/sdnc-oam/1.4.0-SNAPSHOT/sdnc-oam-1.4.0-SNAPSHOT.pom 18:43:05 [INFO] Deploying remotely... 18:43:05 [INFO] Bulk deploying locally gathered artifacts from directory: 18:43:05 [INFO] * Bulk deploying locally gathered snapshot artifacts 18:45:14 Oct 02, 2018 6:45:14 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute 18:45:14 INFO: I/O exception (java.net.SocketException) caught when processing request to {}->http://nexus.onap.org:80: Connection reset .... 18:46:47 [ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:deploy (injected-nexus-deploy) on project sdnc-oam: Failed to deploy artifacts: Could not transfer artifact org.onap.sdnc.oam:platform-logic-installer:zip:1.4.0-20181002.184326-145 from/to ecomp-snapshots (http://nexus.onap.org/content/repositories/snapshots): Connection reset -> [Help 1] So while the error is happening on Jenkins, it seems that Nexus is really the culprit. Dan -- Dan Timoney SDN-CP Development ONAP Project Technical Lead : CCSDK and SDNC Please go to D2 ECOMP Release Planning Wiki <https://wiki.web.att.com/display/DERP/D2+ECOMP+Release+Planning+Home> for D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find key Release Planning Contact Information. On 10/2/18, 2:14 PM, "FREEMAN, BRIAN D" <[email protected]> wrote: Gildas, Help - this is blocking instantiation testing because we cant distribute the models without a new sdnc docker. Brian -----Original Message----- From: TIMONEY, DAN Sent: Tuesday, October 02, 2018 2:11 PM To: [email protected]; [email protected]; DRAGOSH, PAM <[email protected]>; [email protected]; [email protected] Cc: FREEMAN, BRIAN D <[email protected]>; LEFEVRE, CATHERINE <[email protected]> Subject: Re: [onap-discuss] [ONAP Helpdesk #61676] gerrit down All, Whatever can be done to alleviate this would be helpful. To echo Pam's point, last Friday, all my merges were taking over 90 minutes - or rather, they were running for 90 minutes then getting killed. I've been working now for a week just on doing release builds. The last one failed this morning due to socket connection dropped errors with Nexus. I tried pushing a change to skip the jar that was hitting that error to see if that helps - the verify job for that change just finished after 1 hour and 20 mins. Gildas - this constitutes a jeopardy on our Casablanca release. We are completely blocked until this gets better : we can't create new docker containers to test what we already have; we can't merge anything new. The factory is essentially closed for business. Dan -- Dan Timoney SDN-CP Development ONAP Project Technical Lead : CCSDK and SDNC Please go to D2 ECOMP Release Planning Wiki <https://wiki.web.att.com/display/DERP/D2+ECOMP+Release+Planning+Home> for D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find key Release Planning Contact Information. On 10/2/18, 2:01 PM, "[email protected] on behalf of Gary Wu" <[email protected] on behalf of [email protected]> wrote: It seems like nexus and nexus3 are suffering severe congestion right now, so the jobs are spending a long time trying to download artifacts. Maybe we should consider migrating those systems to AWS as well? Thanks, Gary -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Pamela Dragosh Sent: Tuesday, October 02, 2018 10:12 AM To: [email protected] Cc: [email protected] Subject: Re: [onap-discuss] [ONAP Helpdesk #61676] gerrit down This just started this morning. Seems to have been resolved as folks can now submit changes. Nobody hard codes any IP address, their environments haven’t changed in months. These were separate firewalls. But jenkins is really, really slow today and failing to finish verify and merge jobs. Pam On 10/2/18, 11:49 AM, "Andrew Grimberg via RT" <[email protected]> wrote: On 10/02/2018 06:56 AM, [email protected] via RT wrote: > > It seems that multiple folks on my team across the US cannot submit a > gerrit review. It either hangs or gives a connection refused. > Greetings Pam, Is this a problem that people have been having (and are still having) since the maintenance of Gerrit on Friday? If so, it sounds like there's possibly corporate firewalls blocking access then as the ONAP Gerrit system is working just fine for me and I've seen no alarms from our monitoring. The new system is now behind an Amazon ELB and does not have hard and firm IP addresses. My experience with these sorts of systems is that the addresses will change with no notice and no control on our part but as Amazon remanages the addresses in their own system. The _current_ IP addresses are: 35.166.47.83 and 35.164.144.118 -Andy- -- Andrew J Grimberg Manager Release Engineering The Linux Foundation -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12797): https://lists.onap.org/g/onap-discuss/message/12797 Mute This Topic: https://lists.onap.org/mt/26661009/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
