Bug 1467764 - Update notice RHEA-2016:2827 (from rhui-rhel-7-server-dotnet-rhui-rpms) is broken, or a bad duplicate, skipping.
Update notice RHEA-2016:2827 (from rhui-rhel-7-server-dotnet-rhui-rpms) is br...
Status: CLOSED DUPLICATE of bug 1194915
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: yum (Show other bugs)
7.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Valentina Mukhamedzhanova
BaseOS QE Security Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-05 00:30 EDT by Johan Burati
Modified: 2017-07-11 05:13 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-07-11 05:13:52 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Johan Burati 2017-07-05 00:30:58 EDT
Description of problem:

Getting error messages when running 'yum check-update' from RHEL 7.3 VM on Azure.

How reproducible:
Every time

Steps to Reproduce:

sudo yum check-update

Actual results:

Update notice RHEA-2016:2827 (from rhui-rhel-7-server-dotnet-rhui-rpms) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the rhui-rhel-7-server-dotnet-rhui-rpms repository.
Update notice RHBA-2016:2044 (from rhui-rhel-7-server-dotnet-rhui-rpms) is broken, or a bad duplicate, skipping.
Update notice RHEA-2016:1312 (from rhui-rhel-7-server-dotnet-rhui-rpms) is broken, or a bad duplicate, skipping.
Update notice RHBA-2016:2826 (from rhui-rhel-7-server-dotnet-rhui-source-rpms) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the rhui-rhel-7-server-dotnet-rhui-source-rpms repository.
Comment 2 Karel Srot 2017-07-11 05:13:52 EDT
Will be fixed in rhel-7.4

*** This bug has been marked as a duplicate of bug 1194915 ***

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