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

ODC-7337: Skip wait for authentication operator to start progressing when the secret already exists #12884

Conversation

sanketpathak
Copy link
Contributor

@sanketpathak sanketpathak commented Jun 8, 2023

Issue: https://issues.redhat.com/browse/ODC-7337

Description: For periodic jobs, our tests will append to existing console tests but because the value of waitForAuthOperatorProgressing changes from true to false at the start of console tests and with the same procedure our tests keep on waiting to fetch its value as true which never happens and tests do not start

@openshift-ci openshift-ci bot requested review from jhadvig and spadgett June 8, 2023 12:25
@sanketpathak sanketpathak force-pushed the prow-change-topology-periodic-test branch from 1e4968a to a6da146 Compare June 9, 2023 12:39
@sanketpathak
Copy link
Contributor Author

/retest

@sanketpathak
Copy link
Contributor Author

/test e2e-gcp-console

Copy link
Member

@jerolimov jerolimov left a comment

Choose a reason for hiding this comment

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

Hey Sanket, this looks good to me, but please add a ticket and a description why this is needed. Thanks :)

/cc
/assign

test-prow-e2e.sh Outdated
set -x
# Skip wait for authentication operator to start Progressing when the Secret already exists.
# And ignore any kind of errors when the Secret doesn't exist.
set +e
Copy link
Member

Choose a reason for hiding this comment

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

Maybe just use --ignore-not-found instead of set +e? That would be better so that we still fail on other errors.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks @spadgett, updated the pr

test-prow-e2e.sh Outdated
# Skip wait for authentication operator to start Progressing when the Secret already exists.
# And ignore any kind of errors when the Secret doesn't exist.
set +e
htpasswdSecretName=$(oc get secret -n openshift-config htpass-secret -o name 2> /dev/null)
Copy link
Member

Choose a reason for hiding this comment

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

nitpick: shell scripts typically use snake case for var names like htpasswd_secret_name

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks @spadgett, updated the pr

@jerolimov
Copy link
Member

jerolimov commented Jun 27, 2023

/retitle ODC-7337: Skip wait for authentication operator to start progressing when the secret already exists

@openshift-ci openshift-ci bot changed the title Skip wait for authentication operator to start progressing when the secret already exists ODC-7337: Skip wait for authentication operator to start progressing when the secret already exists Jun 27, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 27, 2023
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 27, 2023

@sanketpathak: This pull request references ODC-7337 which is a valid jira issue.

In response to this:

Issue: https://issues.redhat.com/browse/ODC-7337

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.

@sanketpathak sanketpathak force-pushed the prow-change-topology-periodic-test branch from a6da146 to bc79776 Compare June 27, 2023 11:23
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 27, 2023

@sanketpathak: This pull request references ODC-7337 which is a valid jira issue.

In response to this:

Issue: https://issues.redhat.com/browse/ODC-7337
Description:

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
Copy link
Contributor

openshift-ci-robot commented Jun 27, 2023

@sanketpathak: This pull request references ODC-7337 which is a valid jira issue.

In response to this:

Issue: https://issues.redhat.com/browse/ODC-7337
Description: For periodic jobs, our tests will append to existing console tests but because
the value of waitForAuthOperatorProgressing changes from true to false at the start of console tests and with the same procedure our tests keep on waiting to fetch its value as true which never happens and tests do not start

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
Copy link
Contributor

openshift-ci-robot commented Jun 27, 2023

@sanketpathak: This pull request references ODC-7337 which is a valid jira issue.

In response to this:

Issue: https://issues.redhat.com/browse/ODC-7337

Description: For periodic jobs, our tests will append to existing console tests but because the value of waitForAuthOperatorProgressing changes from true to false at the start of console tests and with the same procedure our tests keep on waiting to fetch its value as true which never happens and tests do not start

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.

Copy link
Member

@spadgett spadgett 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 openshift-ci bot 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 Jun 27, 2023
Copy link
Member

@jerolimov jerolimov left a comment

Choose a reason for hiding this comment

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

👍

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 28, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerolimov, sanketpathak, spadgett

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

@jerolimov
Copy link
Member

jerolimov commented Jun 28, 2023

Chore change that makes the test-prow-e2e.sh script executable multiple times. Shouldn't affect the product or e2e tests if the e2e tests run just once.

/label docs-approved
/label px-approved
/label qe-approved
/retest

@openshift-ci openshift-ci bot added docs-approved Signifies that Docs has signed off on this PR px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR labels Jun 28, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 28, 2023

@sanketpathak: 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 407d961 into openshift:master Jun 28, 2023
6 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. docs-approved Signifies that Docs has signed off on this PR 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. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants