Bug 2168414 - The customer can't see the .686 errata package to be installed via webUI. However, in the CH, they can see both version getting updated
Summary: The customer can't see the .686 errata package to be installed via webUI. How...
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.11.5
Hardware: All
OS: All
medium
medium
Target Milestone: 6.14.0
Assignee: Lucy Fu
QA Contact: Sam Bible
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-08 23:19 UTC by Waldirio M Pinheiro
Modified: 2023-08-03 14:45 UTC (History)
7 users (show)

Fixed In Version: rubygem-katello-4.9.0.8-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2211956 (view as bug list)
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36100 0 Normal Closed Package upgradable versions are not set correctly based on architecture 2023-05-30 09:28:21 UTC
Red Hat Issue Tracker SAT-18032 0 None None None 2023-06-01 14:38:02 UTC

Description Waldirio M Pinheiro 2023-02-08 23:19:53 UTC
Description of problem:
When the customer check via webUI, only the x86_64 version it's available to update. However, when doing the update via content host, the customer can see both versions, .686 and also .x86_64.

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

How reproducible:
100%

Steps to Reproduce:
1. Install satellite, sync repos
2. Register CH in older version, and install some packages in .686 and .x86_64. (systemd-libs, for example) from media
3. Satellite now should be able to present new errata to be applied

Actual results:
The customer can see only systemd-libs-xxx.x86_64

Expected results:
The customer would like to see both versions, systemd-libs-xxx.x86_64 and  systemd-libs-xxx.i686

Additional info:

Comment 6 Jeremy Lenz 2023-03-17 20:46:16 UTC
Connecting redmine issue https://projects.theforeman.org/issues/36100 from this bug

Comment 7 Bryan Kearney 2023-03-22 16:03:14 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36100 has been resolved.

Comment 8 Bryan Kearney 2023-03-22 16:03:32 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36100 has been resolved.

Comment 9 Sam Bible 2023-06-26 19:54:19 UTC
Failing this BZ, as the root cause of this is the same as the 6.13.2 version, https://bugzilla.redhat.com/show_bug.cgi?id=2211956 - and that hasn't been resolved.

Comment 12 Sam Bible 2023-08-03 14:45:44 UTC
Version-Release number of selected component (if applicable):
6.14 - Snap 10

Steps to Reproduce:
1. Sync RHEL8 Appstream and RHEL8 BaseOS repos to Satellite
2. Register a Host with Satellite
3. Install systemd-libs.i686 and systemd-libs.x86_64 on the Host
4. Downgrade both packages on the host using 'yum downgrade <package_name>'
5. Compare the results of running 'yum update systemd-libs' on the host with what Satellite reports in the Upgradable view under the Host's packages.


Actual results:
Both packages are marked for update on the host, and both are marked as upgradeable on Satellite.

Expected results:
Both Versions should correctly be marked for update.


Note You need to log in before you can comment on or make changes to this bug.