Skip to content

Conversation

@Miciah
Copy link
Contributor

@Miciah Miciah commented Mar 27, 2020

Configure the console to use the default-ingress-cert configmap if the configmap exists, or else to use the default CA if the configmap is absent. Before this commit, the operator did exactly the reverse.

Fix a comment that falsely stated that the configmap would be absent if the administrator provided a default certificate for every ingress controller.

Follow-up to #361.

  • pkg/console/operator/sync_v400.go: Invert the value of useDefaultCAFile. Fix a comment.

@jhadvig

Configure the console to use the default-ingress-cert configmap if the
configmap exists, or else to use the default CA if the configmap is absent.
Before this commit, the operator did exactly the reverse.

Fix a comment that falsely stated that the configmap would be absent if the
administrator provided a default certificate for every ingress controller.

Follow-up to commit 489dfd0.

* pkg/console/operator/sync_v400.go: Invert the value of useDefaultCAFile.
Fix a comment.
@spadgett
Copy link
Member

Thanks @Miciah. Seeing a test error that looks related.

 --- FAIL: TestEditManagedRoute (243.82s)
    managed_test.go:13: waiting for setup to reach settled state...
    util.go:72: patching TargetPort on the console Route
    util.go:79: polling for patched TargetPort on the console Route
    managed_test.go:17: waiting for cleanup to reach settled state...
    console-operator.go:369: waited 10 seconds to reach settled state...
    console-operator.go:369: waited 30 seconds to reach settled state...
    console-operator.go:369: waited 60 seconds to reach settled state...
    console-operator.go:369: waited 90 seconds to reach settled state...
    console-operator.go:369: waited 120 seconds to reach settled state...
    managed_test.go:17: operator has not reached settled state in 4m0s attempts due to [RouteHealthDegraded] - timed out waiting for the condition 

Copy link
Contributor

@benjaminapetersen benjaminapetersen left a comment

Choose a reason for hiding this comment

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

/approve
/lgtm

But looking into the e2e failures. something funny.

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benjaminapetersen, Miciah

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-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 2, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@Miciah
Copy link
Contributor Author

Miciah commented Apr 2, 2020

I have been performing some manual testing:

% go test -count 1 -v -tags e2e -run TestEditManagedRoute ./test/e2e

Sometimes the test succeeds in about 30 to 90 seconds, sometimes it hangs for several minutes and eventually fails. When it hangs, I can see the failing status condition:

% oc get consoles.operator/cluster -o yaml
...
  - lastTransitionTime: "2020-04-02T02:33:16Z"
    message: route not yet available, https://console-openshift-console.apps.ci-ln-h70r2jt-d5d6b.origin-ci-int-aws.dev.rhcloud.com/health
      returns '503 Service Unavailable'
    reason: StatusError
    status: "True"
    type: RouteHealthDegraded
...

But curling the route works:

% curl -ksv https://console-openshift-console.apps.ci-ln-h70r2jt-d5d6b.origin-ci-int-aws.dev.rhcloud.com/health
* About to connect() to console-openshift-console.apps.ci-ln-h70r2jt-d5d6b.origin-ci-int-aws.dev.rhcloud.com port 443 (#0)
*   Trying 44.228.49.144...
* Connected to console-openshift-console.apps.ci-ln-h70r2jt-d5d6b.origin-ci-int-aws.dev.rhcloud.com (44.228.49.144) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* skipping SSL peer certificate verification
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
*       subject: CN=*.apps.ci-ln-h70r2jt-d5d6b.origin-ci-int-aws.dev.rhcloud.com
*       start date: Apr 02 00:19:22 2020 GMT
*       expire date: Apr 02 00:19:23 2022 GMT
*       common name: *.apps.ci-ln-h70r2jt-d5d6b.origin-ci-int-aws.dev.rhcloud.com
*       issuer: CN=ingress-operator@1585786761
> GET /health HTTP/1.1
> User-Agent: curl/7.29.0
> Host: console-openshift-console.apps.ci-ln-h70r2jt-d5d6b.origin-ci-int-aws.dev.rhcloud.com
> Accept: */*
>
< HTTP/1.1 200 OK
< content-type: application/json
< referrer-policy: strict-origin-when-cross-origin
< x-content-type-options: nosniff
< x-dns-prefetch-control: off
< x-frame-options: DENY
< x-xss-protection: 1; mode=block
< date: Thu, 02 Apr 2020 02:35:48 GMT
< content-length: 15
< set-cookie: 1e2670d92730b515ce3a1bb65da45062=5bc7860bccc251cfb87ae1d8366659b6; path=/; HttpOnly; Secure
< cache-control: private
<
* Connection #0 to host console-openshift-console.apps.ci-ln-h70r2jt-d5d6b.origin-ci-int-aws.dev.rhcloud.com left intact
{"status":"ok"}

Could the status update code be failing to update?

@benjaminapetersen
Copy link
Contributor

I've been running the tests locally as well, they appear to be working for me. Very curious.

@benjaminapetersen
Copy link
Contributor

It may be that we just need to increase the timeout a bit. I've ran these a number of times and only hit a fail once.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@Miciah
Copy link
Contributor Author

Miciah commented Apr 2, 2020

I only did a small number of tests on my test cluster. I saw two successes and two failures.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit e26c857 into openshift:master Apr 2, 2020
@benjaminapetersen
Copy link
Contributor

We will keep an eye on this, perhaps our timeout needs to increase... but will look to see if there is anything else wrong.

@benjaminapetersen
Copy link
Contributor

/cherry-pick release-4.4

I think we need to backport this.

@openshift-cherrypick-robot

@benjaminapetersen: new pull request created: #407

Details

In response to this:

/cherry-pick release-4.4

I think we need to backport this.

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.

@benjaminapetersen benjaminapetersen changed the title Fix console oauthEndpointCAFile setting Bug 1824934: Fix console oauthEndpointCAFile setting Apr 16, 2020
@openshift-ci-robot
Copy link
Contributor

@Miciah: All pull requests linked via external trackers have merged: . Bugzilla bug 1824934 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1824934: Fix console oauthEndpointCAFile setting

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.

@benjaminapetersen
Copy link
Contributor

/bugzilla assign-qa

@openshift-ci-robot
Copy link
Contributor

@benjaminapetersen: All pull requests linked via external trackers have merged: . Bugzilla bug 1824934 has been moved to the MODIFIED state.

Details

In response to this:

/bugzilla assign-qa

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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants