Bug 1325456 - Satellite 5.6 client registration and package updates/installs tracebacks
Summary: Satellite 5.6 client registration and package updates/installs tracebacks
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf-plugin-spacewalk
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-08 21:03 UTC by Paul Gozart
Modified: 2019-10-10 11:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 19:53:02 UTC
Type: Bug


Attachments (Terms of Use)
attachment from sfdc 01612369 (9.77 KB, text/plain)
2016-04-08 21:03 UTC, Paul Gozart
no flags Details

Description Paul Gozart 2016-04-08 21:03:36 UTC
Created attachment 1145265 [details]
attachment from sfdc 01612369

Description of problem:
Satellite 5.6 registration of Fedora 23 host and/or package updates or installs on F23 results in timeout tracebacks presumably trying to update the RHN profile.


Version-Release number of selected component (if applicable):
Fedora 23 and Satellite 5.6


How reproducible:
register a Fedora 23 client and do dnf update <rpm> or dnf install <rpm>
    The client updates are eventually reflected on the RHN profile. It can take up to an hour though.


Steps to Reproduce:
1.  Register F23 with Sat 5.6
2.  dnf update <rpm> OR dnf install <rpm>


Actual results:
See attachment for tracebacks


Expected results:
Expected successful updates/installs of packages


Additional info:
Setting severity of high because this issue is present in customer's production environment.

Comment 5 Michael Mráka 2016-04-11 08:31:08 UTC
> Steps to Reproduce:
> 1.  Register F23 with Sat 5.6
> 2.  dnf update <rpm> OR dnf install <rpm>

Are they able to reproduce it against current Spacewalk (2.4)?

Comment 6 Paul Gozart 2016-05-06 21:02:31 UTC
This was a high priority issue for my customer but they haven't seen the problem in over two weeks now so they had me close the case.  I'm not sure if they would be willing to test Spacewalk or not.  This is no longer a priority for them.

Comment 7 Fedora End Of Life 2016-11-25 07:18:23 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2016-12-20 19:53:02 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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