Bug 831685 - Guest has predictable hostname
Guest has predictable hostname
Product: Fedora
Classification: Fedora
Component: gnome-boxes (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Christophe Fergeau
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-06-13 10:52 EDT by David Zeuthen
Modified: 2013-07-31 18:07 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-31 18:07:41 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Zeuthen 2012-06-13 10:52:54 EDT
After using "Express Install" for installing F17 x86_64, the guest has hostname "(none)" and the VG is named VolGroup00 and the LVs are LogVol00 and LogVol01.

It is a bad idea to use generic names like that, in particular LVM has had problems in the past if you are combining PVs with identically named VGs and LVs (mostly fixed now, I think).

Suggest to autogenerate a hostname (UUID or something based on the hypervisor hostname?) and use the standard vg-<hostname>, lv-root / lv-swap for naming LVM. Alternatively, ask the user for the hostname if you can make it fit into the design [1]

[1] : I do agree that asking the user to name a machine, virtual or otherwise, is asking too much... so you may not want to trouble the user with it
Comment 1 Christophe Fergeau 2012-06-13 11:24:10 EDT
Filed upstream at https://bugzilla.gnome.org/show_bug.cgi?id=678030
Comment 2 Zeeshan Ali 2012-06-13 12:04:27 EDT
(In reply to comment #0)
> After using "Express Install" for installing F17 x86_64, the guest has
> hostname "(none)"

This part has been fixed in git master already and hopefully the changes will be release in next 3.4 releaase as well.
Comment 4 Fedora End Of Life 2013-07-03 17:12:52 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 5 Fedora End Of Life 2013-07-31 18:07:57 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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.