Skip to content

feat(neutron): make Helm timeout configurable - #4250

Merged
Mohammed Naser (mnaser) merged 2 commits into
mainfrom
agent/neutron-helm-timeout
Aug 12, 2026
Merged

feat(neutron): make Helm timeout configurable#4250
Mohammed Naser (mnaser) merged 2 commits into
mainfrom
agent/neutron-helm-timeout

Conversation

@fitbeard

Copy link
Copy Markdown
Contributor

What changed

  • add neutron_helm_timeout with a five-minute default;
  • use it for Neutron Helm operations;
  • add a release note.

Why

Deployments that need more time had no supported way to extend the Helm operation timeout.

This production improvement is extracted from #4152 so it can be reviewed, released, and backported independently from selective CI.

Validation

  • file-scoped pre-commit hooks passed;
  • git diff --check passed;
  • the repository-wide Ansible lint traversal reached all roles and only failed on the existing galaxy[no-changelog] metadata issue;
  • Reno parsed the new note and only reported the repository's existing duplicate release-note UID.

Signed-off-by: Tadas Sutkaitis <tadas.sutkaitis@vexxhost.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1d45d25842

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "Codex (@codex) review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".

@@ -0,0 +1,4 @@
---

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Add the required DCO sign-off

The reviewed commit object cd260781aa5d72ecb713a8a1f8c92d6d06991c67 has no Signed-off-by: trailer, so it does not satisfy the repository's DCO requirement and should be recreated with the author's sign-off before merging.

AGENTS.md reference: AGENTS.md:L9-L9

Useful? React with 👍 / 👎.

---
features:
- |
The Neutron role now exposes ``neutron_helm_timeout`` to configure how long\n Helm operations may run.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Replace the literal newline escape

YAML literal blocks do not interpret \n, so Reno will publish this as visible backslash text and spaces between “long” and “Helm.” Replace the escape with an actual line break or a normal space so the release note renders as natural English.

AGENTS.md reference: AGENTS.md:L18-L23

Useful? React with 👍 / 👎.

# Time to wait for Helm operations to complete, using Go duration syntax.
#
# neutron_helm_timeout: 10m0s
neutron_helm_timeout: 5m0s

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Document the new timeout setting

This adds a public role setting but updates only the default and release note; a repository-wide search confirms that doc/source/deploy/neutron.rst, which already documents Neutron configuration variables, does not mention neutron_helm_timeout. Add usage documentation there so operators can discover and configure the feature after the release note ages out.

AGENTS.md reference: AGENTS.md:L38-L40

Useful? React with 👍 / 👎.

Signed-off-by: Tadas Sutkaitis <tadas.sutkaitis@vexxhost.com>
@fitbeard

Copy link
Copy Markdown
Contributor Author

recheck

1 similar comment
@fitbeard

Copy link
Copy Markdown
Contributor Author

recheck

@mnaser
Mohammed Naser (mnaser) merged commit c8af392 into main Aug 12, 2026
15 checks passed
@mnaser
Mohammed Naser (mnaser) deleted the agent/neutron-helm-timeout branch August 12, 2026 00:15
@vexxhost-bot

Copy link
Copy Markdown
Collaborator

Backport failed for stable/zed, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin stable/zed
git worktree add -d .worktree/backport-4250-to-stable/zed origin/stable/zed
cd .worktree/backport-4250-to-stable/zed
git switch --create backport-4250-to-stable/zed
git cherry-pick -x c8af392b294f90cb2262b2f922930771007679fa

@vexxhost-bot

Copy link
Copy Markdown
Collaborator

Backport failed for stable/2023.1, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin stable/2023.1
git worktree add -d .worktree/backport-4250-to-stable/2023.1 origin/stable/2023.1
cd .worktree/backport-4250-to-stable/2023.1
git switch --create backport-4250-to-stable/2023.1
git cherry-pick -x c8af392b294f90cb2262b2f922930771007679fa

@vexxhost-bot

Copy link
Copy Markdown
Collaborator

Backport failed for stable/2023.2, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin stable/2023.2
git worktree add -d .worktree/backport-4250-to-stable/2023.2 origin/stable/2023.2
cd .worktree/backport-4250-to-stable/2023.2
git switch --create backport-4250-to-stable/2023.2
git cherry-pick -x c8af392b294f90cb2262b2f922930771007679fa

@vexxhost-bot

Copy link
Copy Markdown
Collaborator

Successfully created backport PR for stable/2024.1:

@vexxhost-bot

Copy link
Copy Markdown
Collaborator

Successfully created backport PR for stable/2024.2:

@vexxhost-bot

Copy link
Copy Markdown
Collaborator

Successfully created backport PR for stable/2025.1:

@vexxhost-bot

Copy link
Copy Markdown
Collaborator

Successfully created backport PR for stable/2025.2:

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.

3 participants