Skip to content

Comments

AGENT-1447: Override prefilled rendezvousIP#256

Open
pawanpinjarkar wants to merge 1 commit intoopenshift:mainfrom
pawanpinjarkar:prefilled-rendezvousIP-tui
Open

AGENT-1447: Override prefilled rendezvousIP#256
pawanpinjarkar wants to merge 1 commit intoopenshift:mainfrom
pawanpinjarkar:prefilled-rendezvousIP-tui

Conversation

@pawanpinjarkar
Copy link
Contributor

@pawanpinjarkar pawanpinjarkar commented Feb 16, 2026

This PR adds support for interactive UI mode in agent-tui, allowing users to override a prefilled rendezvous IP address. When the agent-tui detects it's running in interactive mode with a prefilled IP, it displays a timeout modal giving users the option to modify the IP or quit, with an automatic timeout to proceed with the existing configuration.

To test, run make test.

To test TUI manually on local machine:

  1. Test interactive mode with prefilled IP:
    • Create sentinel file: sudo touch /etc/assisted/interactive-ui
    • Set rendezvous IP in /etc/assisted/rendezvous-host.env
    • make run - should display timeout modal with prefilled IP
  2. Test interactive mode without prefilled IP:
    • Create sentinel file while rendezvous-host.env does not have an IP
    • make run - should show rendezvous IP form directly with options to enter rendezvous IP, save rendezvous IP button, this is the rendezvous node button and a configure network button
  3. Test non-interactive mode:
    • Delete sentinel file
    • make run - should show usual registry connectivity check screen.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 16, 2026
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 16, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 16, 2026

@pawanpinjarkar: This pull request references AGENT-1447 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

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
Copy link

openshift-ci bot commented Feb 16, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci
Copy link

openshift-ci bot commented Feb 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pawanpinjarkar

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

The pull request process is described here

Details 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 Feb 16, 2026
@pawanpinjarkar pawanpinjarkar force-pushed the prefilled-rendezvousIP-tui branch 2 times, most recently from 4ae9cbf to c7dcf5f Compare February 16, 2026 19:57
@pawanpinjarkar pawanpinjarkar marked this pull request as ready for review February 16, 2026 19:57
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 16, 2026
@openshift-ci openshift-ci bot requested review from andfasano and zaneb February 16, 2026 19:57
@pawanpinjarkar pawanpinjarkar force-pushed the prefilled-rendezvousIP-tui branch from c7dcf5f to fe82cf5 Compare February 16, 2026 21:53
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 17, 2026

@pawanpinjarkar: This pull request references AGENT-1447 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This PR adds support for interactive UI mode in agent-tui, allowing users to override a prefilled rendezvous IP address. When the agent-tui detects it's running in interactive mode with a prefilled IP, it displays a timeout modal giving users the option to modify the IP or quit, with an automatic timeout to proceed with the existing configuration.

To test, run make test.

To test TUI manually on local machine:

  1. Test interactive mode with prefilled IP:
    • Create sentinel file: sudo touch /etc/assisted/interactive-ui
    • Set rendezvous IP in /etc/assisted/rendezvous-host.env
    • make run - should display timeout modal with prefilled IP
  2. Test interactive mode without prefilled IP:
    • Create sentinel file while rendezvous-host.env does not have an IP
    • make run - should show rendezvous IP form directly with options to enter rendezvous IP, save rendezvous IP button, this is the rendezvous node button and a configure network button
  3. Test non-interactive mode:
    • Delete sentinel file
    • make run - should show usual registry connectivity check screen.

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.

If an user has provided rendezvousIP from the SaaS UI, the TUI will now
show that prefilled rendezvousIP and user will have an option to modify it.

- Detect interactive mode via sentinel file (/etc/assisted/interactive-ui)
- Support prefilled rendezvous IP passed from SaaS UI
- Display 20-second timeout when interactive mode has prefilled rendezvous IP
- Moved "Configure Network" to the first screen
- Enhanced navigation on rendezvous IP page with 4 focusable elements
- Added new tests
- Added a new Makefile target, `make test`

The TUI now handles three distinct flows:
1. Interactive mode + prefilled IP from SaaS UI: Shows timeout with an option to modify the rendezvous IP
2. Interactive mode without IP: Shows rendezvous IP form directly
3. Non-interactive mode: Shows registry check screen (existing behavior)

Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com
@pawanpinjarkar pawanpinjarkar force-pushed the prefilled-rendezvousIP-tui branch from fe82cf5 to fb43682 Compare February 17, 2026 02:16
@pawanpinjarkar
Copy link
Contributor Author

/test verify-vendor

@openshift-ci
Copy link

openshift-ci bot commented Feb 17, 2026

@pawanpinjarkar: all tests passed!

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.

@pawanpinjarkar
Copy link
Contributor Author

/cc @rwsu @bfournie

@openshift-ci openshift-ci bot requested review from bfournie and rwsu February 19, 2026 14:38
u.configureNetworkForm.SetButtonsAlign(tview.AlignRight)
u.configureNetworkForm.AddButton(RENDEZVOUS_CONFIGURE_NETWORK_BUTTON, func() {
u.showNMTUIWithErrorDialog(func() {
u.setFocusToRendezvousIP()
Copy link
Contributor

Choose a reason for hiding this comment

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

After quitting from nmtui, the UI redirects to a page showing the release image checks. It should go back to the rendezvous IP form.

Copy link
Contributor

Choose a reason for hiding this comment

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

Screen.Recording.2026-02-19.at.10.16.40.AM.mov

mainFlex.SetTitle(" Rendezvous node setup ").
AddItem(u.selectIPForm, 3, 0, false).
AddItem(separator, 1, 0, false).
AddItem(u.configureNetworkForm, 3, 0, false)
Copy link
Contributor

Choose a reason for hiding this comment

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

The bottom border is missing.

Image

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/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants