-
Notifications
You must be signed in to change notification settings - Fork 45
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
[BUG] Module deployment failure: jupyter-hub #583
Comments
You can try this before merge, I need to test from the groundup so this may take awhile before its merged. File: name: jupyter-hub
path: git::https://github.com/awslabs/autonomous-driving-data-framework.git//modules/demo-only/jupyter-hub?ref=chore/583&depth=1 |
unfortunately,
doesn't work for me:
|
with
I got the following error: ...
|
please find the attached the codebuild log for jupyter-hub module: jupyter-hub_CodeBuild.log |
@serge-dolgavin-dxc Can you try this module from |
Sorry that my messages are not clear and for confusion. I have recognized that the branch was deleted and I am already using The yesterday's codebuild log for jupyter-hub module is based of the recent |
Gotcha missed that, taking a look... |
@serge-dolgavin-dxc Are you able to provide the trust policy for |
@malachi-constant , please find the attached policy details along with the latest codebuild log. |
Ok so the trust is not being added for some reason, can you also tell me which version of the eks module is deployed? |
I am using the latest main branch (default demo / example-dev manifests).
|
Ok thanks, was able to replicate, working on it... |
See manifest in PR This error is resolved by updating name: jupyter-hub
path: modules/demo-only/jupyter-hub/
parameters:
- name: eks-cluster-admin-role-arn
valueFrom:
moduleMetadata:
group: core
name: eks
key: EksClusterMasterRoleArn |
@malachi-constant , thanks a lot for your help! I was able to deploy
Unfortunately, I got two issues after the deployment:
Please notice regions. ADDF demo was deployed in eu-west-1, not eu-central-1.
Could you please advise how to address these issues? |
I think your credentials for kubectl are pointing to the wrong cluster (do you have multiple clusters defined in .kube?)...this command: |
@dgraeber , thanks a lot for your hint! addf-demo-core-eks-cluster configuration was missing. The first issue was solved, but the second still remain. Is it an issue with access rights? |
Describe the bug
addf-demo-ide-jupyter-hub deployment failure, due to no longer supported runtime.
To Reproduce
deploy jupyter-hub module
Expected behavior
jupyter-hub deployed without issues
Screenshots
na
Additional context
...
Failed resources:
addf-demo-ide-jupyter-hub | 10:17:07 AM | CREATE_FAILED | AWS::Lambda::Function | AWSCDKCfnUtilsProviderCustomResourceProvider/Handler
handler returned message: "The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions. We recommend you use a supported runtime while creating or updating functions. (Service: Lambda, Status Code: 400,
❌ addf-demo-ide-jupyter-hub failed: Error: The stack named addf-demo-ide-jupyter-hub failed creation, it may need to be manually deleted from the AWS console: ROLLBACK_COMPLETE
...
The text was updated successfully, but these errors were encountered: