Skip to content

Remove unused xinetd parameter from bash_service_command macro - #15027

Open
ggbecker wants to merge 1 commit into
ComplianceAsCode:masterfrom
ggbecker:remove-xinetd-dead-code
Open

Remove unused xinetd parameter from bash_service_command macro#15027
ggbecker wants to merge 1 commit into
ComplianceAsCode:masterfrom
ggbecker:remove-xinetd-dead-code

Conversation

@ggbecker

Copy link
Copy Markdown
Member

The xinetd parameter in bash_service_command has never been used in the codebase and contains inverted logic (a 7+ year old bug where disabling a service sets disable=no, enabling it).

Since:

  • The parameter is not used anywhere in rules or templates
  • A dedicated xinetd_service_disabled template exists with correct logic
  • xinetd has been removed from RHEL 9, RHEL 10, and OL9
  • xinetd is obsolete on modern systems

Remove the dead code rather than fixing the bug.

Changes:

  • Remove xinetd parameter from bash_service_command signature
  • Remove xinetd example from documentation
  • Remove xinetd parameter documentation
  • Remove buggy xinetd code block (lines 735-742)

This cleanup removes confusing, buggy, and unused code without any functional impact since the parameter was never actually utilized.

The xinetd parameter in bash_service_command has never been used in the
codebase and contains inverted logic (a 7+ year old bug where disabling
a service sets disable=no, enabling it).

Since:
- The parameter is not used anywhere in rules or templates
- A dedicated xinetd_service_disabled template exists with correct logic
- xinetd has been removed from RHEL 9, RHEL 10, and OL9
- xinetd is obsolete on modern systems

Remove the dead code rather than fixing the bug.

Changes:
- Remove xinetd parameter from bash_service_command signature
- Remove xinetd example from documentation
- Remove xinetd parameter documentation
- Remove buggy xinetd code block (lines 735-742)

This cleanup removes confusing, buggy, and unused code without any
functional impact since the parameter was never actually utilized.
@ggbecker ggbecker added this to the 0.1.83 milestone Aug 21, 2026
@Mab879 Mab879 self-assigned this Aug 21, 2026
@openshift-ci

openshift-ci Bot commented Aug 21, 2026

Copy link
Copy Markdown

@ggbecker: 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/e2e-aws-openshift-platform-compliance 3f920c6 link true /test e2e-aws-openshift-platform-compliance
ci/prow/e2e-aws-openshift-node-compliance 3f920c6 link false /test e2e-aws-openshift-node-compliance

Full PR test history. Your PR dashboard.

Details

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.

@Mab879

Mab879 commented Aug 21, 2026

Copy link
Copy Markdown
Member

/packit retest-failed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants