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

OCM-13218 | test: fix the failure of cluster provision and resource clean up #2739

Merged
merged 1 commit into from
Dec 24, 2024

Conversation

xueli181114
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 23, 2024
@xueli181114 xueli181114 force-pushed the OCM-12112 branch 2 times, most recently from 71c3505 to 60118d5 Compare December 23, 2024 08:11
Copy link

codecov bot commented Dec 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 29.11%. Comparing base (d980017) to head (60118d5).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2739   +/-   ##
=======================================
  Coverage   29.11%   29.11%           
=======================================
  Files         185      185           
  Lines       25805    25805           
=======================================
  Hits         7513     7513           
  Misses      17693    17693           
  Partials      599      599           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

AuditLogArn string `json:"audit_log,omitempty"`
DNSDomain string `json:"dns_domain,omitempty"`
EtcdKMSKey string `json:"etcd_kms_key,omitempty"`
FromSharedAWSAccount *FromSharedAWSAccount `json:"from_shard_aws_account,omitempty"`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo error from_shard_aws_account?

ResourceShareArn string `json:"resource_share,omitempty"`
SharedVPCRole string `json:"shared_vpc_role,omitempty"`
VpcID string `json:"vpc_id,omitempty"`
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which resources are created by the regular AWS account, and which resources are created by the Shared AWS account, it is better to separate the resources created by the Shared AWS account in an individual block.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is a better resolution needs more research to see if any other place relied on the resources.json. How about make this merged to resolve the problem of resources leak which is affecting all CI jobs?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK

@yasun1
Copy link
Contributor

yasun1 commented Dec 24, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 24, 2024
Copy link
Contributor

openshift-ci bot commented Dec 24, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xueli181114, yasun1

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 06c25f5 into openshift:master Dec 24, 2024
9 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants