Skip to content

Conversation

@Mujib-Ahasan
Copy link

@Mujib-Ahasan Mujib-Ahasan commented Nov 28, 2025

closes #27290

Checklist

Ensure you have completed the following checklist for your pull request to be reviewed:

  • Certify you wrote the patch or otherwise have the right to pass it on as an open-source patch by signing all
    commits. (git commit -s). (If needed, use git commit -s --amend). The author email must match
    the sign-off email address. See CONTRIBUTING.md
    for more information.
  • Referenced issues using Fixes: #00000 in commit message (if applicable)
  • Tests have been added/updated (or no tests are needed)
  • Documentation has been updated (or no documentation changes are needed)
  • All commits pass make validatepr (format/lint checks)
  • Release note entered in the section below (or None if no user-facing changes)

Does this PR introduce a user-facing change?

None

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 28, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Mujib-Ahasan
Once this PR has been reviewed and has the lgtm label, please assign mheon for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

Copy link
Member

@Honny1 Honny1 left a comment

Choose a reason for hiding this comment

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

I reviewed the code and have some suggestions for improvements. Please also add a test for this.

}

msg := fmt.Appendf(nil, "EXTEND_TIMEOUT_USEC=%d", step.Microseconds())
if _, err := conn.Write(msg); err != nil {
Copy link
Member

Choose a reason for hiding this comment

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

Can sending messages be simplified using notifyproxy.SendMessage?

extension := 30 * time.Second
timerFreq := 25 * time.Second

if c.config.SdNotifySocket != "" && needsExtension {
Copy link
Member

Choose a reason for hiding this comment

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

What if c.config.SdNotifySocket is empty?


notifyproxy.SendMessage should already handle that.

@Mujib-Ahasan
Copy link
Author

Mujib-Ahasan commented Dec 3, 2025

Hey @Honny1, could you please be more specific about the test case?? I simplified the message sending as you mentioned, but confused about the test coverage.

@packit-as-a-service
Copy link

Cockpit tests failed for commit 0876822. @martinpitt, @jelly, @mvollmer please check.

@Honny1
Copy link
Member

Honny1 commented Dec 4, 2025

Sure. I mean a test case that reproduces the original issue. It should fail without your fix and pass with it.

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.

Quadlet: Container with Notify=healthy does not respect HealthStartPeriod larger than systemd TimeoutStartSec

2 participants