Bug 1145777 - realmd should try discovering via domainname
Summary: realmd should try discovering via domainname
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: realmd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sumit Bose
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-23 18:08 UTC by Stephen Gallagher
Modified: 2018-08-22 10:55 UTC (History)
5 users (show)

Fixed In Version: realmd-0.16.3-15.fc29
Clone Of:
Environment:
Last Closed: 2018-08-22 10:55:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Stephen Gallagher 2014-09-23 18:08:14 UTC
Description of problem:
When running 'realm discover -v', it tries only to get a default domain from DHCP and bails out if there is none. In this situation, reamld should try to use the configured domain name on the system ('hostname -d') to create the DNS lookup.

Not every environment will have DHCP configured to provide a default domain name (example: test environments in libvirt).

Version-Release number of selected component (if applicable):
realmd-0.15.1-4.fc21.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Install a Fedora 21 Server VM with libvirt/virt-manager
2. Log in as root
3. Set the machine's hostname to 'clientname.windows.domain.name'
3. Point /etc/resolv.conf at a Windows Active Directory server.
4. run 'realm discover -v'

Actual results:
 * No default domain received via DHCP

Expected results:
 * Resolving: _ldap._tcp.windows.domain.name


Additional info:

Comment 1 Adam Williamson 2014-10-23 01:03:38 UTC
I see this too. It makes testing realm enrolment via kickstart a bit of a pain. I guess I'll have to modify libvirt's DHCP configuration, or something.

Comment 2 Fedora End Of Life 2015-11-04 15:00:02 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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 3 Adam Williamson 2015-11-04 20:33:10 UTC
I can't see anything in upstream or downstream realmd changelogs (incl. upstream git commit log) to indicate this has been fixed.

Comment 4 Fedora Admin XMLRPC Client 2016-05-18 13:44:28 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.


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