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

Inspector coverage inconsistent with actual configuration #6354

Closed
achave11-ucsc opened this issue Jun 21, 2024 · 8 comments
Closed

Inspector coverage inconsistent with actual configuration #6354

achave11-ucsc opened this issue Jun 21, 2024 · 8 comments
Assignees
Labels
+ [priority] High bug [type] A defect preventing use of the system as specified demo [process] To be demonstrated at the end of the sprint demoed [process] Successfully demonstrated to team infra [subject] Project infrastructure like CI/CD, build and deployment scripts operator [process] To be addressed by whoever is operator orange [process] Done by the Azul team

Comments

@achave11-ucsc
Copy link
Member

achave11-ucsc commented Jun 21, 2024

In anvilprod, the Inspector console indicates that the container images in ECR are not configured to be actively/continuously monitored and are all listed in the 'Not scanning' tab. Since they are supposedly scanned manually. However, this is contradictory with the information in the scanning settings for the images within the ECR console.

In the following screenshot from the Inspector console, it appears as if non of the images in ECR are configured for continuous scans.
CleanShot 2024-06-20 at 18 24 05@2x

But in ECR, the scan configuration is contradictory to the one shown in the Inspector console.
Screenshot 2024-06-20 at 7 28 35 PM

Furthermore, Inspector's last scanned date for the container images highlighted in the following screenshot …
Screenshot 2024-06-20 at 7 38 36 PM
is not congruent with the scan details of the image as seen from the ECR console.
Screenshot 2024-06-20 at 7 35 33 PM
Screenshot 2024-06-20 at 7 39 18 PM

The expectation for the Inspector console in the affected deployments is for it to resemble the one of the tempdev. With most container images configured with the 'Actively monitoring' status.
CleanShot 2024-06-20 at 18 27 18@2x

@achave11-ucsc achave11-ucsc added the orange [process] Done by the Azul team label Jun 21, 2024
@achave11-ucsc achave11-ucsc self-assigned this Jun 21, 2024
@achave11-ucsc
Copy link
Member Author

Assignee to provide screenshots with reproduction.

@achave11-ucsc achave11-ucsc removed their assignment Jun 21, 2024
@dsotirho-ucsc
Copy link
Contributor

dsotirho-ucsc commented Jun 24, 2024

@hannes-ucsc: "Assignee to open support ticket with AWS. Focus on the docker Docker image."

@dsotirho-ucsc dsotirho-ucsc self-assigned this Jun 24, 2024
@dsotirho-ucsc dsotirho-ucsc added bug [type] A defect preventing use of the system as specified infra [subject] Project infrastructure like CI/CD, build and deployment scripts + [priority] High labels Jun 24, 2024
@dsotirho-ucsc
Copy link
Contributor

Opened AWS Support case 171927048400112 on anvilprod.

@dsotirho-ucsc
Copy link
Contributor

@hannes-ucsc: "We discovered during the upgrade PR that newly pushed images are being scanned and show up as covered in Inspector. This leads me to believe that the problem will slowly fix itself once we push updates to all images. Assignee to close AWS Support ticket with the following statement: 'AWS Support confuses custom image tags with base image layers. While it is true that recently the OS in the base image of the image in question had not been supported, support for Alpine 3.20 was recently added. Furthermore, our evidence shows that the error message indicates that the scans are manual, not that the image is not supported (the status message for that would contain the word 'unsupported').' "

@dsotirho-ucsc
Copy link
Contributor

dsotirho-ucsc commented Jul 1, 2024

Assignee to delete any images still affected and to re-upload them by deploying the shared component, as part of the merging of the upgrade and promotion PRs.

@dsotirho-ucsc dsotirho-ucsc added the operator [process] To be addressed by whoever is operator label Jul 1, 2024
@dsotirho-ucsc
Copy link
Contributor

Assignee to delete any images still affected and to re-upload them by deploying the shared component, as part of the merging of the upgrade and promotion PRs.

Added CL items to current upgrade PR #6361

@dsotirho-ucsc
Copy link
Contributor

AWS Support ticket has been closed and feedback about the ticket was submitted

@hannes-ucsc hannes-ucsc added the demo [process] To be demonstrated at the end of the sprint label Jul 3, 2024
@hannes-ucsc
Copy link
Member

For demo, attempt to reproduce.

@dsotirho-ucsc dsotirho-ucsc added the demoed [process] Successfully demonstrated to team label Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
+ [priority] High bug [type] A defect preventing use of the system as specified demo [process] To be demonstrated at the end of the sprint demoed [process] Successfully demonstrated to team infra [subject] Project infrastructure like CI/CD, build and deployment scripts operator [process] To be addressed by whoever is operator orange [process] Done by the Azul team
Projects
None yet
Development

No branches or pull requests

3 participants