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

OCPBUGS-12790: README: Fix Bugzilla link #968

Conversation

Miciah
Copy link
Contributor

@Miciah Miciah commented Jul 25, 2023

Follow-up to #916.

  • README.md: Update the Bugzilla link to point instead to the Red Hat Issue Tracker.

@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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 25, 2023
@openshift-ci-robot
Copy link
Contributor

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

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

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.

In response to this:

Follow-up to #916.

  • README.md: Update the Bugzilla link to point instead to the Red Hat Issue Tracker.

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 openshift-ci bot requested review from alebedev87 and gcs278 July 25, 2023 03:26
@Miciah
Copy link
Contributor Author

Miciah commented Jul 25, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jul 25, 2023
@openshift-ci-robot
Copy link
Contributor

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

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @melvinjoseph86

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 Jul 25, 2023
Related to bug OCPBUGS-12790.

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

Follow-up to commit e5382b2.

* README.md: Update the Bugzilla link to point instead to the Red Hat Issue
Tracker.
@Miciah Miciah force-pushed the OCPBUGS-12790-README-fix-Bugzilla-link branch from 633d4ef to 69cd0a2 Compare July 25, 2023 03:28
@melvinjoseph86
Copy link

/test e2e-gcp-operator

@frobware
Copy link
Contributor

/lgtm
/approve

/retest

@Miciah
Copy link
Contributor Author

Miciah commented Jul 28, 2023

e2e-gcp-operator failed because multiple clusteroperators reported degraded:

{Operator degraded (DNSDegraded): DNS default is degraded  Operator degraded (DNSDegraded): DNS default is degraded}
{Operator progressing (Reconciling): ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...
).  Operator progressing (Reconciling): ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...
).}
{Operator unavailable (UpdatingPrometheusOperatorFailed): reconciling Prometheus Operator Admission Webhook Deployment failed: updating Deployment object failed: waiting for DeploymentRollout of openshift-monitoring/prometheus-operator-admission-webhook: context deadline exceeded  Operator unavailable (UpdatingPrometheusOperatorFailed): reconciling Prometheus Operator Admission Webhook Deployment failed: updating Deployment object failed: waiting for DeploymentRollout of openshift-monitoring/prometheus-operator-admission-webhook: context deadline exceeded}
{Operator progressing (Deploying): DaemonSet "/openshift-network-diagnostics/network-check-target" is not available (awaiting 1 nodes)
Deployment "/openshift-network-diagnostics/network-check-source" is waiting for other operators to become ready  Operator progressing (Deploying): DaemonSet "/openshift-network-diagnostics/network-check-target" is not available (awaiting 1 nodes)
Deployment "/openshift-network-diagnostics/network-check-source" is waiting for other operators to become ready}

DNS reported degraded because one of its pods was not ready; this pod reported repeated failures to connect to the API:

[WARNING] plugin/kubernetes: Kubernetes API connection failure: Get "https://172.30.0.1:443/version": dial tcp 172.30.0.1:443: connect: no route to host

Ingress likewise reported degraded because one of the router pods was not ready, again reporting repeated failures to connect to the API:

W0725 09:03:09.048635       1 reflector.go:533] github.com/openshift/router/pkg/router/controller/factory/factory.go:124: failed to list *v1.Route: Get "https://172.30.0.1:443/apis/route.openshift.io/v1/routes?limit=500&resourceVersion=0": dial tcp 172.30.0.1:443: connect: no route to host
E0725 09:03:09.048790       1 reflector.go:148] github.com/openshift/router/pkg/router/controller/factory/factory.go:124: Failed to watch *v1.Route: failed to list *v1.Route: Get "https://172.30.0.1:443/apis/route.openshift.io/v1/routes?limit=500&resourceVersion=0": dial tcp 172.30.0.1:443: connect: no route to host
W0725 09:03:15.384635       1 reflector.go:533] github.com/openshift/router/pkg/router/controller/factory/factory.go:124: failed to list *v1.EndpointSlice: Get "https://172.30.0.1:443/apis/discovery.k8s.io/v1/endpointslices?limit=500&resourceVersion=0": dial tcp 172.30.0.1:443: connect: no route to host
E0725 09:03:15.384777       1 reflector.go:148] github.com/openshift/router/pkg/router/controller/factory/factory.go:124: Failed to watch *v1.EndpointSlice: failed to list *v1.EndpointSlice: Get "https://172.30.0.1:443/apis/discovery.k8s.io/v1/endpointslices?limit=500&resourceVersion=0": dial tcp 172.30.0.1:443: connect: no route to host
I0725 09:03:43.463182       1 shared_informer.go:337] stop requested
E0725 09:03:43.463369       1 factory.go:130] failed to sync cache for *v1.Route shared informer
I0725 09:03:43.463405       1 shared_informer.go:337] stop requested
E0725 09:03:43.463415       1 factory.go:130] failed to sync cache for *v1.EndpointSlice shared informer
I0725 09:03:43.464612       1 template.go:704] router "msg"="Shutdown requested, waiting 45s for new connections to cease" 
E0725 09:03:43.466534       1 haproxy.go:418] can't scrape HAProxy: dial unix /var/lib/haproxy/run/haproxy.sock: connect: no such file or directory
I0725 09:03:43.507094       1 router.go:635] template "msg"="router reloaded" "output"=" - Checking http://localhost:80 ...\n - Health check ok : 0 retry attempt(s).\n"
W0725 09:03:47.064604       1 reflector.go:533] github.com/openshift/router/pkg/router/template/service_lookup.go:33: failed to list *v1.Service: Get "https://172.30.0.1:443/api/v1/services?limit=500&resourceVersion=0": dial tcp 172.30.0.1:443: connect: no route to host
E0725 09:03:47.064674       1 reflector.go:148] github.com/openshift/router/pkg/router/template/service_lookup.go:33: Failed to watch *v1.Service: failed to list *v1.Service: Get "https://172.30.0.1:443/api/v1/services?limit=500&resourceVersion=0": dial tcp 172.30.0.1:443: connect: no route to host
I0725 09:04:28.467074       1 template.go:706] router "msg"="Instructing the template router to terminate" 
I0725 09:04:28.480478       1 router.go:635] template "msg"="router reloaded" "output"=" - Shutting down\n"
I0725 09:04:28.480515       1 template.go:710] router "msg"="Shutdown complete, exiting" 

Overall, the job failure looks like it was caused by issues with the API.
/test e2e-gcp-operator

@candita
Copy link
Contributor

candita commented Aug 2, 2023

/lgtm
/approve

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

openshift-ci bot commented Aug 2, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: candita, frobware

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

/retest-required

Remaining retests: 0 against base HEAD ddba423 and 2 for PR HEAD 69cd0a2 in total

@melvinjoseph86
Copy link

/retest-required

@candita
Copy link
Contributor

candita commented Aug 3, 2023

/test e2e-aws-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 4, 2023

@Miciah: all tests passed!

Full PR test history. Your PR dashboard.

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-merge-robot openshift-merge-robot merged commit 4e7b2da into openshift:master Aug 4, 2023
14 checks passed
@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.

In response to this:

Follow-up to #916.

  • README.md: Update the Bugzilla link to point instead to the Red Hat Issue Tracker.

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.

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. 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.

None yet

6 participants