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.

Sign up for GitHub

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

Jump to bottom

Re-disable the cluster-ingress-operator #496

Merged
merged 1 commit into from
Oct 19, 2018
Merged

Re-disable the cluster-ingress-operator #496

merged 1 commit into from
Oct 19, 2018

Conversation

ironcladlou
Copy link
Contributor

Fix the cluster-ingress-operator override to match the
cluster-ingress-operator's new namespace and deployment name[1].

[1] openshift/cluster-ingress-operator#52

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Oct 19, 2018
@ironcladlou
Re-disable the cluster-ingress-operator
006929a 
Fix the cluster-ingress-operator override to match the
cluster-ingress-operator's new namespace and deployment name[1].

[1] openshift/cluster-ingress-operator#52
@openshift-ci-robot openshift-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 19, 2018
@ironcladlou
Copy link
Contributor Author

Noticed that the new operator is being deployed by default now in my new 4.0 cluster. I think this is causing e2e hangs that look like:

Waiting for API at https://ci-op-k0ynxymq-2945d-api.origin-ci-int-aws.dev.rhcloud.com:6443  to respond ...
Waiting for API at https://ci-op-k0ynxymq-2945d-api.origin-ci-int-aws.dev.rhcloud.com:6443  to respond ...
Waiting for API at https://ci-op-k0ynxymq-2945d-api.origin-ci-int-aws.dev.rhcloud.com:6443  to respond ...
Waiting for API at https://ci-op-k0ynxymq-2945d-api.origin-ci-int-aws.dev.rhcloud.com:6443  to respond ...
Waiting for API at https://ci-op-k0ynxymq-2945d-api.origin-ci-int-aws.dev.rhcloud.com:6443  to respond ...
Waiting for API at https://ci-op-k0ynxymq-2945d-api.origin-ci-int-aws.dev.rhcloud.com:6443  to respond ...
NAME                           STATUS    ROLES       AGE       VERSION
ip-10-0-14-67.ec2.internal     Ready     master      10m       v1.11.0+d4cacc0
ip-10-0-16-216.ec2.internal    Ready     master      10m       v1.11.0+d4cacc0
ip-10-0-193-97.ec2.internal    Ready     worker      4m        v1.11.0+d4cacc0
ip-10-0-198-221.ec2.internal   Ready     worker      4m        v1.11.0+d4cacc0
ip-10-0-203-50.ec2.internal    Ready     worker      4m        v1.11.0+d4cacc0
ip-10-0-47-28.ec2.internal     Ready     master      10m       v1.11.0+d4cacc0
ip-10-0-5-100.ec2.internal     Ready     bootstrap   10m       v1.11.0+d4cacc0
API at https://ci-op-k0ynxymq-2945d-api.origin-ci-int-aws.dev.rhcloud.com:6443  has responded
NAME             DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR                     AGE
router-default   3         3         3         3            3           node-role.kubernetes.io/worker=   2m
Found router in openshift-ingress
error: timed out waiting for the condition
error deploy/router did not come up
error: timed out waiting for the condition
error deploy/router did not come up
error: timed out waiting for the condition
error deploy/router did not come up
error: timed out waiting for the condition
error deploy/router did not come up
error: timed out waiting for the condition
error deploy/router did not come up
error: timed out waiting for the condition
error deploy/router did not come up
error: timed out waiting for the condition
error deploy/router did not come up
error: timed out waiting for the condition
error deploy/router did not come up

@ironcladlou ironcladlou mentioned this pull request Oct 19, 2018
Merged
abhinavdahiya
abhinavdahiya approved these changes Oct 19, 2018
View reviewed changes
Copy link
Contributor

@abhinavdahiya abhinavdahiya left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 19, 2018
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, ironcladlou

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 19, 2018
@openshift-merge-robot openshift-merge-robot merged commit e49c6a5 into openshift:master Oct 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@abhinavdahiya abhinavdahiya abhinavdahiya approved these changes

@crawford crawford Awaiting requested review from crawford

@staebler staebler Awaiting requested review from staebler

Assignees

@abhinavdahiya abhinavdahiya

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. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ironcladlou @openshift-ci-robot @abhinavdahiya @openshift-merge-robot