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-29637: azurepathfix: fix stack hub, government and workload identity setup #1003

Merged
merged 7 commits into from Feb 21, 2024

Conversation

flavianmissi
Copy link
Member

@flavianmissi flavianmissi commented Feb 19, 2024

No description provided.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 19, 2024
this fixes azure government cloud, where the suffix is different.
@flavianmissi flavianmissi changed the title cmd/move-blobs: use endpoint suffix from environment OCPBUGS-29638: cmd/move-blobs: use endpoint suffix from environment Feb 19, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical 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 Feb 19, 2024
@openshift-ci-robot
Copy link
Contributor

@flavianmissi: This pull request references Jira Issue OCPBUGS-29638, which is invalid:

  • expected the bug to target either version "4.16." or "openshift-4.16.", but it targets "4.15.0" 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:

this fixes azure government cloud, where the suffix is different.

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 openshift-eng/jira-lifecycle-plugin repository.

@flavianmissi
Copy link
Member Author

/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 Feb 19, 2024
@openshift-ci-robot
Copy link
Contributor

@flavianmissi: This pull request references Jira Issue OCPBUGS-29638, 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.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @xiuwang

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 openshift-eng/jira-lifecycle-plugin 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 Feb 19, 2024
@openshift-ci openshift-ci bot requested a review from xiuwang February 19, 2024 08:36
@flavianmissi
Copy link
Member Author

this is critical to both 4.15 and another backport to 4.14.
/label acknowledge-critical-fixes-only
/cherry-pick release-4.15

@openshift-cherrypick-robot

@flavianmissi: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you.

In response to this:

this is critical to both 4.15 and another backport to 4.14.
/label acknowledge-critical-fixes-only
/cherry-pick release-4.15

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 added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Feb 19, 2024
@flavianmissi flavianmissi changed the title OCPBUGS-29638: cmd/move-blobs: use endpoint suffix from environment OCPBUGS-29637: cmd/move-blobs: use endpoint suffix from environment Feb 19, 2024
@openshift-ci-robot
Copy link
Contributor

@flavianmissi: This pull request references Jira Issue OCPBUGS-29637, 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.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @xiuwang

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

In response to this:

this fixes azure government cloud, where the suffix differs.

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 openshift-eng/jira-lifecycle-plugin repository.

this should fix the job for clusters with workload identity
@wewang58
Copy link

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@wewang58: This pull request references Jira Issue OCPBUGS-29637, which is valid.

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

Requesting review from QA contact:
/cc @wewang58

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 openshift-eng/jira-lifecycle-plugin repository.

@flavianmissi flavianmissi changed the title OCPBUGS-29637: cmd/move-blobs: use endpoint suffix from environment OCPBUGS-29637: azurepathfix: fix stack hub, government and workload identity setup Feb 19, 2024
@openshift-ci-robot
Copy link
Contributor

@flavianmissi: An error was encountered querying GitHub for users with public email (wewang@redhat.com) for bug OCPBUGS-29637 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. Post "http://ghproxy/graphql": dial tcp 172.30.229.2:80: connect: connection refused

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 20, 2024
the storage controller sometimes recreates the storage account after the
job has been created. to account for that, we compare the container envs
between created and desired values, and when they differ we recreate the
job.
@flavianmissi
Copy link
Member Author

/test verify

@flavianmissi
Copy link
Member Author

/payload-aggregate periodic-ci-openshift-release-master-ci-4.16-e2e-azure-ovn 4

Copy link
Contributor

openshift-ci bot commented Feb 20, 2024

@flavianmissi: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.16-e2e-azure-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/16427340-cfe8-11ee-83dc-c951619146e3-0

@flavianmissi
Copy link
Member Author

/test e2e-azure-operator

@flavianmissi
Copy link
Member Author

The payload job failed not because the tests didn't pass, but because I chose to run it 4 times (instead of the required 6 to succeed). I inspected every test with image-registry in its name individually, and each of them had passed 4 times as expected.

@flavianmissi
Copy link
Member Author

I'm running the same tests locally, let's see who's fastest.
/test e2e-azure-operator

@flavianmissi
Copy link
Member Author

flavianmissi commented Feb 20, 2024

Test run on a 4.15.0-0.ci.test-2024-02-20-161756-ci-ln-pl80pmb-latest cluster (built by ClusterBot with the code in this PR). Note that I removed some output to make the tests result more clear:

go test -v -run PVC ./test/e2e
=== RUN   TestDefaultPVC
    [...]
--- PASS: TestDefaultPVC (133.62s)
=== RUN   TestCustomRWXPVC
    [...]
--- PASS: TestCustomRWXPVC (124.35s)
=== RUN   TestCustomRWOPVC
    [...]
--- PASS: TestCustomRWOPVC (123.45s)
PASS
ok  	github.com/openshift/cluster-image-registry-operator/test/e2e	391.967s

I'm trying to get a 4.16 build of this PR but so far have not been able to. Will report back.

if err != nil {
return nil, false, err
}
expectedJob := exp.(*batchv1.Job)
Copy link
Member

Choose a reason for hiding this comment

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

nit: is it better to check the conversion with expectedJob, ok to ignore the ones that is !ok

GracePeriodSeconds: &gracePeriod,
PropagationPolicy: &propagationPolicy,
}
if err := gapfj.Delete(opts); err != nil {
Copy link
Member

Choose a reason for hiding this comment

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

Nit: Is it possible that err can be NotFound which is valid for deletes to continue gapfj.Create

@ardaguclu
Copy link
Member

It is already on hold;
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2024
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2024
@ardaguclu
Copy link
Member

/lgtm
/retest

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 21, 2024
Copy link
Contributor

openshift-ci bot commented Feb 21, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ardaguclu, dmage, flavianmissi

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

@flavianmissi
Copy link
Member Author

the job changed in this PR does not run on AWS, and hypershift is AWS only - the failures are unrelated.
/override ci/prow/e2e-hypershift

@flavianmissi
Copy link
Member Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 21, 2024
Copy link
Contributor

openshift-ci bot commented Feb 21, 2024

@flavianmissi: Overrode contexts on behalf of flavianmissi: ci/prow/e2e-hypershift

In response to this:

the job changed in this PR does not run on AWS, and hypershift is AWS only - the failures are unrelated.
/override ci/prow/e2e-hypershift

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
Contributor

openshift-ci bot commented Feb 21, 2024

@flavianmissi: 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-bot openshift-merge-bot bot merged commit 41ea2a9 into openshift:master Feb 21, 2024
12 checks passed
@openshift-ci-robot
Copy link
Contributor

@flavianmissi: Jira Issue OCPBUGS-29637: All pull requests linked via external trackers have merged:

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

In response to 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-cherrypick-robot

@flavianmissi: new pull request created: #1004

In response to this:

this is critical to both 4.15 and another backport to 4.14.
/label acknowledge-critical-fixes-only
/cherry-pick release-4.15

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

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-image-registry-operator-container-v4.16.0-202402210939.p0.g41ea2a9.assembly.stream.el9 for distgit ose-cluster-image-registry-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
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-critical Referenced Jira bug's severity is critical 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. 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

7 participants