Skip to content

Conversation

@zaneb
Copy link
Member

@zaneb zaneb commented Nov 21, 2025

The agent-interactive-console and agent-interactive-console-serial@ services should have consistent Before/After edges since only one runs on each system (depending on whether there is a graphical console).

Previously, set-hostname.service had a Before= dependency on agent-interactive-console.service only, which created an edge in the systemd diagrams from set-hostname to agent-interactive-console but not to agent-interactive-console-serial@.

This fixes the inconsistency by:

  • Adding set-hostname.service to the After= directive in both console services
  • Removing the redundant Before= directive from set-hostname.service

Both services now define the dependency consistently in the same direction.

(This is the first bug detected by our new autogenerated dependency diagrams!)

…rvices

The agent-interactive-console and agent-interactive-console-serial@
services should have consistent Before/After edges since only one runs
on each system (depending on whether there is a graphical console).

Previously, set-hostname.service had a Before= dependency on
agent-interactive-console.service only, which created an edge in the
systemd diagrams from set-hostname to agent-interactive-console but not
to agent-interactive-console-serial@.

This fixes the inconsistency by:
- Adding set-hostname.service to the After= directive in both console
  services
- Removing the redundant Before= directive from set-hostname.service

Both services now define the dependency consistently in the same
direction.

Assisted-by: Claude Code
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 21, 2025
@openshift-ci-robot
Copy link
Contributor

@zaneb: This pull request references Jira Issue OCPBUGS-65859, which is invalid:

  • expected the bug to target either version "4.21." or "openshift-4.21.", but it targets "4.20.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

The agent-interactive-console and agent-interactive-console-serial@ services should have consistent Before/After edges since only one runs on each system (depending on whether there is a graphical console).

Previously, set-hostname.service had a Before= dependency on agent-interactive-console.service only, which created an edge in the systemd diagrams from set-hostname to agent-interactive-console but not to agent-interactive-console-serial@.

This fixes the inconsistency by:

  • Adding set-hostname.service to the After= directive in both console services
  • Removing the redundant Before= directive from set-hostname.service

Both services now define the dependency consistently in the same direction.

(This is the first bug detected by our new autogenerated dependency diagrams!)

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 requested review from andfasano and bfournie November 21, 2025 03:29
The agent-interactive-console and agent-interactive-console-serial@
services should have consistent Before/After edges. Previously,
agent-auth-token-status.service had agent-interactive-console.service
in its After= directive, but there was no corresponding dependency for
the serial console variant.

This adds agent-auth-token-status.service to the Before= directive in
both console services, and removes the now-redundant After= directive
from agent-auth-token-status.service, so both services define the
dependency consistently in the same direction.

Assisted-by: Claude Code
@andfasano
Copy link
Contributor

/approve
/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 21, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2025

@zaneb: 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-agent-two-node-fencing-ipv4 85aac1a link false /test e2e-agent-two-node-fencing-ipv4
ci/prow/e2e-agent-compact-ipv4-iso-no-registry 85aac1a link false /test e2e-agent-compact-ipv4-iso-no-registry

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.

@bfournie
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 21, 2025
@zaneb
Copy link
Member Author

zaneb commented Nov 23, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 23, 2025
@openshift-ci-robot
Copy link
Contributor

@zaneb: This pull request references Jira Issue OCPBUGS-65859, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mhanss

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 requested a review from mhanss November 23, 2025 20:55
@zaneb
Copy link
Member Author

zaneb commented Dec 2, 2025

/assign @mhanss

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants