-
Bug
-
Resolution: Fixed
-
Low
-
Assets - AWS Integration 2.2.14, Assets - AWS Integration 2.2.17, 10.3.0
-
1
-
Severity 3 - Minor
-
Issue Summary
AWS Assets integration does not fetch Docker objects from AWS
Steps to Reproduce
- Create an AWS import
- Disable all Object Types except "Docker Image" and "Repository"
- Run the import
Expected Results
Dockers Objects should be imported into Assets
Actual Results
No Docker images objects are being fetch from AWS. The following exception is seen in the atlassian-jira logs
2025-03-07 15:25:27,416+0200 insight-InsightImportThreadGroup-1564-worker-thread-2 DEBUG xxx [o.apache.http.wire] http-outgoing-3584 << "{"__type":"InvalidParameterException","message":"Invalid parameter at 'repositoryName' failed to satisfy constraint: 'must not be null'"}" 2025-03-07 15:25:27,416+0200 insight-InsightImportThreadGroup-1564-worker-thread-2 DEBUG xxx [com.amazonaws.request] Received error response: com.amazonaws.services.ecr.model.InvalidParameterException: Invalid parameter at 'repositoryName' failed to satisfy constraint: 'must not be null' (Service: AmazonECR; Status Code: 400; Error Code: InvalidParameterException; Request ID: 88994d3b-099a-464c-b93e-41586aef7527; Proxy: null) 2025-03-07 15:25:27,416+0200 insight-InsightImportThreadGroup-1564-worker-thread-2 ERROR xxx [c.r.j.p.a.i.m.impl.ecr.DockerImageService] Error fetch AWS ECR Docker Image response com.amazonaws.services.ecr.model.InvalidParameterException: Invalid parameter at 'repositoryName' failed to satisfy constraint: 'must not be null' (Service: AmazonECR; Status Code: 400; Error Code: InvalidParameterException; Request ID: 88994d3b-099a-464c-b93e-41586aef7527; Proxy: null) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1879) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleServiceErrorResponse(AmazonHttpClient.java:1418) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1387) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1157) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:814) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:781) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:755) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:715) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:697) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:561) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:541) at com.amazonaws.services.ecr.AmazonECRClient.doInvoke(AmazonECRClient.java:3487) at com.amazonaws.services.ecr.AmazonECRClient.invoke(AmazonECRClient.java:3454) at com.amazonaws.services.ecr.AmazonECRClient.invoke(AmazonECRClient.java:3443) at com.amazonaws.services.ecr.AmazonECRClient.executeDescribeImages(AmazonECRClient.java:1468) at com.amazonaws.services.ecr.AmazonECRClient.describeImages(AmazonECRClient.java:1437) at com.riadalabs.jira.plugins.aws.imports.manager.impl.ecr.DockerImageService.retrieveData(DockerImageService.java:176) at com.riadalabs.jira.plugins.aws.imports.manager.impl.ecr.DockerImageService.retrieveData(DockerImageService.java:43) at com.riadalabs.jira.plugins.aws.imports.manager.AssetsAWSSupplier.get(AssetsAWSSupplier.java:24)
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
This is available in version 2.2.18
https://marketplace.atlassian.com/apps/1218757/assets-aws-integration?hosting=datacenter&tab=overview