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

ResourceNotFoundException during initial deploy of shared component #6252

Open
hannes-ucsc opened this issue May 11, 2024 · 2 comments
Open
Labels
-- [priority] Low bug [type] A defect preventing use of the system as specified debt [type] A defect incurring continued engineering cost infra [subject] Project infrastructure like CI/CD, build and deployment scripts needs design [process] Solution to issue has yet to be devised orange [process] Done by the Azul team spike:2 [process] Spike estimate of two points

Comments

@hannes-ucsc
Copy link
Member

The first deployment of the shared component in a newly created AWS account fails like this:

│ Error: putting CloudWatch Logs Metric Filter (): ResourceNotFoundException: The specified log group does not exist.
│ 
│   with aws_cloudwatch_log_metric_filter.clamscan,
│   on shared.tf.json line 511, in resource[12].aws_cloudwatch_log_metric_filter[11].clamscan:
│  511:                     }
│ 
╵
╷
│ Error: putting CloudWatch Logs Metric Filter (): ResourceNotFoundException: The specified log group does not exist.
│ 
│   with aws_cloudwatch_log_metric_filter.freshclam,
│   on shared.tf.json line 524, in resource[12].aws_cloudwatch_log_metric_filter[12].freshclam:
│  524:                     }
│ 
╵
╷
│ Error: putting CloudWatch Logs Metric Filter (): ResourceNotFoundException: The specified log group does not exist.
│ 
│   with aws_cloudwatch_log_metric_filter.clam_fail,
│   on shared.tf.json line 537, in resource[12].aws_cloudwatch_log_metric_filter[13].clam_fail:
│  537:                     }
│

A retry results in the same error.

@hannes-ucsc hannes-ucsc added the orange [process] Done by the Azul team label May 11, 2024
@achave11-ucsc
Copy link
Member

Assignee to consider next steps.

@achave11-ucsc achave11-ucsc added spike:2 [process] Spike estimate of two points + [priority] High -- [priority] Low and removed + [priority] High labels Jun 10, 2024
@achave11-ucsc
Copy link
Member

Spike for design.

@hannes-ucsc hannes-ucsc added needs design [process] Solution to issue has yet to be devised bug [type] A defect preventing use of the system as specified debt [type] A defect incurring continued engineering cost infra [subject] Project infrastructure like CI/CD, build and deployment scripts labels Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-- [priority] Low bug [type] A defect preventing use of the system as specified debt [type] A defect incurring continued engineering cost infra [subject] Project infrastructure like CI/CD, build and deployment scripts needs design [process] Solution to issue has yet to be devised orange [process] Done by the Azul team spike:2 [process] Spike estimate of two points
Projects
None yet
Development

No branches or pull requests

3 participants