Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 903075

Summary:

reading hardware memory information failed for 3.X kernels

Product:

[Community] Spacewalk

Reporter:

Peter Hudec <peter>

Component:

Clients

Assignee:

Michael Mráka <mmraka>

Status:

CLOSED EOL

QA Contact:

Red Hat Satellite QA List <satqe-list>

Severity:

low

Docs Contact:

Priority:

unspecified

Version:

1.7

CC:

mmraka

Target Milestone:

---

Target Release:

---

Hardware:

All

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2019-07-18 09:08:06 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
small fix which solved my problem	none

Description Peter Hudec 2013-01-23 05:10:56 UTC

For 3.X kernel the up2date client did not pass any information to the spacewalk server.

Comment 1 Peter Hudec 2013-01-23 05:12:28 UTC

The problem is in

file: client/rhel/rhn-client-tools/src/up2date_client/hardware.py
function: read_memory

For 3.X there is no "IF" statement.

Comment 2 Peter Hudec 2013-01-23 05:13:26 UTC

Created attachment 685651 [details]
small fix which solved my problem

Comment 3 Milan Zázrivec 2013-02-01 10:31:29 UTC

# python hardware.py
> /usr/share/rhn/up2date_client/hardware.py(348)read_memory()
-> if kernel[:3] >= "2.6":
(Pdb) print kernel[:3]
3.7
(Pdb) print kernel[:3] >= "2.6"
True
(Pdb) 

The patch should not be needed for 3.X kernels really, since we should
end up in

    if kernel[:3] >= "2.6":
        return read_memory_2_6()

anyway.

I'm more wondering what that

    kernel[:3]

returns in your case?

Are you seeing this on a Fedora / CentOS / RHEL / Debian / SuSE system?

Comment 4 Peter Hudec 2013-02-06 07:32:18 UTC

We are using the Debian based systems and the packages from the 
https://fedorahosted.org/spacewalk/wiki/RegisteringClients#Debian


>>> un = os.uname()
>>> kernel = un[2]
>>> kernel
'3.5.0-21-generic'
>>> print kernel[:3] >= 2.6
True
This code is woring fine, but in my hardware.py was this code originally

def read_memory():
    un = os.uname()
    kernel = un[2]
    if kernel[:3] == "2.6":
        return read_memory_2_6()
    if kernel[:3] == "2.4":
        return read_memory_2_4()

Comment 5 Milan Zázrivec 2013-02-06 12:59:02 UTC

(In reply to comment #4)
> We are using the Debian based systems and the packages from the 
> https://fedorahosted.org/spacewalk/wiki/RegisteringClients#Debian

OK, the instructions at the page above were updated to reflect current
status of debian client packages. In short, most of the packages you need
are already in Debian, although current builds still contain the problem
described in this report. We still need to hash this out with the package
maintainer and get more recent packages into the distribution.

Comment 6 Michael Mráka 2019-07-18 09:08:06 UTC

Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.