[FOLIO-1923] stripes fails to build on ec2 instances reports 403 finding electron package Created: 29/Mar/19 Updated: 03/Jun/20 Resolved: 02/Apr/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | Ian Hardy | Assignee: | John Malconian |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | devops, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | Core: Platform |
| Description |
|
Stripes fails to build on ec2 instaces, reports 403 response trying to download electron package from github. This has only been observed on ec2 instances: $ node install.js Downloading electron-v1.8.8-linux-x64.zip Error: GET https://github.com/electron/electron/releases/download/v1.8.8/electron-v1.8.8-linux-x64.zip returned 403 /etc/folio/stripes.test/node_modules/electron/install.js:47 throw err |
| Comments |
| Comment by John Malconian [ 29/Mar/19 ] |
|
@Ian - I notice that while folio-snapshot-core and folio-snapshot builds fail due to this issue, folio-testing does not. folio-testing is set up a bit different than the snapshot builds. For example, for folio-testing, the Nodejs environment is not updated on the system where stripes is built. I also can’t reproduce the failure on Jenkins slave nodes where we are still running NodeJS 9.x. So I’m guessing this is some kind of environment issue. I’m wondering if there has been a recent change in the Node JS environment on the snapshot builds. Perhaps a newer version of Node that gets installed. |
| Comment by John Malconian [ 29/Mar/19 ] |
|
Seems folio-testing and folio-snapshot have the same Node environment - v10.15.3. So much for that theory. Yarn is at different versions, however: folio-snapshot - yarn=v1.15.2 The weird thing is, however, if I log into the last successful instance of folio-snapshot and attempt to rebuild stripes by hand, I get the error. So the initial stripes build on the system was good, but subsequent attempts since yesterday fail. So, while I think the issue is environmental, I'm not sure it has much to do with the system environment. |
| Comment by John Malconian [ 29/Mar/19 ] |
|
New update: Now (sheesh) I can build stripes by hand on the current folio-snapshot where I couldn't yesterday with the following environment: yarn config v1.15.2
info yarn config
{ 'version-tag-prefix':
'v',
'version-git-tag':
true,
'version-commit-hooks':
true,
'version-git-sign':
false,
'version-git-message':
'v%s',
'init-version':
'1.0.0',
'init-license':
'MIT',
'save-prefix':
'^',
'bin-links':
true,
'ignore-scripts':
false,
'ignore-optional':
false,
registry:
'https://repository.folio.org/repository/npm-ci-all',
'strict-ssl':
true,
'user-agent':
'yarn/1.15.2 npm/? node/v10.15.3 linux x64',
lastUpdateCheck:
1553793679820 }
info npm config
{ '@folio:registry':
'https://repository.folio.org/repository/npm-folioci/' }
|
| Comment by John Malconian [ 29/Mar/19 ] |
|
And now I can build stripes on the folio-snapshot-core instance that just failed a few minutes ago (Build 143). Going to attempt another folio-snapshot-core build. |
| Comment by John Malconian [ 29/Mar/19 ] |
|
Build 144 of folio-snapshot-core succeeded . We either have an intermittent issue (the best kind!) or an issue that has passed. Going to try a build of folio-snapshot now. |
| Comment by John Malconian [ 29/Mar/19 ] |
|
folio-snapshot build fails but for not related to this issue. https://jenkins-aws.indexdata.com/job/Automation/job/folio-snapshot/631/console Let's keep this issue open for a bit to monitor. |
| Comment by John Malconian [ 02/Apr/19 ] |
|
Haven't seen this issue re-occur. Closing. |