Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to bring up my node js registry client with oc 0.41.9 #696

Closed
JuniorDev4Lyf opened this issue Oct 6, 2017 · 0 comments · Fixed by #700
Closed

Not able to bring up my node js registry client with oc 0.41.9 #696

JuniorDev4Lyf opened this issue Oct 6, 2017 · 0 comments · Fixed by #700
Assignees

Comments

@JuniorDev4Lyf
Copy link
Contributor

JuniorDev4Lyf commented Oct 6, 2017

Hey guys i am not able to bring up my registry with oc 0.41.9.

Connecting to registry with following s3 configuration `
{ bucket: 'an.com-976779235782-ui-oc-library-us-east-1-development',
  region: 'us-east-1',
  path: '//s3.amazonaws.com/an.com-976779235782-ui-oc-library-us-east-1-development/',
  componentsDir: 'components',
  timeout: 600000,
  agentProxy: null,
  key: 'AWS_KEY',
  secret: 'AWS_Secret' }
/Users/sokathav/go/src/bitbucket-eng-sjc1.com/an/plainCrusader/crusader/docker/node_modules/aws-sdk/lib/request.js:31
            throw err;
            ^

TypeError: Cannot read property 'message' of undefined
    at repository.publishComponent (/Users/sokathav/go/src/bitbucket-eng-sjc1.com/an/plainCrusader/crusader/docker/node_modules/oc/src/registry/app-start.js:58:68)
    at cdn.putDir.err (/Users/sokathav/go/src/bitbucket-eng-sjc1.com/an/plainCrusader/crusader/docker/node_modules/oc/src/registry/domain/repository.js:364:28)
    at /Users/sokathav/go/src/bitbucket-eng-sjc1.com/an/plainCrusader/crusader/docker/node_modules/async/lib/async.js:52:16
    at ManagedUpload.done (/Users/sokathav/go/src/bitbucket-eng-sjc1.com/an/plainCrusader/crusader/docker/node_modules/async/lib/async.js:241:17)
    at ManagedUpload.callback (/Users/sokathav/go/src/bitbucket-eng-sjc1.com/an/plainCrusader/crusader/docker/node_modules/async/lib/async.js:44:16)
    at Response.finishSinglePart (/Users/sokathav/go/src/bitbucket-eng-sjc1.com/an/plainCrusader/crusader/docker/node_modules/aws-sdk/lib/s3/managed_upload.js:661:28)
    at Request.<anonymous> (/Users/sokathav/go/src/bitbucket-eng-sjc1.com/an/plainCrusader/crusader/docker/node_modules/aws-sdk/lib/request.js:364:18)
    at Request.callListeners (/Users/sokathav/go/src/bitbucket-eng-sjc1.com/an/plainCrusader/crusader/docker/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
    at Request.emit (/Users/sokathav/go/src/bitbucket-eng-sjc1.com/an/plainCrusader/crusader/docker/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
    at Request.emit (/Users/sokathav/go/src/bitbucket-eng-sjc1.com/an/plainCrusader/crusader/docker/node_modules/aws-sdk/lib/request.js:683:14)
SOKATHAV-M-T0KM:docker sokathav$ cat /Users/sokathav/go/src/bitbucket-eng-sjc1.com/an/plainCrusader/crusader/docker/node_modules/oc/src/registry/app-start.js

Looks like its failing when pushing the oc-client to s3 bucket and the error callback its throwing an error.

Thanks for you help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants