Surfaced by #3341, where fixing the lite profile to correctly not install Chain/Result exposed a pre-existing reconciler issue.
What happens
The e2e test TestTektonConfigTestSuite/Test02_ChangeProfile walks the sequence default → lite → basic → all. With the lite-profile fix in #3341, the lite step deletes the TektonResult CR (correct behaviour). The next step (basic) then has to recreate it, and the test times out with the controller stuck reporting:
config devel False Components not in ready state: TektonResult reconcile again and proceed
CI run with the failing transition: https://github.com/tektoncd/operator/actions/runs/24321929589
Why it wasn't seen before
Before #3341 the lite profile silently installed Chain + Result alongside Pipelines (the bug #3341 fixes). The existing Result CR was therefore always present, so the lite → basic transition was effectively a no-op for Result and never exercised the (re)create path under those conditions. Once lite started actually deleting Result, the re-create on lite → basic started failing/looping.
Where to look
pkg/reconciler/kubernetes/tektoninstallerset and the TektonResult reconciler, around the path that goes from Result deleted → Result recreated and waited on for ready. The "reconcile again and proceed" message comes from the install-set readiness check.
Acceptance criteria
TestTektonConfigTestSuite/Test02_ChangeProfile runs the full default → lite → basic → all sequence to completion against #3341 (or its successor) without timing out.
cc @anithapriyanatarajan @khrm @savitaashture
Surfaced by #3341, where fixing the
liteprofile to correctly not install Chain/Result exposed a pre-existing reconciler issue.What happens
The e2e test
TestTektonConfigTestSuite/Test02_ChangeProfilewalks the sequencedefault → lite → basic → all. With the lite-profile fix in #3341, thelitestep deletes theTektonResultCR (correct behaviour). The next step (basic) then has to recreate it, and the test times out with the controller stuck reporting:CI run with the failing transition: https://github.com/tektoncd/operator/actions/runs/24321929589
Why it wasn't seen before
Before #3341 the
liteprofile silently installed Chain + Result alongside Pipelines (the bug #3341 fixes). The existing Result CR was therefore always present, so thelite → basictransition was effectively a no-op for Result and never exercised the (re)create path under those conditions. Oncelitestarted actually deleting Result, the re-create onlite → basicstarted failing/looping.Where to look
pkg/reconciler/kubernetes/tektoninstallersetand the TektonResult reconciler, around the path that goes fromResult deleted→Result recreated and waited on for ready. The "reconcile again and proceed" message comes from the install-set readiness check.Acceptance criteria
TestTektonConfigTestSuite/Test02_ChangeProfileruns the fulldefault → lite → basic → allsequence to completion against #3341 (or its successor) without timing out.cc @anithapriyanatarajan @khrm @savitaashture