Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2255285 - Satellite-Capsule update warning message shows Scenario as failed.
Summary: Satellite-Capsule update warning message shows Scenario as failed.
Keywords:
Status: CLOSED DUPLICATE of bug 2254492
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.15.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-19 21:09 UTC by Prashant
Modified: 2023-12-21 14:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-12-21 14:25:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-22050 0 None None None 2023-12-19 21:11:36 UTC

Description Prashant 2023-12-19 21:09:50 UTC 
Description of problem:

Satellite-Capsule 6.15 update <packages-check-for-reboot> warning message shows Scenario [Checks after upgrading to Capsule 6.15.z] as failed.

Version-Release number of selected component (if applicable):

satellite-capsule-6.15.0

How reproducible:


Steps to Reproduce:
Try to update the Satellite-Capsule 6.15
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# satellite-maintain upgrade run --target-version 6.15.z
--------------------------------------------------------------------------------
Check if system needs reboot:                                         [WARNING]
Updating Subscription Management repositories.
Repository satellite-client-6-for-rhel-8-x86_64-rpms is listed more than once in the configuration
Repository rhel-8-for-x86_64-appstream-rpms is listed more than once in the configuration
Repository rhel-8-for-x86_64-baseos-rpms is listed more than once in the configuration
Core libraries or services have been updated since boot-up:
  * kernel

Reboot is required to fully utilize these updates.
More information: https://access.redhat.com/solutions/27943
--------------------------------------------------------------------------------
Scenario [Checks after upgrading to Capsule 6.15.z] failed.

The following steps ended up in warning state:

  [packages-check-for-reboot]

The steps in warning state itself might not mean there is an error,
but it should be reviewed to ensure the behavior is expected



--------------------------------------------------------------------------------
Upgrade finished.
=====


Actual results: Below message is confusing and need to re-run upgrade again:

~~~~
Scenario [Checks after upgrading to Capsule 6.15.z] failed.
~~~~


Expected results: Can we remove the below messages? we can --whitelist=packages-check-for-reboot.

~~~~
Scenario [Checks after upgrading to Capsule 6.15.z] failed.

The following steps ended up in warning state:

  [packages-check-for-reboot]

The steps in warning state itself might not mean there is an error,
but it should be reviewed to ensure the behavior is expected
~~~~~

Additional info:
Comment 1 Eric Helms 2023-12-21 14:25:08 UTC 

*** This bug has been marked as a duplicate of bug 2254492 ***
Note You need to log in before you can comment on or make changes to this bug.