OCPBUGS-48481: annotation validation policy

[miyadav]

if the annotation cloud.google.com/network-tier was used in service resource and it is left without value or incorrect value(say xyz) , the service goes to Pending status with only warning
Warning SyncLoadBalancerFailed 1s (x3 over 17s) service-controller Error syncing load balancer: failed to ensure load balancer: unsupported network tier: "xyz"
, to avoid that , added the VAP .

[miyadav]

Validated for gcp , looks good , yet to check on azure cluster .

[openshift-ci-robot]

@miyadav: This pull request references Jira Issue OCPBUGS-48481, which is invalid:

• expected the bug to target the "4.19.0" version, but no target version was set

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:

if the annotation cloud.google.com/network-tier was used in service resource and it is left without value or incorrect value(say xyz) , the service goes to Pending status with only warning
Warning SyncLoadBalancerFailed 1s (x3 over 17s) service-controller Error syncing load balancer: failed to ensure load balancer: unsupported network tier: "xyz"
, to avoid that , added the VAP .

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.

[miyadav]

/jira refresh

[openshift-ci-robot]

@miyadav: This pull request references Jira Issue OCPBUGS-48481, which is invalid:

• expected the bug to target the "4.19.0" version, but no target version was set

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.

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.

[miyadav]

/jira refresh

[openshift-ci-robot]

@miyadav: This pull request references Jira Issue OCPBUGS-48481, 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 @miyadav

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-robot: GitHub didn't allow me to request PR reviews from the following users: miyadav.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@miyadav: This pull request references Jira Issue OCPBUGS-48481, 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 @miyadav

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.

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.

[miyadav]

validated for azure as well.

[openshift-ci-robot]

@miyadav: This pull request references Jira Issue OCPBUGS-48481, 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 @miyadav

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-robot: GitHub didn't allow me to request PR reviews from the following users: miyadav.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@miyadav: This pull request references Jira Issue OCPBUGS-48481, 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 @miyadav

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.

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.

[miyadav]

/jira refresh

[openshift-ci-robot]

@miyadav: This pull request references Jira Issue OCPBUGS-48481, 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 @sunzhaohua2

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.

[sunzhaohua2]

/retest-required

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 84ac6e4 and 2 for PR HEAD a637b1f in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 84ac6e4 and 2 for PR HEAD a637b1f in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 84ac6e4 and 2 for PR HEAD a637b1f in total

[JoelSpeed]

@miyadav Can you take a look at the failing units? They look as though they could be legitimate issues

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 84ac6e4 and 2 for PR HEAD a637b1f in total

[miyadav]

/retest-required

[openshift-ci]

@miyadav: 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/okd-scos-e2e-aws-ovn	b93ed3c	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-vsphere-ovn	b93ed3c	link	false	/test e2e-vsphere-ovn
ci/prow/e2e-openstack-ovn	b93ed3c	link	false	/test e2e-openstack-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.

[JoelSpeed]

/lgtm

[openshift-ci-robot]

@miyadav: Jira Issue OCPBUGS-48481: All pull requests linked via external trackers have merged:

• openshift/cluster-cloud-controller-manager-operator#379

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

In response to this:

if the annotation cloud.google.com/network-tier was used in service resource and it is left without value or incorrect value(say xyz) , the service goes to Pending status with only warning
Warning SyncLoadBalancerFailed 1s (x3 over 17s) service-controller Error syncing load balancer: failed to ensure load balancer: unsupported network tier: "xyz"
, to avoid that , added the VAP .

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]

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-cloud-controller-manager-operator
This PR has been included in build ose-cluster-cloud-controller-manager-operator-container-v4.19.0-202502241207.p0.ga4f2374.assembly.stream.el9.
All builds following this will include this PR.

[miyadav]

/label qe-approved

[openshift-ci-robot]

@miyadav: Jira Issue OCPBUGS-48481 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state.

In response to this:

if the annotation cloud.google.com/network-tier was used in service resource and it is left without value or incorrect value(say xyz) , the service goes to Pending status with only warning
Warning SyncLoadBalancerFailed 1s (x3 over 17s) service-controller Error syncing load balancer: failed to ensure load balancer: unsupported network tier: "xyz"
, to avoid that , added the VAP .

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.

[miyadav]

/jira refresh

[openshift-ci-robot]

@miyadav: Jira Issue OCPBUGS-48481 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state.

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.