Bug 1394900 - Docker instance of Fedora does not register to Spacewalk/Satellite 5
Summary: Docker instance of Fedora does not register to Spacewalk/Satellite 5
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rhn-client-tools
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1343435 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-14 16:37 UTC by Pavel Studeník
Modified: 2017-12-01 11:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-01 11:41:46 UTC
Type: Bug


Attachments (Terms of Use)

Description Pavel Studeník 2016-11-14 16:37:06 UTC
Description of problem:
I tried to register Fedora client in Docker to Spacewalk/Satellite, but registration failed due to missing installed packages.

1) at first I received:

>> rhnreg_ks --activationkey=1-xxx --force
Traceback (most recent call last):
  File "/usr/sbin/rhnreg_ks", line 37, in <module>
    from up2date_client import rhnreg
  File "/usr/share/rhn/up2date_client/rhnreg.py", line 12, in <module>
    import dbus
ImportError: No module named 'dbus'

missing package: python3-dbus (workaround - install this package)


2) after installation of python3-dbus:

>> rhnreg_ks --activationkey=1-xxx
An unexpected OS error occurred: [Errno 2] No such file or directory: '/usr/share/hwdata/pci.ids'

missing package: hwdata (workaround - install this package)


Version-Release number of selected component (if applicable):
rhn-client-tools-2.6.7-1.fc24.noarch

How reproducible:
on Fedora 24

Steps to Reproduce:
1. docker run -it fedora:24 /usr/bin/bash
2. rpm -Uvh http://yum.spacewalkproject.org/nightly-client/Fedora/24/x86_64/spacewalk-client-repo-2.5-3.fc24.noarch.rpm

3. sed s/enabled=0/enabled=1/g /etc/yum.repos.d/spacewalk-client-nightly.repo -i 
  sed s/enabled=1/enabled=0/g /etc/yum.repos.d/spacewalk-client.repo -i
4. dnf install rhn-client-tools rhn-check rhn-setup rhnsd m2crypto wget osad -y
5. rhnreg_ks --activationkey=1-xxx --force

Actual results:
Traceback due to missing packages.

Expected results:
Set correct dependencies to work in Docker by default.

Comment 1 Pavel Studeník 2017-01-24 13:54:01 UTC
Workaround is easy - install following packages:

>> dnf install -y hwdata python3-dbus m2crypto 

Inspired by https://github.com/Pajinek/docker-spacewalk-client/blob/master/Dockerfile

Comment 2 Pavel Studeník 2017-01-24 13:57:02 UTC
*** Bug 1343435 has been marked as a duplicate of this bug. ***

Comment 3 Fedora End Of Life 2017-11-16 19:39:32 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 4 Pavel Studeník 2017-12-01 11:32:05 UTC
# rhnreg_ks  --activationkey=1-pstudeni
Failed to connect to bus: No such file or directory
# echo $?
0

Verified on Fedora 27 - rhn-setup-2.7.15-1.fc27.noarch with warning, but it is not problem.


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