Skip to content

Conversation

@perdasilva
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 24, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 24, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva

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 Sep 24, 2025
@perdasilva perdasilva marked this pull request as ready for review September 24, 2025 14:09
@perdasilva
Copy link
Contributor Author

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview 5

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 24, 2025

@perdasilva: 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.20-e2e-gcp-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fc1e6420-9957-11f0-85bf-af374a10d3ea-0

@perdasilva
Copy link
Contributor Author

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-metal-ipi-ovn-ipv6-techpreview 5

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 25, 2025

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

@perdasilva
Copy link
Contributor Author

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview 5

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 25, 2025

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

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fda12af0-9a04-11f0-8abc-e1b342e60427-0

@perdasilva perdasilva force-pushed the ote-dc-test branch 2 times, most recently from ffd9ab7 to 42a85d1 Compare September 29, 2025 13:24
@perdasilva
Copy link
Contributor Author

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview 1

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2025

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

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/4f782950-9d43-11f0-9ce3-c7dc4b9b6993-0

@perdasilva perdasilva force-pushed the ote-dc-test branch 2 times, most recently from 3110080 to d177028 Compare September 29, 2025 16:10
@perdasilva
Copy link
Contributor Author

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview 1

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2025

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

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d4e1e7b0-9d4e-11f0-9c06-673c7c8b1fa8-0

@perdasilva
Copy link
Contributor Author

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview 1

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2025

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

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e6789ad0-9d55-11f0-9f30-747af7593e18-0

@perdasilva
Copy link
Contributor Author

/test ci/prow/openshift-e2e-aws-techpreview

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2025

@perdasilva: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test check-sync-pr-valid
/test default-catalog-consistency
/test e2e-aws-techpreview-olmv1-ext
/test images
/test okd-scos-images
/test openshift-e2e-aws
/test tests-extension
/test unit
/test verify
/test verify-commits
/test verify-deps

The following commands are available to trigger optional jobs:

/test okd-scos-e2e-aws-ovn
/test openshift-e2e-aws-techpreview

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-operator-framework-operator-controller-main-check-sync-pr-valid
pull-ci-openshift-operator-framework-operator-controller-main-e2e-aws-techpreview-olmv1-ext
pull-ci-openshift-operator-framework-operator-controller-main-images
pull-ci-openshift-operator-framework-operator-controller-main-okd-scos-e2e-aws-ovn
pull-ci-openshift-operator-framework-operator-controller-main-okd-scos-images
pull-ci-openshift-operator-framework-operator-controller-main-openshift-e2e-aws
pull-ci-openshift-operator-framework-operator-controller-main-openshift-e2e-aws-techpreview
pull-ci-openshift-operator-framework-operator-controller-main-tests-extension
pull-ci-openshift-operator-framework-operator-controller-main-unit
pull-ci-openshift-operator-framework-operator-controller-main-verify
pull-ci-openshift-operator-framework-operator-controller-main-verify-commits
pull-ci-openshift-operator-framework-operator-controller-main-verify-deps

In response to this:

/test ci/prow/openshift-e2e-aws-techpreview

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-sigs/prow repository.

@perdasilva
Copy link
Contributor Author

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview 5

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 30, 2025

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

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8063deb0-9e01-11f0-9265-98260a5fdaeb-0

@perdasilva perdasilva changed the title [WIP] OTE building controller image OPRUN-4169: OTE building controller image Oct 2, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 2, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 2, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 2, 2025

@perdasilva: This pull request references OPRUN-4169 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

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.

@perdasilva
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 2, 2025

@perdasilva: This pull request references OPRUN-4169 which is a valid jira issue.

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.

@perdasilva
Copy link
Contributor Author

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview 10

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 2, 2025

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

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8573b970-9f96-11f0-83a7-78fb89bc68af-0

Comment on lines 99 to 103
@# Check if KUBECONFIG is set and not empty
@if [ -z "$(KUBECONFIG)" ]; then \
echo "Please set KUBECONFIG first"; \
exit 1; \
fi
Copy link
Contributor

Choose a reason for hiding this comment

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

KUBECONFIG is not the only method to reach a cluster, there's also oc config get-context and other config commands.

Copy link
Contributor Author

@perdasilva perdasilva Oct 6, 2025

Choose a reason for hiding this comment

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

KUBECONFIG being set seems to be a requirement for updating metadata. It seems to be failing without error code - that's why I put this check here to make sure we fail loudly. I'll update the message to make that clearer. Thanks for calling this out!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

So, for more info, here's the output without this guard:

 make update-metadata                                                                                                                                                                                                                                                                                       perdasilva@nibbler
/home/perdasilva/repos/perdasilva/operator-framework-operator-controller/openshift/tests-extension/bin/olmv1-tests-ext update --component openshift:payload:olmv1
Please set KUBECONFIG first!
make clean-metadata
make[1]: Entering directory '/home/perdasilva/repos/perdasilva/operator-framework-operator-controller/openshift/tests-extension'
Cleaning metadata (removing codeLocations)...
make[1]: Leaving directory '/home/perdasilva/repos/perdasilva/operator-framework-operator-controller/openshift/tests-extension'

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I did a bit more digging and found out the source of the issue. I've reverted this change and reached out to Kui to see what we could do about fixing it.

gopkg.in/evanphx/json-patch.v4 v4.12.0 // indirect
gopkg.in/inf.v0 v0.9.1 // indirect
gopkg.in/yaml.v2 v2.4.0 // indirect
k8s.io/cloud-provider v0.0.0 // indirect
Copy link
Contributor

Choose a reason for hiding this comment

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

Why were a bunch of these v0.0.0?? Weird

Copy link
Contributor Author

Choose a reason for hiding this comment

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

strange indeed - could it be related to dependencies pointing to shas instead of releases?

@tmshort
Copy link
Contributor

tmshort commented Oct 3, 2025

Just a few nits, but fine otherwise.
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 3, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 6, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 6, 2025

@perdasilva: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/openshift-e2e-aws-techpreview 880a090 link false /test openshift-e2e-aws-techpreview
ci/prow/okd-scos-e2e-aws-ovn 880a090 link false /test okd-scos-e2e-aws-ovn

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-sigs/prow repository. I understand the commands that are listed here.

@tmshort
Copy link
Contributor

tmshort commented Oct 6, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 6, 2025
@tmshort
Copy link
Contributor

tmshort commented Oct 6, 2025

techpreview failure was [sig-instrumentation]

@bandrade
Copy link

bandrade commented Oct 6, 2025

/label qe-approved
/verified by @bandrade

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Oct 6, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 6, 2025

@perdasilva: This pull request references OPRUN-4169 which is a valid jira issue.

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-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 6, 2025
@openshift-ci-robot
Copy link

@bandrade: This PR has been marked as verified by @bandrade.

In response to this:

/label qe-approved
/verified by @bandrade

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-merge-bot openshift-merge-bot bot merged commit d6b8f7f into openshift:main Oct 6, 2025
11 of 13 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. 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 verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants