Skip to content

Conversation

@rna-afk
Copy link
Contributor

@rna-afk rna-afk commented Feb 20, 2025

Fixing the error messages in the check for available IPs. The error message is always empty since there was no error but there are no IPs available.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 20, 2025
@openshift-ci-robot
Copy link
Contributor

@rna-afk: This pull request references Jira Issue OCPBUGS-50534, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA 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.

Details

In response to this:

Fixing the error messages in the check for available IPs. The error message is always empty since there was no error but there are no IPs available.

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 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Feb 20, 2025
@openshift-ci openshift-ci bot requested review from jhixson74 and mtulio February 20, 2025 13:55
Copy link
Member

Choose a reason for hiding this comment

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

nit: should we include a reason, for example, no available IP (i.e. same for line 286 above)?

I feel like failed to ... alone could mean some unknown internal error, which might not be descriptive enough :D

Copy link
Contributor

Choose a reason for hiding this comment

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

+1 for line 299.
Currently, installer seems always running into line 286 when lack of permissions, maybe add reason what Patrick suggested for line 271?

@rna-afk rna-afk force-pushed the fix_available_ip_error_msg branch from babd7d5 to 759b731 Compare February 24, 2025 08:13
@patrickdillon
Copy link
Contributor

The shared vpc job is permafailing until we have openshift/release#61374, so the silver lining is we can see these changes in the ci test results!

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 24, 2025
@rna-afk
Copy link
Contributor Author

rna-afk commented Feb 24, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 24, 2025
@openshift-ci-robot
Copy link
Contributor

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

Requesting review from QA contact:
/cc @jinyunma

Details

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 openshift-ci bot requested a review from jinyunma February 24, 2025 18:03
Copy link
Member

Choose a reason for hiding this comment

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

question: I think here *ipAvail.AvailableIPAddresses is non-empty and we could not find any suitable IP right? How about no available IP or similar?

Copy link
Contributor Author

@rna-afk rna-afk Feb 26, 2025

Choose a reason for hiding this comment

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

There is IP available but at this stage there's no Ip that we can use that's in the machine network so I think it's fine but I am really bad at error messages or commenting so.

Copy link
Member

Choose a reason for hiding this comment

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

Right, what do you think of using what you just wrote as error message instead (i.e. that is There is IP available but at this stage there's no Ip that we can use that's in the machine network)? Otherwise, LGTM.

Copy link
Member

Choose a reason for hiding this comment

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

I realized the wordings in my original question was kinda odd. Your latest commit looks great! 👏🏼

Fixing the error messages in the check for available IPs.
The error message is always empty since there was no error
but there are no IPs available.
@rna-afk rna-afk force-pushed the fix_available_ip_error_msg branch from 759b731 to be7f5b5 Compare February 26, 2025 10:02
@tthvo
Copy link
Member

tthvo commented Feb 26, 2025

/lgtm ^-^

@tthvo
Copy link
Member

tthvo commented Feb 26, 2025

/lgtm
/retest-required

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

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

@openshift-ci-robot
Copy link
Contributor

@openshift-bot: This pull request references Jira Issue OCPBUGS-50534, which is valid.

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

Requesting review from QA contact:
/cc @jinyunma

Details

In response to this:

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

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

/retest-required

Remaining retests: 0 against base HEAD 3612909 and 2 for PR HEAD be7f5b5 in total

2 similar comments
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 3612909 and 2 for PR HEAD be7f5b5 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 3612909 and 2 for PR HEAD be7f5b5 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 6bc5c21 and 1 for PR HEAD be7f5b5 in total

@tthvo
Copy link
Member

tthvo commented Feb 27, 2025

/override ci/prow/okd-scos-images
/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 27, 2025

@tthvo: tthvo unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers.

Details

In response to this:

/override ci/prow/okd-scos-images
/retest-required

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.

@tthvo
Copy link
Member

tthvo commented Feb 28, 2025

@tthvo: tthvo unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers.

Ah no, I don't have the power 😅

/retest-required

@tthvo
Copy link
Member

tthvo commented Feb 28, 2025

/retest-required

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD e9b3cf7 and 0 for PR HEAD be7f5b5 in total

@openshift-ci-robot
Copy link
Contributor

/hold

Revision be7f5b5 was retested 3 times: holding

@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 Mar 1, 2025
@jinyunma
Copy link
Contributor

jinyunma commented Mar 3, 2025

/unhold
/retest-required

@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 Mar 3, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2025

@rna-afk: 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/e2e-azurestack be7f5b5 link false /test e2e-azurestack
ci/prow/okd-scos-e2e-aws-ovn be7f5b5 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-vsphere-ovn-multi-network be7f5b5 link false /test e2e-vsphere-ovn-multi-network
ci/prow/e2e-vsphere-static-ovn be7f5b5 link false /test e2e-vsphere-static-ovn
ci/prow/azure-ovn-marketplace-images be7f5b5 link false /test azure-ovn-marketplace-images

Full PR test history. Your PR dashboard.

Details

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.

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD e9b3cf7 and 2 for PR HEAD be7f5b5 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD de563b9 and 2 for PR HEAD be7f5b5 in total

@openshift-merge-bot openshift-merge-bot bot merged commit b20e29d into openshift:main Mar 3, 2025
19 of 24 checks passed
@openshift-ci-robot
Copy link
Contributor

@rna-afk: Jira Issue OCPBUGS-50534: All pull requests linked via external trackers have merged:

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

Details

In response to this:

Fixing the error messages in the check for available IPs. The error message is always empty since there was no error but there are no IPs available.

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

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-altinfra
This PR has been included in build ose-installer-altinfra-container-v4.19.0-202503040041.p0.gb20e29d.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-terraform-providers
This PR has been included in build ose-installer-terraform-providers-container-v4.19.0-202503040041.p0.gb20e29d.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-baremetal-installer
This PR has been included in build ose-baremetal-installer-container-v4.19.0-202503040041.p0.gb20e29d.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-artifacts
This PR has been included in build ose-installer-artifacts-container-v4.19.0-202503040309.p0.gb20e29d.assembly.stream.el9.
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

approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants