Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,69 @@
build_root:
from_repository: true
images:
items:
- dockerfile_path: Dockerfile.rhel
to: cluster-version-operator
promotion:
to:
- disabled: true
name: "5.0"
namespace: ocp
releases:
initial:
integration:
name: "5.0"
namespace: ocp
latest:
integration:
include_built_images: true
name: "5.0"
namespace: ocp
resources:
'*':
requests:
cpu: 100m
memory: 200Mi
tests:
- as: e2e-gcp-compact-install
interval: 168h
steps:
cluster_profile: gcp-qe
env:
CUSTOM_OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE: registry.build06.ci.openshift.org/ci-ln-bi25fn2/release:latest
workflow: cucushift-installer-rehearse-gcp-ipi-compact
Comment on lines +31 to +34

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🌐 Web query:

How long are OpenShift CI build farm ci-ln- ephemeral namespaces retained before garbage collection?

💡 Result:

In the OpenShift CI build farm, ephemeral namespaces—which typically follow the naming pattern ci-op-* (as referenced in official documentation [1][2])—are automatically garbage-collected one hour after the job finishes executing [1][2]. If you are referring to namespaces managed by the ephemeral-namespace workflow (which reserves namespaces in a pool), the reservation duration is configurable and defaults to 1 hour, though it can be set to values ranging from 30 minutes to 14 days [3][4]. For more generalized namespace lifecycle management in the OpenShift CI infrastructure, the ci-ns-ttl-controller is used to manage both hard and soft Time-To-Live (TTL) values, which are configurable via namespace annotations [5]. - A hard TTL (annotation: ci.openshift.io/ttl.hard) deletes the namespace after a specific duration following its creation [5]. - A soft TTL (annotation: ci.openshift.io/ttl.soft) deletes the namespace after a duration of inactivity, defined as the time since the last active marker or pod termination, provided no other pods are running or pending [5].

Citations:


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== File context =="
sed -n '1,120p' ci-operator/config/openshift/cluster-version-operator/openshift-cluster-version-operator-release-5.0__periodics.yaml

echo
echo "== Search for this exact pull spec / namespace pattern =="
rg -n "ci-ln-3qfdxwk|ci-ln-|CUSTOM_OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE" ci-operator core-services services cluster projects tools -S

echo
echo "== Search CI docs references in repo =="
rg -n "ci-ln-|build farm|garbage-collected|ephemeral namespace|registry.build10.ci.openshift.org" -S .

Repository: openshift/release

Length of output: 19647


Recurring periodic uses an ephemeral build-farm payload. CUSTOM_OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE points to registry.build10.ci.openshift.org/ci-ln-3qfdxwk/release:latest; once that ci-ln-* namespace is garbage-collected, this tag disappears, so the weekly job will go stale. Replace it with a stable release image or remove the override if this is only meant for a one-off comparison.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/cluster-version-operator/openshift-cluster-version-operator-release-5.0__periodics.yaml`
around lines 31 - 34, The periodic job is pinned to an ephemeral ci-ln-* release
image override, which will disappear after garbage collection and make the
workflow stale. Update the periodic config for the
cucushift-installer-rehearse-gcp-ipi-compact job to use a stable release image
reference, or remove CUSTOM_OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE entirely if
it is only intended for a one-time comparison, so the recurring job does not
depend on a transient payload.

- as: e2e-gcp-compact-install-techpreview
interval: 168h
steps:
cluster_profile: gcp-qe
env:
CUSTOM_OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE: registry.build10.ci.openshift.org/ci-ln-c69vs5k/release:latest
FEATURE_SET: TechPreviewNoUpgrade
workflow: cucushift-installer-rehearse-gcp-ipi-compact
- as: e2e-gcp-compact-install-techpreview-baselinecap
interval: 168h
steps:
cluster_profile: gcp-qe
env:
ADDITIONAL_ENABLED_CAPABILITIES: ClusterAPI CompatibilityRequirements
BASELINE_CAPABILITY_SET: vCurrent
CUSTOM_OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE: registry.build10.ci.openshift.org/ci-ln-nmhm4j2/release:latest
FEATURE_SET: TechPreviewNoUpgrade
workflow: cucushift-installer-rehearse-gcp-ipi-compact
- as: e2e-gcp-compact-install-withnightly
interval: 168h
steps:
cluster_profile: gcp-qe
workflow: cucushift-installer-rehearse-gcp-ipi-compact
- as: e2e-gcp-compact-install-withnightly-techpreview
interval: 168h
steps:
cluster_profile: gcp-qe
env:
FEATURE_SET: TechPreviewNoUpgrade
workflow: cucushift-installer-rehearse-gcp-ipi-compact
zz_generated_metadata:
branch: release-5.0
org: openshift
repo: cluster-version-operator
variant: periodics
Loading