Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-76352

LCA 4.17 seedgen reports error in LCA pod

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Critical
    • None
    • x86_64
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-75923. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-75895. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-73772. The following is the description of the original issue:
      —

      Description of Problem

      • Attempting to generate a seed image of a spoke running OCP 4.17 with LCA 4.17 operator fails with the following message:
      Seed generation failed: imager container status check failed: unable to parse podman inspect command output: invalid character 'i' in literal true (expecting 'r')

      Additional Info

      • must-gather and other info to be attached in a comment when available.

      pod log:

      2026-01-13T21:06:19Z	ERROR	controllers.SeedGenerator	Seed generation failed	{"error": "imager container status check failed: unable to parse podman inspect command output: invalid character 'i' in literal true (expecting 'r')"}
github.com/openshift-kni/lifecycle-agent/controllers.(*SeedGeneratorReconciler).Reconcile
	/opt/app-root/controllers/seedgen_controller.go:1014
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
	/opt/app-root/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:119
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/opt/app-root/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:316
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/opt/app-root/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:266
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/opt/app-root/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:227
2026-01-13T21:06:19Z	INFO	controllers.SeedGenerator	Finish reconciling SeedGen	{"name": {"name":"seedimage"}, "requeueRightAway": false}
2026-01-13T21:06:19Z	INFO	controllers.ImageBasedUpgrade	Start reconciling IBU	{"name": {"name":"upgrade"}}
2026-01-13T21:06:19Z	INFO	controllers.ImageBasedUpgrade	Loaded IBU	{"name": {"name":"upgrade"}, "version": "29236", "desired stage": "Idle"}
INFO[0000] Executing /usr/bin/env with args [-- rpm-ostree status --json] 
2026-01-13T21:06:19Z	INFO	controllers.ImageBasedUpgrade	Finish reconciling IBU	{"name": {"name":"upgrade"}, "requeueRightAway": false}

      LCA image version:

              "lifecycle-agent": {
            "bundle": "registry-proxy.engineering.redhat.com/rh-osbs/openshift4-lifecycle-agent-operator-bundle-container-rhel9@sha256:3b02c64084b38f048a4b3dd39a202a77a27dcef7e75a2f2bcf2e224138c8846d",
            "fbc": "quay.io/redhat-user-workloads/telco-5g-tenant/lifecycle-agent-fbc-4-17@sha256:f4dafb9e1f91e6237e12dd292f934652adb37c2e75f85fba69ddca6a4edeb181"
        }

    "Name": "registry.stage.redhat.io/openshift4/lifecycle-agent-rhel9-operator",
    "Digest": "sha256:519c8047a552ffca80a80c6262b819e05a4aa41ad311b3f17f7ddae8e6a050ca",

      Problem Reproduction

      • Deploy spoke with OCP 4.17 and LCA 4.17 operator appropriately for seed genaration
      • Attempt to to create a seed image from the spoke
      • monitor the LCA pod log

      Reproducibility

      • Always

      Prerequisites/Environment

      • This was found with a spoke setup with RAN DU profile

      Steps to Reproduce

      • See Problem Reproduction

      Expected Results

      • seed image generates successfully

      Actual Results

      • seed image generation fails with error message above

      Problem Analysis

      • <Completed by engineering team as part of the triage/refinement process>

      Root Cause

      • <What is the root cause of the problem? Or, why is it not a bug?>

      Workaround (If Possible)

      • <Are there any workarounds we can provide to the customers?>

      Fix Approaches

      • <If we decide to fix this bug, how will we do it?>

      Acceptance Criteria

      • ...

      Definition of Done

      • Code Complete:
        • All code has been written, reviewed, and approved.
      • Tested:
        • Unit tests have been written and passed.
        • Ensure code coverage is not reduced with the changes.
        • Integration tests have been automated.
        • System tests have been conducted, and all critical bugs have been fixed.
        • Tested and merged on OpenShift either upstream or downstream on a local build.
      • Documentation:
        • User documentation or release notes have been written (if applicable).
      • Build:
        • Code has been successfully built and integrated into the main repository / project.
        • Midstream changes (if applicable) are done, reviewed, approved and merged.
      • Review:
        • Code has been peer-reviewed and meets coding standards.
        • All acceptance criteria defined in the user story have been met.
        • Tested by reviewer on OpenShift.
      • Deployment:
        • The feature has been deployed on OpenShift cluster for testing.

              jche@redhat.com Jun Chen
              rhn-support-dgonyier Dwaine Gonyier
              Dwaine Gonyier, Yang Liu
              None
              Dwaine Gonyier Dwaine Gonyier
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: