The use of http on port 80 seems to be defined in the distributionManagement block in CCSDK here: https://git.onap.org/ccsdk/parent/tree/odlparent/odlparent-lite/pom.xml?id=c3dde295948318a40bd1a78319e197299b47e153
Thanks, Gary -----Original Message----- From: TIMONEY, DAN [mailto:dt5...@att.com] Sent: Wednesday, October 03, 2018 12:06 PM To: onap-helpd...@rt.linuxfoundation.org Cc: Gildas Lanilis <gildas.lani...@huawei.com>; agrimb...@linuxfoundation.org; FREEMAN, BRIAN D <bf1...@att.com>; Gary Wu <gary.i...@huawei.com>; LEFEVRE, CATHERINE <catherine.lefe...@intl.att.com>; onap-discuss@lists.onap.org Subject: Re: [ONAP Helpdesk #61676] gerrit down Jess, I took a closer look at that error below. Not only is the staging plugin using port 80, but it's using http, not https. I checked my configuration and verified that I'm using https://nexus.onap.org not http://nexus.onap.org. I have no clue where that's coming from, unless our settings.xml in Jenkins is somehow messed up (I can't see that directly) 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/3/18, 11:26 AM, "TIMONEY, DAN" <dt5...@att.com> wrote: Jess, I'm still seeing this problem this morning. You ask an excellent question about port 80. I checked my configuration and verified that we're using https://nexus.onap.org with no port specified - so it should be port 443, not 80. This error is happening within the staging plugin, which I personally have been railing against for over a year now ... this is just the latest in a series of problems with that wonderful plugin, the others being: 1) It occasionally loses track of which is the latest version of a jar file (which I think Andrew created a workaround for last year). 2) For zip files (which we use as installation bundles), if you try to pull a specific version from the staging repository, you'll consistently get the very first copy ever pushed, not the latest. You can see that actually if you look at the artifacts in the nexus web page - for jar files, you'll see a list of autogenerated repos but for zip files you'll only see the first. So, it looks like yet another issue in the staging plugin .... if you don't explicitly provide a port, it defaults to 80 even for https, which is just plain wrong. I'll try seeing if I can get around this by explicitly setting the port to 443 in the staging url, but if that's the problem ,we should really get Sonatype to fix it. 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, 6:49 PM, "Jessica Wagantall via RT" <onap-helpd...@rt.linuxfoundation.org> wrote: Hi Dan, Looking into this issue. Why are we using port 80? : https://urldefense.proofpoint.com/v2/url?u=http-3A__nexus.onap.org-3A80&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Ms-DNhR23dO4sQFfYRm4ow&m=9BsdxCi7UWgNWFeVZnwuitt1LsK6wdh0bsG3J-s2mTE&s=8qfiU_gE41IyWoPbuFI1liIVFnxglXe9ybT4xnDI4Vo&e=: Nothing changed for Nexus servers on Friday. The only migration that happened was for Gerrit. thanks a ton! Jess On Tue Oct 02 15:03:09 2018, dt5...@att.com wrote: > 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 {}->https://urldefense.proofpoint.com/v2/url?u=http-3A__nexus.onap.org-3A80&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Ms-DNhR23dO4sQFfYRm4ow&m=9BsdxCi7UWgNWFeVZnwuitt1LsK6wdh0bsG3J-s2mTE&s=8qfiU_gE41IyWoPbuFI1liIVFnxglXe9ybT4xnDI4Vo&e=: 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 > (https://urldefense.proofpoint.com/v2/url?u=http-3A__nexus.onap.org_content_repositories_snapshots&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Ms-DNhR23dO4sQFfYRm4ow&m=9BsdxCi7UWgNWFeVZnwuitt1LsK6wdh0bsG3J-s2mTE&s=EiwDg5DnN7NKAKMUGa1uPirJhkJGUeAnGN7lBaMlHwQ&e=): 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" <bf1...@att.com> 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: onap-discuss@lists.onap.org; gary.i...@huawei.com; DRAGOSH, PAM > <pdrag...@research.att.com>; onap-helpd...@rt.linuxfoundation.org; > gildas.lani...@huawei.com > Cc: FREEMAN, BRIAN D <bf1...@att.com>; LEFEVRE, CATHERINE > <catherine.lefe...@intl.att.com> > 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, "onap-discuss@lists.onap.org on behalf of Gary > Wu" <onap-discuss@lists.onap.org on behalf of gary.i...@huawei.com> > 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: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] > On Behalf Of Pamela Dragosh > > Sent: Tuesday, October 02, 2018 10:12 AM > > To: onap-helpd...@rt.linuxfoundation.org > > Cc: onap-discuss@lists.onap.org > > 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" <onap- > helpd...@rt.linuxfoundation.org> wrote: > > > > On 10/02/2018 06:56 AM, pdrag...@research.att.com 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 (#12823): https://lists.onap.org/g/onap-discuss/message/12823 Mute This Topic: https://lists.onap.org/mt/26661009/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
