Skip to content

CNV-37050: OVN-K secondary network IP address management #80724

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.

Sign up for GitHub

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

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

CNV-37050: OVN-K secondary network IP address management #80724

wants to merge 1 commit into from

Conversation

sjhala-ccs
Copy link
Contributor

@sjhala-ccs sjhala-ccs commented Aug 20, 2024 •
edited
Loading

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 20, 2024 •
edited by openshift-ci bot
Loading

@sjhala-ccs: This pull request references CNV-37050 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 story to target the "4.18.0" version, but no target version was set.

In response to this:

Version(s): 4.17+

Issue: CNV-37050

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 20, 2024
@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 20, 2024
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Aug 20, 2024 •
edited
Loading

🤖 Thu Aug 22 15:19:27 - Prow CI generated the docs preview:

https://80724--ocpdocs-pr.netlify.app/openshift-dedicated/latest/virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.html
https://80724--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.html
https://80724--ocpdocs-pr.netlify.app/openshift-rosa/latest/virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.html

@sjhala-ccs sjhala-ccs added CNV Label for all CNV PRs branch/enterprise-4.17 labels Aug 20, 2024
@sjhala-ccs sjhala-ccs added this to the Planned for 4.17 GA milestone Aug 20, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 20, 2024 •
edited by openshift-ci bot
Loading

@sjhala-ccs: This pull request references CNV-37050 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 story to target the "4.18.0" version, but no target version was set.

In response to this:

Version(s): 4.17+

Issue: CNV-37050

Link to docs preview: https://80724--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.html#creating-ovn-nad_virt-connecting-vm-to-ovn-secondary-network

QE review:

  • QE has approved this change.

Additional information:

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.

@sjhala-ccs
Copy link
Contributor Author

/retest

@sjhala-ccs sjhala-ccs force-pushed the cnv-37050 branch 3 times, most recently from 583fa59 to 9486d04 Compare August 21, 2024 14:06
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Aug 22, 2024

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

@kalexand-rh
Copy link
Contributor

The branch/enterprise-4.18 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.17. And any PR going into main must also target the latest version branch (enterprise-4.18).

If the update in your PR does NOT apply to version 4.18 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 30, 2024
@openshift-merge-robot
Copy link

PR needs rebase.

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.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 30, 2024
@sjhala-ccs
Copy link
Contributor Author

This feature has been moved to backlog because of change in priorities. The PR is on hold for now.

@sjhala-ccs sjhala-ccs added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 10, 2025
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 10, 2025
@sjhala-ccs
Copy link
Contributor Author

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Feb 18, 2025
@bergerhoffer
Copy link
Contributor

The branch/enterprise-4.19 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.18. And any PR going into main must also target the latest version branch (enterprise-4.19).

If the update in your PR does NOT apply to version 4.19 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
branch/enterprise-4.17 branch/enterprise-4.18 branch/enterprise-4.19 CNV Label for all CNV PRs do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
Continuous Release
Development

Successfully merging this pull request may close these issues.
7 participants
@sjhala-ccs @openshift-ci-robot @ocpdocs-previewbot @kalexand-rh @openshift-bot @openshift-merge-robot @bergerhoffer