Bug 1212556

Summary: The system release info get from 'utsname' is different from the host
Product: [Fedora] Fedora Reporter: Hu Zhang <huzhan>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 22CC: leiwang, mbooth, ptoscano, rjones, virt-maint, wshi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 20:52:58 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:

Description Hu Zhang 2015-04-16 15:58:09 UTC
Description of problem:
The appliance release info get from 'utsname' is different form the host.

Version-Release number of selected component (if applicable):
kernel-4.0.0-0.rc1.git0.1.fc22.x86_64
libguestfs-1.29.33-1.fc22.x86_64

How reproducible:
Always

Steps to Reproduce:
1. In guestfish
><fs> utsname

2. On the host,
# uname -a 
Linux dhcp-11-44.nay.redhat.com 4.0.0-0.rc1.git0.1.fc22.x86_64 #1 SMP Mon Feb 23 21:15:25 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Actual results:
The appliance release info is 4.0.0-0.rc5.git4.1.fc22.x86_64.
On host, it's 4.0.0-0.rc1.git0.1.fc22.x86_64.

Expected results:
The release info should be same.

Additional info:

Comment 1 Richard W.M. Jones 2015-04-16 16:01:34 UTC
You wouldn't always expect them to be the same, or even to be
predictable.

Supermin picks up the latest kernel from /boot to run the appliance.
That might not be the same kernel as is running on the host (eg.
if you yum updated the kernel, but didn't reboot).

Comment 3 Fedora End Of Life 2016-07-19 20:52:58 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.