Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-25795 Capsule upgrade fails in container labels migration post-upgrade task
  3. SAT-25797

[DEV] Capsule upgrade fails in container labels migration post-upgrade task

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Capsule - Content, Upgrades
    • Sprint 134, Sprint 135, Sprint 136, Sprint 137, Sprint 138, Sprint 139, Sprint 140, Sprint 141

      Description of problem:

      When upgrading Capsule from 6.15.1 to 6.16.0 the upgrade fails in post-upgrade task.

       

      How reproducible:

      always

       

      Is this issue a regression from an earlier version:

      yes

       

      Steps to Reproduce:

      1. Set up SAT + CAPS, sync a docker repo on both.

      2. Upgrade the SAT to 6.16.0

      3. Upgrade the CAPS to 6.16.0

       

      Actual behavior:
      Capsule upgrade fails since there is no foreman-rake there.

      --------------------------------------------------------------------------------
      Initialize and expose container image metadata in the pulpcore db: 
      \ Adding image metadata to katello. You can continue using the system normally while the task runs in the background.
                                                                            [FAIL]
      Failed executing foreman-rake katello:import_container_manifest_labels, exit status 127:
       sh: foreman-rake: command not found
      --------------------------------------------------------------------------------
      Scenario [Checks after upgrading to Capsule 6.16] failed.

       

      Expected behavior:
      Upgrade should succeed.

       

      Business Impact / Additional info:

      Blocks upgrade.

      DEV Tracker for https://issues.redhat.com/browse/SAT-25795

            rhn-engineering-sajha Samir Jha
            rhn-engineering-paji Partha Aji
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: