https://bugzilla.wikimedia.org/show_bug.cgi?id=61508

            Bug ID: 61508
           Summary: [Regression] Jenkins: Jobs for npm testing are broken
                    due to npm certificate issues on the new slaves
           Product: Wikimedia
           Version: wmf-deployment
          Hardware: All
                OS: All
            Status: NEW
          Severity: blocker
          Priority: Unprioritized
         Component: Continuous integration
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected],
                    [email protected]
       Web browser: ---
   Mobile Platform: ---

Last working job:
  https://integration.wikimedia.org/ci/job/mwext-VisualEditor-npm/942/console

  - Feb 16, 2014
  - Building remotely on integration-slave01

  - node v0.10.22
  - npm v1.1.38

First failing job:
  https://integration.wikimedia.org/ci/job/mwext-VisualEditor-npm/943/console

  - Feb 18, 2014
  - Building remotely on integration-slave02

  - node v0.8.2
  - npm v1.1.39

16:23:41 npm ERR! Error: SSL Error: CERT_UNTRUSTED
16:23:41 npm ERR!     at ClientRequest.<anonymous> 
16:23:41 npm ERR!     at Socket.ondata (stream.js:38:26)
16:23:41 npm ERR!  [Error: SSL Error: CERT_UNTRUSTED]

Server log:
 
https://wikitech.wikimedia.org/w/index.php?title=Server_Admin_Log&diff=99596&oldid=99549


  - February 17
    - 16:15 hashar: Jenkins deleting slave integration-slave01
    - 16:14 hashar: Jenkins added two labs slaves with 4 CPU:
integration-slave02 and integration-slave03
    - 08:46 hashar: Upgrading Jenkins, half an hour downtime



So npm was upgraded one minor version, and nodejs was downgraded *2 major
versions*, and (possibly unrelated) it seems to be unable to verify the
certificate properly.

According to existing bug reports, this is related to it being a self-signed
certificate, however this shouldn't be a problem since a validation mechanism
for their official certificate ships with the npm package. Upstream recommends
upgrading to the most recent minor version, but that doesn't seem to be the
problem considering the bug started happening for us overnight (no certificate
change upstream) when we went from v1.1.38 to v1.1.39 (not down).

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to