Skip to content

Improve IPv4 and IPv6 requirements#10

Open
aneta-petrova wants to merge 1 commit intomasterfrom
sourcery-ipv
Open

Improve IPv4 and IPv6 requirements#10
aneta-petrova wants to merge 1 commit intomasterfrom
sourcery-ipv

Conversation

@aneta-petrova
Copy link
Copy Markdown
Owner

@aneta-petrova aneta-petrova commented Nov 12, 2025

What changes are you introducing?

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

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

Contributor 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.16/Katello 4.18 (Satellite 6.18)
  • Foreman 3.15/Katello 4.17
  • Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4)
  • Foreman 3.13/Katello 4.15 (EL9 only)
  • Foreman 3.12/Katello 4.14 (Satellite 6.16; orcharhino 7.2 on EL9 only; orcharhino 7.3)
  • Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9; orcharhino 7.1 with Leapp)
  • Foreman 3.10/Katello 4.12
  • Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
  • We do not accept PRs for Foreman older than 3.9.

Summary by Sourcery

Documentation:

  • Clarify IPv4 and IPv6 configuration requirements in the common modules reference

Copy link
Copy Markdown

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey there - I've reviewed your changes and they look great!

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc:14` </location>
<code_context>
 The loopback is typically configured by default.
 Do not disable it.
-* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter.
+Using the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option will break the installation.

 The following requirements apply to installations in an IPv6 network:
</code_context>

<issue_to_address>
**suggestion (review_instructions):** No troubleshooting or error recognition steps are provided for the scenario where these settings break the installation.

Consider adding guidance on how users can recognize if the installation is broken due to these settings, and steps to troubleshoot or resolve the issue if encountered.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `guides/common/modules/*.adoc`

**Instructions:**
Troubleshooting and error recognition steps are included where appropriate.

</details>
</issue_to_address>

### Comment 2
<location> `guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc:14` </location>
<code_context>
 The loopback is typically configured by default.
 Do not disable it.
-* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter.
+Using the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option will break the installation.

 The following requirements apply to installations in an IPv6 network:
</code_context>

<issue_to_address>
**suggestion (review_instructions):** This sentence describes a product feature's effect rather than a user story or user action.

Consider rephrasing to focus on what the user should do or avoid, e.g., "To ensure a successful installation, do not use the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option."

<details>
<summary>Review instructions:</summary>

**Path patterns:** `guides/common/modules/*.adoc,guides/common/*.adoc`

**Instructions:**
Documentation describes a user story rather than a product feature.

</details>
</issue_to_address>

### Comment 3
<location> `guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc:14` </location>
<code_context>
 The loopback is typically configured by default.
 Do not disable it.
-* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter.
+Using the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option will break the installation.

 The following requirements apply to installations in an IPv6 network:
</code_context>

<issue_to_address>
**suggestion (review_instructions):** The sentence focuses on the consequences of a feature rather than instructing the user on an action or task.

It would be clearer to instruct the user directly, e.g., "Do not use the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option."

<details>
<summary>Review instructions:</summary>

**Path patterns:** `guides/common/modules/*.adoc,guides/common/*.adoc`

**Instructions:**
Documentation focuses on actions and tasks to be performed rather than features.

</details>
</issue_to_address>

### Comment 4
<location> `guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc:14` </location>
<code_context>
 The loopback is typically configured by default.
 Do not disable it.
-* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter.
+Using the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option will break the installation.

 The following requirements apply to installations in an IPv6 network:
</code_context>

<issue_to_address>
**suggestion (review_instructions):** The sentence could be more precise and unambiguous about the consequences of using these options.

The phrase "will break the installation" is somewhat vague. It would be clearer to specify what exactly will break or what the user should expect if these options are used. For example, "Using the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option will prevent the installation from completing successfully."

<details>
<summary>Review instructions:</summary>

**Path patterns:** `guides/common/modules/*.adoc,guides/common/*.adoc`

**Instructions:**
Text is clear, concise, precise, and unambiguous.

</details>
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@aneta-petrova
Copy link
Copy Markdown
Owner Author

@sourcery-ai review

Copy link
Copy Markdown

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey there - I've reviewed your changes and they look great!

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc:14` </location>
<code_context>
 The loopback is typically configured by default.
 Do not disable it.
-* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter.
+Using the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option will break the installation.

 The following requirements apply to installations in an IPv6 network:
</code_context>

<issue_to_address>
**suggestion (review_instructions):** No troubleshooting or error recognition steps are provided for the scenario where these settings break the installation.

Since the line states that using these options will break the installation, it would be helpful to include troubleshooting steps or guidance on how to recognize and resolve issues if these settings are applied inadvertently.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `guides/common/modules/*.adoc`

**Instructions:**
Troubleshooting and error recognition steps are included where appropriate.

</details>
</issue_to_address>

### Comment 2
<location> `guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc:14` </location>
<code_context>
 The loopback is typically configured by default.
 Do not disable it.
-* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter.
+Using the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option will break the installation.

 The following requirements apply to installations in an IPv6 network:
</code_context>

<issue_to_address>
**suggestion (review_instructions):** This sentence describes a product feature's effect rather than framing it as a user story.

Consider rephrasing to focus on the user's actions and the consequences, such as: "If you disable IPv6 using either the kernel parameter or the sysctl option, the installation will fail. Ensure these settings are not applied." This helps frame the documentation around what the user should do or avoid, rather than just stating a feature's limitation.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `guides/common/modules/*.adoc,guides/common/*.adoc`

**Instructions:**
Documentation describes a user story rather than a product feature.

</details>
</issue_to_address>

### Comment 3
<location> `guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc:14` </location>
<code_context>
 The loopback is typically configured by default.
 Do not disable it.
-* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter.
+Using the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option will break the installation.

 The following requirements apply to installations in an IPv6 network:
</code_context>

<issue_to_address>
**suggestion (review_instructions):** The sentence focuses on the effect of a feature rather than guiding the user on what actions to take.

To better align with task-focused documentation, rephrase to instruct the user: "Do not use the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option, as these will break the installation." This makes the documentation actionable.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `guides/common/modules/*.adoc,guides/common/*.adoc`

**Instructions:**
Documentation focuses on actions and tasks to be performed rather than features.

</details>
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@aneta-petrova
Copy link
Copy Markdown
Owner Author

@sourcery-ai review

Copy link
Copy Markdown

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey there - I've reviewed your changes and they look great!

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc:14` </location>
<code_context>
 The loopback is typically configured by default.
 Do not disable it.
-* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter.
+Using the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option will break the installation.

 The following requirements apply to installations in an IPv6 network:
</code_context>

<issue_to_address>
**suggestion (review_instructions):** No troubleshooting or error recognition steps are provided for the scenario where these settings break the installation.

Consider adding guidance on how to recognize if the installation is broken due to these settings, and steps to troubleshoot or resolve the issue.

<details>
<summary>Review instructions:</summary>

**Path patterns:** `guides/common/modules/*.adoc`

**Instructions:**
Troubleshooting and error recognition steps are included where appropriate.

</details>
</issue_to_address>

### Comment 2
<location> `guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc:14` </location>
<code_context>
 The loopback is typically configured by default.
 Do not disable it.
-* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter.
+Using the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option will break the installation.

 The following requirements apply to installations in an IPv6 network:
</code_context>

<issue_to_address>
**suggestion (review_instructions):** This line describes a technical feature and its effect, rather than framing it in terms of a user story.

Consider rephrasing to focus on the user's actions and the consequences, such as: "To ensure a successful installation, avoid disabling IPv6 using either the kernel parameter or the sysctl option."

<details>
<summary>Review instructions:</summary>

**Path patterns:** `guides/common/modules/*.adoc,guides/common/*.adoc`

**Instructions:**
Documentation describes a user story rather than a product feature.

</details>
</issue_to_address>

### Comment 3
<location> `guides/common/modules/ref_ipv6-and-ipv4-requirements.adoc:14` </location>
<code_context>
 The loopback is typically configured by default.
 Do not disable it.
-* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter.
+Using the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option will break the installation.

 The following requirements apply to installations in an IPv6 network:
</code_context>

<issue_to_address>
**suggestion (review_instructions):** This line focuses on configuration features rather than guiding the user through specific actions or tasks.

It would be clearer to instruct the user on what to do or not do, e.g., "Do not disable IPv6 using these options to avoid installation issues."

<details>
<summary>Review instructions:</summary>

**Path patterns:** `guides/common/modules/*.adoc,guides/common/*.adoc`

**Instructions:**
Documentation focuses on actions and tasks to be performed rather than features.

</details>
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant