MGMT-21659: clarify conditions for starting the cluster install

[zszabo-rh]

According to MGMT-21659 the chatbot occasionally claims that the installation is supposed to start automatically once the hosts have registered.

I wasn’t able to reproduce this behavior during my test conversations, but I added an extra instruction to the system prompt to ensure this response never occurs.

Summary by CodeRabbit

• Documentation
  • Clarified installation flow to require explicit user initiation; removed any wording that could imply automatic start and now instructs showing a clear "ready to start installation" prompt before proceeding.
  • Updated guidance and user-facing messaging to ensure installers request and await user confirmation prior to beginning installation, improving safety and predictability.

[openshift-ci-robot]

@zszabo-rh: This pull request references MGMT-21659 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.21.0" version, but no target version was set.

Details

In response to this:

According to MGMT-21659 the chatbot occasionally claims that the installation is supposed to start automatically once the hosts have registered.

I wasn’t able to reproduce this behavior during my test conversations, but I added an extra instruction to the system prompt to ensure this response never occurs.

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

Walkthrough

Added an explicit safety directive in template.yaml under the Initiate Installation step: installation must never start automatically and must be explicitly initiated by the user; wording changed to use phrases like "ready to start installation."

Changes

Cohort / File(s)	Summary
Installation initiation safety guidance template.yaml	Replaced any implication of automatic installation start with explicit guidance that installation never starts automatically and must be explicitly initiated by the user; updated phrasing to use "ready to start installation" style prompts.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify the revised phrasing unambiguously requires explicit user initiation.
• Check consistency with other prompts or automation hooks that might imply auto-start.

Possibly related PRs

• MGMT-21349: system prompt update for vips #150: Also updates "Initiate Installation" messaging to require explicit user confirmation and avoid implying automatic startup.
• MGMT-21787: Update prompt to include platform integration #218: Modifies the assistant prompt's Initiate Installation wording in template.yaml, with overlapping changes to initiation prompts.
• MGMT-21690: chatbot installation asks again for host and cluster IDs #195: Previously adjusted messaging around installation initiation; may overlap in wording or flow.

Suggested labels

lgtm, ok-to-test

Suggested reviewers

• keitwb
• omertuc

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title 'MGMT-21659: clarify conditions for starting the cluster install' directly relates to the main change in the changeset. The summary indicates the PR adds an explicit directive to ensure installation must never start automatically and must be explicitly initiated by the user. The title accurately captures this core intent—clarifying the conditions for starting the cluster install by removing ambiguity about automatic startup.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f45cd32 and d0777d6.

📒 Files selected for processing (1)

• template.yaml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• template.yaml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci-robot]

@zszabo-rh: This pull request references MGMT-21659 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.21.0" version, but no target version was set.

Details

In response to this:

According to MGMT-21659 the chatbot occasionally claims that the installation is supposed to start automatically once the hosts have registered.

I wasn’t able to reproduce this behavior during my test conversations, but I added an extra instruction to the system prompt to ensure this response never occurs.

Summary by CodeRabbit

• Documentation
• Updated installation flow guidance to enforce explicit user-initiated startup, replacing automatic startup implications with clearer messaging that installation is ready to begin upon user action.

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.

[eranco74]

LGTM
just a nit

[eranco74]

Suggested change

	* **CRITICAL: Installation NEVER starts automatically.** Installation must always be explicitly initiated by the user's request. Never claim that installation will begin automatically when hosts register, are discovered, or meet requirements. Use phrases like "ready to start installation" or "installation can now be initiated" instead of "installation will begin automatically."
	* **CRITICAL: Installation NEVER starts automatically.** Installation must always be explicitly initiated per the user's request. Never claim that installation will begin automatically when hosts register, are discovered, or meet requirements. Use phrases like "ready to start installation" or "installation can now be initiated" instead of "installation will begin automatically."

[openshift-ci-robot]

@zszabo-rh: This pull request references MGMT-21659 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.21.0" version, but no target version was set.

Details

In response to this:

According to MGMT-21659 the chatbot occasionally claims that the installation is supposed to start automatically once the hosts have registered.

I wasn’t able to reproduce this behavior during my test conversations, but I added an extra instruction to the system prompt to ensure this response never occurs.

Summary by CodeRabbit

• Documentation
• Clarified installation flow to require explicit user initiation; removed any wording that could imply automatic start and now instructs showing a clear "ready to start installation" prompt before proceeding.
• Updated guidance and user-facing messaging to ensure installers request and await user confirmation prior to beginning installation, improving safety and predictability.

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.

[zszabo-rh]

/test eval-test

[eranco74]

/lgtm