Skip to content

Conversation

@Miciah
Copy link
Contributor

@Miciah Miciah commented Apr 27, 2023

  • .github/ISSUE_TEMPLATE/config.yml: Update the Bugzilla link to point instead to the Red Hat Issue Tracker.
  • OWNERS: Remove the component field. Add past approvers to emeritus_approvers and remove them from the approvers and reviewers lists.

This commit fixes OCPBUGS-12790.

https://issues.redhat.com/browse/OCPBUGS-12790

* .github/ISSUE_TEMPLATE/config.yml: Update the Bugzilla link to point
instead to the Red Hat Issue Tracker.
* OWNERS: Remove the component field.  Add past approvers to
emeritus_approvers and remove them from the approvers and reviewers lists.
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Apr 27, 2023
@openshift-ci-robot
Copy link
Contributor

@Miciah: This pull request references Jira Issue OCPBUGS-12790, which is invalid:

  • expected the bug to target the "4.14.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

  • .github/ISSUE_TEMPLATE/config.yml: Update the Bugzilla link to point instead to the Red Hat Issue Tracker.
  • OWNERS: Remove the component field. Add past approvers to emeritus_approvers and remove them from the approvers and reviewers lists.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 27, 2023
@Miciah
Copy link
Contributor Author

Miciah commented Apr 27, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Apr 27, 2023
@openshift-ci-robot
Copy link
Contributor

@Miciah: This pull request references Jira Issue OCPBUGS-12790, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @melvinjoseph86

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 27, 2023
@candita
Copy link
Contributor

candita commented Apr 27, 2023

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 27, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 27, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: candita

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

The pull request process is described here

Details 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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 27, 2023
@candita
Copy link
Contributor

candita commented Apr 27, 2023

Fixes #911

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 469a84e and 2 for PR HEAD e5382b2 in total

@Miciah
Copy link
Contributor Author

Miciah commented Apr 28, 2023

e2e-aws-operator failed because cluster provisioning failed:

level=error msg=Error: error waiting for EC2 NAT Gateway (nat-049be124c157e0bed) create: unexpected state 'failed', wanted target 'available'. last error: InvalidSubnetID.NotFound: The specified subnet subnet-0ee9d367220d0beb2 does not exist 

/test e2e-aws-operator

e2e-gcp-operator failed because the machine-config clusteroperator failed:

{Operator unavailable (MachineConfigControllerFailed): Cluster not available for [{operator 4.14.0-0.ci.test-2023-04-27-172910-ci-op-8lsi16gg-latest}]: ControllerConfig.machineconfiguration.openshift.io "machine-config-controller" is invalid: [spec.dns.apiVersion: Required value: must not be empty, spec.dns.kind: Required value: must not be empty, <nil>: Invalid value: "null": some validation rules were not checked because the object was invalid; correct the existing errors to complete validation]  Operator unavailable (MachineConfigControllerFailed): Cluster not available for [{operator 4.14.0-0.ci.test-2023-04-27-172910-ci-op-8lsi16gg-latest}]: ControllerConfig.machineconfiguration.openshift.io "machine-config-controller" is invalid: [spec.dns.apiVersion: Required value: must not be empty, spec.dns.kind: Required value: must not be empty, <nil>: Invalid value: "null": some validation rules were not checked because the object was invalid; correct the existing errors to complete validation]}

Also, TestUnmanagedDNSToManagedDNSInternalIngressController failed:

util_test.go:90: retrying client call due to: Get "http://10.0.128.5/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
    unmanaged_dns_test.go:318: failed to verify connectivity with workload with reqURL http://10.0.128.5/ using external client: timed out waiting for the condition
    panic.go:522: deleted ingresscontroller unmanaged-migrated-internal

Also, TestRouterCompressionOperationfailed:

    router_compression_test.go:209: compression error: expected "gzip", got "" for canary route

I filed OCPBUGS-12913 to track TestRouterCompressionOperation failures.
/test e2e-gcp-operator

@Miciah
Copy link
Contributor Author

Miciah commented Apr 28, 2023

e2e-aws-operator failed again because TestRouterCompressionOperation failed.

Need to rerun all tests since #901 merged.
/test all

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD ed5d8f8 and 1 for PR HEAD e5382b2 in total

@Miciah
Copy link
Contributor Author

Miciah commented Apr 28, 2023

e2e-aws-operator failed because the cluster couldn't be provisioned and AWS is full:

level=error msg=Error: creating EC2 Instance: InvalidNetworkInterface.InUse: Interface: [eni-05ab9214d3d23cd26] in use.
level=error msg=	status code: 400, request id: 6a8fd0ce-8fc1-4d0d-9ada-817162b614fa 
level=error msg=Error: creating EC2 Instance: InsufficientInstanceCapacity: We currently do not have sufficient m6a.xlarge capacity in the Availability Zone you requested (us-west-1b). Our system will be working on provisioning additional capacity. You can currently get m6a.xlarge capacity by not specifying an Availability Zone in your request or choosing us-west-1a.
level=error msg=	status code: 500, request id: 0900cc18-53fc-4ab3-baff-bc60a9c9644d 

e2e-azure-operator failed because TestRouterCompressionOperation failed (OCPBUGS-12913).

e2e-gcp-operator failed because TestScopeChange and TestInternalLoadBalancer failed.

None of these changes could be caused by the changes in this PR.

/skip e2e-aws-operator
/skip e2e-azure-operator
/test e2e-gcp-operator

@Miciah
Copy link
Contributor Author

Miciah commented Apr 28, 2023

/override ci/prow/e2e-aws-operator
/override ci/prow/e2e-azure-operator
/override ci/prow/e2e-gcp-operator

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 28, 2023

@Miciah: Overrode contexts on behalf of Miciah: ci/prow/e2e-aws-operator, ci/prow/e2e-azure-operator, ci/prow/e2e-gcp-operator

Details

In response to this:

/override ci/prow/e2e-aws-operator
/override ci/prow/e2e-azure-operator
/override ci/prow/e2e-gcp-operator

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-merge-robot openshift-merge-robot merged commit 43395ef into openshift:master Apr 28, 2023
@openshift-ci-robot
Copy link
Contributor

@Miciah: Jira Issue OCPBUGS-12790: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-12790 has been moved to the MODIFIED state.

Details

In response to this:

  • .github/ISSUE_TEMPLATE/config.yml: Update the Bugzilla link to point instead to the Red Hat Issue Tracker.
  • OWNERS: Remove the component field. Add past approvers to emeritus_approvers and remove them from the approvers and reviewers lists.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 28, 2023

@Miciah: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-ingress-operator-container-v4.14.0-202304282242.p0.g43395ef.assembly.stream for distgit ose-cluster-ingress-operator.
All builds following this will include this PR.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants