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

CNV-55889: SSH over LoadBalancer creates Service with incorrect selector #2419

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

avivtur
Copy link
Member

@avivtur avivtur commented Feb 4, 2025

📝 Description

Replacing load balancer service selector according to: https://issues.redhat.com/browse/CNV-55889

🎥 Demo

Before:
selector-service-b4

After:
correct-selector-service

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Feb 4, 2025

@avivtur: This pull request references CNV-55889 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 bug to target the "4.19.0" version, but no target version was set.

In response to this:

📝 Description

Replacing load balancer service selector according to: https://issues.redhat.com/browse/CNV-55889

🎥 Demo

Before:
selector-service-b4

After:
correct-selector-service

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 approved This issue is something we want to fix label Feb 4, 2025
@avivtur
Copy link
Member Author

avivtur commented Feb 4, 2025

/jira refresh

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Feb 4, 2025

@avivtur: This pull request references CNV-55889 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 bug to target either version "4.19." or "openshift-4.19.", but it targets "CNV v4.19.0" instead.

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 added the lgtm Passed code review, ready for merge label Feb 4, 2025
Copy link
Contributor

openshift-ci bot commented Feb 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avivtur, upalatucci

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

@sarahbx
Copy link

sarahbx commented Feb 4, 2025

/hold

@sarahbx
Copy link

sarahbx commented Feb 4, 2025

@avivtur when using vm.kubevirt.io/name the VM must be selected instead of the VMI

@avivtur
Copy link
Member Author

avivtur commented Feb 4, 2025

@avivtur when using vm.kubevirt.io/name the VM must be selected instead of the VMI

@sarahbx what do you mean?

@sarahbx
Copy link

sarahbx commented Feb 4, 2025

@avivtur when using vm.kubevirt.io/name the VM must be selected instead of the VMI

@sarahbx what do you mean?

In your example above, the VMI is referenced, not the VM.
VMI name: fedora-sapphire-piranha-33-{random-suffix}
VM name: fedora-sapphire-piranha-33

So the Pod selector would be:
vm.kubevirt.io/name: fedora-sapphire-piranha-33

@avivtur avivtur force-pushed the fix-loadbalancer-service-selector branch from f8c450f to aa2d2bd Compare February 6, 2025 17:06
@openshift-ci openshift-ci bot removed the lgtm Passed code review, ready for merge label Feb 6, 2025
Copy link
Contributor

openshift-ci bot commented Feb 6, 2025

New changes are detected. LGTM label has been removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved This issue is something we want to fix do-not-merge/hold jira/valid-reference
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants