Skip to content

Automated Sync from main to stable - #40

Open
rhods-devops-app[bot] wants to merge 713 commits into
stablefrom
main
Open

rhods-devops-app[bot] wants to merge 713 commits into
stablefrom
main

Conversation

@rhods-devops-app

@rhods-devops-app rhods-devops-app Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

Automated Sync from main to stable

This PR automatically syncs the main branch to the stable branch by opening a pull request from main into stable.

Sync Summary

  • Latest commit: 526ee7072 chore(deps): refresh rpm lockfiles [SECURITY] (chore(deps): refresh rpm lockfiles [SECURITY] #152)

  • Total commits to sync: 708

  • Source: https://github.com/red-hat-data-services/OpenShell.git @ main

  • Target: https://github.com/red-hat-data-services/OpenShell.git @ stable

  • PR head: main

Commits to be synced

Merging

GitHub automerge is enabled for this pull request once required checks pass.

Comment thread .github/workflows/codex-security.yml Dismissed
Comment thread .github/workflows/release.yml Fixed
Comment thread .github/workflows/snap-publish.yml Dismissed
@rhods-devops-app
rhods-devops-app Bot enabled auto-merge October 24, 2026 01:13
@coderabbitai

coderabbitai Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

Ask an organization administrator to verify that this bot has an active assigned CodeRabbit review seat. See the seat-assignment guide. After the seat is confirmed, request a review again.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 48d803de-2b57-4cc4-9334-f43b35566c88

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Comment thread .github/workflows/release-auto-tag.yml Dismissed
Comment thread .github/workflows/release-prerelease.yml Dismissed
Comment thread .github/workflows/release.yml Dismissed
@alexxfan

alexxfan commented Nov 6, 2026

Copy link
Copy Markdown

/retest

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
Co-authored-by: red-hat-konflux[bot] <126015336+red-hat-konflux[bot]@users.noreply.github.com>
Signed-off-by: konflux-internal-p02 <170854209+konflux-internal-p02[bot]@users.noreply.github.com>
Co-authored-by: konflux-internal-p02[bot] <170854209+konflux-internal-p02[bot]@users.noreply.github.com>
krishicks and others added 12 commits November 19, 2026 17:57
…ell#5613)

Exec, ForwardTcp, and SSH session records named no resources, so a reader
could not tie a record to the sandbox, relay channel, or session it acted
on, or tell which revoke ended a session.

Name the sandbox and the relay channel each exec or forward opens; an
exec's channel matches the channel_id in the gateway's sandbox logs.
Record a TCP forward's target host and port, and name SSH sessions, and
the SSH forwards that use them, by their generated name. A repeated
revoke records no_op:already_absent. Add [openshell.gateway.audit]
capture_exec_command to record exec command arguments. Environment
variables, standard input, and session tokens are never recorded.

Signed-off-by: Kris Hicks <khicks@nvidia.com>
…ll#4956)

* feat(services): publish authoritative application origins

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* fix(services): align URL schema with separate discovery service

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* fix(services): preserve replay URLs and SDK source compatibility

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* docs(server): link to application URL configuration

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* feat(services): allow disabling gateway application routing

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* chore(server): log enabled application routing modes

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* fix(helm): use canonical service routing configuration

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* refactor(services): derive app listener domain from base URL

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* fix(services): address application URL review feedback

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* fix(supervisor): report app listener route rejections

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

---------

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
…t entries (ai-openshell#5755)

* feat(testkit): run conformance as one program and add unsupported-test entries

Make the openshell-conformance bin the conformance test target
(harness = false) so run, cargo test and nextest execute the same
program. Add OPENSHELL_TEST_UNSUPPORTED, a list of <test>=<issue url>
entries that every interface reports as ignored, with startup,
summary and JUnit reporting, strict checks, and a refusal on forced
runs.

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* docs(testkit): explain why unsupported tests use an environment variable

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* refactor(testkit): leave listing unsupported entries to the caller under libtest

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* docs(testkit): reorder unsupported-tests section and tighten visibility

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* ci(e2e): forward unsupported conformance tests to the program

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* test(ci): temporarily mark a conformance test unsupported to verify forwarding

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* test(ci): remove the temporary unsupported-test entries

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* ci(e2e): source unsupported conformance tests from a YAML file

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* test(ci): temporarily mark a conformance test unsupported to verify the YAML file

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* test(ci): remove the temporary unsupported-test entry

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* refactor(testkit): trim unsupported-tests code and docs, validate environment names

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* refactor(ci): reduce the unsupported-tests script to one yq call

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* ci(e2e): reject unknown environment names in unsupported.yaml

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

---------

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
…-openshell#5771)

The Ubuntu image's apt timer stamps date from image provisioning, so every
test boot catches up apt-daily-upgrade within the hour. Upgrading libc6 or
systemd re-executes PID 1, and a container start in that window fails in
runc with "Message recipient disconnected from message bus without
replying". Mask the apt timers and unattended-upgrades in the setup disk
for the k3s and Docker Ubuntu environments.

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
…#5672)

* feat(helm)!: require opt-in for gateway service routing

BREAKING CHANGE: Helm installations relying on gateway service URLs must explicitly set gatewayConfig."openshell.gateway".service_routing_enabled to true before upgrading. Core and non-Kubernetes defaults remain unchanged.

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* docs(helm): explain app listener ingress prerequisites

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* docs(helm): use derived app listener base URL

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* style(e2e): format Helm routing opt-in configuration

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* docs(helm): move SPIFFE guidance into gateway section

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

* docs(helm): note routing defaults must stay synchronized

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

---------

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
ai-openshell#5265)

* fix(podman): keep a polled stale exit from failing an in-progress start

The gateway's reconcile sweep applies polled snapshots without waiting
for an in-progress start. During a stop/start restart, get_sandbox and
list_sandboxes built the stopped workload from its list entry, so the
previous run's exit was reported as ContainerExited and moved the
sandbox from Starting to Error.

While a start is in progress, inspect a stopped workload before
reporting it. If it is running again, or still shows the exit recorded
before the start, report it as ContainerStarting. A new exit, and any
exit once the start has returned, is still reported. The start is
tracked by a guard that clears the in-progress mark on every return
path.

Closes ai-openshell#5258

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* docs(podman): describe how restarts fence the previous exit

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* fix(podman): keep a restart from containing its own workload

A restart starts the workload before its exited supervisor. Watch
reconciliation, start events, and polled snapshots could inspect the
workload in that gap, see a running workload beside an exited
supervisor, and stop it.

Record the supervisor exit that the start observed. While that start is
in progress, an exited supervisor with the recorded FinishedAt reports
the workload as starting instead of containing it. A missing
supervisor, a new supervisor exit, and any exit after the start returns
are still contained.

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* fix(server): skip the reconcile poll of a sandbox whose start is in progress

StartSandbox holds the sandbox lifecycle gate for the whole driver call,
and the workload can still show its previous exit until the driver starts
it. The watch path already waits on that gate for Starting sandboxes; the
reconcile sweep did not, so a poll could move a restarting sandbox from
Starting to Error. Skip such a sandbox and let the next tick or event
report the settled state. This replaces the Podman-specific fence of
polled snapshots.

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* fix(server): preserve cleanup during start reconciliation

Signed-off-by: Shiju <shiju@nvidia.com>

* fix(server): defer the reconcile sweep for a start claimed by another replica

The sweep skipped a Starting sandbox only when this replica's lifecycle gate was held, so a replica that did not own the start could still apply the previous run's exit. Also skip sandboxes whose driver operation is durably pending. Deletion keeps its own pending-operation handling.

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* test(server): check a sweep still applies an exit after the start settles

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

* refactor(server): narrow the reconcile start guard to the snapshot path

Check for an in-progress start only after the driver poll: the resource-version fence already rejects a poll that overlaps a start beginning earlier. Limit the durable-claim check to Starting sandboxes, drop the prune-path guard (pending operations already block pruning), restore the original watch-delay test, and cover the gap where only the local gate defers the sweep.

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>

---------

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
Signed-off-by: Shiju <shiju@nvidia.com>
Co-authored-by: Shiju <shiju@nvidia.com>
…der (ai-openshell#5777)

The Providers overview read as though profiles ship with the gateway. A new
gateway starts with an empty profile catalog, so every `provider create`
example on the page failed until the reader found the import step elsewhere.

Rewrite the overview as one walkthrough that starts from an empty gateway:
import an inline read-only GitHub REST profile, create a provider from it,
attach it to a sandbox and make an authenticated request, then update and
remove the profile. Link the repository's `providers/` directory, at the
matching release tag, for profiles for other services.

Signed-off-by: Kris Hicks <khicks@nvidia.com>
Comment on lines +98 to +100
"{} Created secret {}",
"✓".green().bold(),
secret_name(&secret)
Comment on lines +150 to +152
"{} Updated secret {}",
"✓".green().bold(),
secret_name(&secret)
}
println!("{}", "Secret:".cyan().bold());
println!();
println!(" {} {}", "Name:".dimmed(), secret_name(&secret));
println!();
println!(" {} {}", "Name:".dimmed(), secret_name(&secret));
if !secret.description.is_empty() {
println!(" {} {}", "Description:".dimmed(), secret.description);
Comment on lines +192 to +194
" {} deletion did not finish; rerun `openshell secret delete {}`",
"Deleting:".dimmed(),
secret_name(&secret)
Comment on lines +261 to +265
"{:<name_width$} {:<8} {:<20} {}",
secret_name(secret),
status(secret),
value_updated(secret),
refresh_endpoints(secret)
shiju-nv and others added 6 commits November 20, 2026 06:28
…i-openshell#5243)

* feat(tracing): show boundary connection time during sandbox startup

Signed-off-by: Shiju <shiju@nvidia.com>

* fix(tracing): report boundary connection status and attempts

Signed-off-by: Shiju <shiju@nvidia.com>

* fix(tracing): record boundary attempt count once

Recording the attempt count on every retry appends duplicate OTLP
attributes. A connection that succeeds on the third attempt exports
four entries for the same key. A long retry loop can consume the span
attribute budget before the final count is recorded.

Track attempts for the lifetime of the connection future and record
the count once when it ends, including on cancellation. Verify the
exported span with a loopback OTLP collector, since the existing
map-based test replaces earlier values and hides duplicates.

Signed-off-by: Kris Hicks <khicks@nvidia.com>

* fix(tracing): keep boundary startup waits in one span

Policy discovery can outlast the 30-second connection retry window
while the sandbox starts. Restarting the connection span at each window
adds ERROR spans to successful startups and splits the wait operators
need to measure.

Use the configured startup budget for the initial connection and keep
the 30-second window for reattachment. Let the caller choose that
budget on every transport so sharing a routed registration between
discovery and attach does not shorten the attach window.

Emit the attempt count only when the supervisor dials or invokes a
backend connector. Inbound transports wait for an authenticated stream
and cannot count the runtime’s dials. If the startup deadline cancels
the wait, the startup span records the failure.

Signed-off-by: Kris Hicks <khicks@nvidia.com>

---------

Signed-off-by: Shiju <shiju@nvidia.com>
Signed-off-by: Kris Hicks <khicks@nvidia.com>
Co-authored-by: Kris Hicks <khicks@nvidia.com>
…-io#186)

* CARRY: test(odh): allow existing image tests to run on Kata

Pass an explicitly selected, approved RuntimeClass to the existing ODH Helm deployment so sandbox pods use Kata during the standard test tiers. Document how to select and verify the class.

Signed-off-by: Jiri Petrlik <jpetrlik@redhat.com>

* CARRY: test(odh): manage approval for the selected Kata RuntimeClass

Temporarily approve the RuntimeClass configured for test sandbox pods
and restore its original label during cleanup, even when tests fail.
Reuse existing approval when present.

Document the required permissions and cover absent, empty, and
preapproved labels with mock tests.

Signed-off-by: Jiri Petrlik <jpetrlik@redhat.com>

---------

Signed-off-by: Jiri Petrlik <jpetrlik@redhat.com>
…r digest to 5e9a097 (#151)

Signed-off-by: konflux-internal-p02 <170854209+konflux-internal-p02[bot]@users.noreply.github.com>
Co-authored-by: konflux-internal-p02[bot] <170854209+konflux-internal-p02[bot]@users.noreply.github.com>
Signed-off-by: konflux-internal-p02 <170854209+konflux-internal-p02[bot]@users.noreply.github.com>
Co-authored-by: konflux-internal-p02[bot] <170854209+konflux-internal-p02[bot]@users.noreply.github.com>
konflux-internal-p02 Bot and others added 5 commits November 22, 2026 02:02
Signed-off-by: konflux-internal-p02 <170854209+konflux-internal-p02[bot]@users.noreply.github.com>
Co-authored-by: konflux-internal-p02[bot] <170854209+konflux-internal-p02[bot]@users.noreply.github.com>
Signed-off-by: konflux-internal-p02 <170854209+konflux-internal-p02[bot]@users.noreply.github.com>
Co-authored-by: konflux-internal-p02[bot] <170854209+konflux-internal-p02[bot]@users.noreply.github.com>
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
…tmaker/main/lock-file-maintenance

chore(deps): refresh rpm lockfiles
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.