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

Add note about virt-who not supporting IPv6 in 6.17 #3687

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

bangelic
Copy link
Contributor

What changes are you introducing?

Adding a note that virt-who does not
support IPv6 in 6.17.

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

Referring to https://issues.redhat.com/browse/SAT-31196.

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

Checklists

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

  • Foreman 3.14/Katello 4.16
  • Foreman 3.13/Katello 4.15 (EL9 only)
  • Foreman 3.12/Katello 4.14 (Satellite 6.16)
  • Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9)
  • Foreman 3.10/Katello 4.12
  • Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
  • Foreman 3.8/Katello 4.10
  • Foreman 3.7/Katello 4.9 (Satellite 6.14)
  • We do not accept PRs for Foreman older than 3.7.

@github-actions github-actions bot added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Feb 23, 2025
@apinnick
Copy link
Contributor

Should this info be added to the virt-who guide as well?

@bangelic
Copy link
Contributor Author

Should this info be added to the virt-who guide as well?

I spoke with Justin about this and he said this topic came up in the program call when they discussed collecting all areas that do not support IPv6 in 6.17.

They're still considering the best approach—whether to consolidate all unsupported features in a single location, distribute them across relevant sections, or include them in multiple places. This may require a larger discussion on how they want to handle it. But he thinks having it in too many areas of documentation might be too much and thinks for now this single location will suffice. He also said Ioanna was part of that conversation and he sent her the ticket he had created on this topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs style review Requires a review from docs style/grammar perspective Needs tech review Requires a review from the technical perspective Needs testing Requires functional testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants