Bug 772715 - warning: Could not retrieve fact fqdn after aeolus-cleanup on F16
Summary: warning: Could not retrieve fact fqdn after aeolus-cleanup on F16
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-configure
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: John Eckersberg
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-09 18:25 UTC by Martin Kočí
Modified: 2012-02-22 23:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-12 21:03:29 UTC


Attachments (Terms of Use)

Description Martin Kočí 2012-01-09 18:25:20 UTC
Description of problem:
I don't know if that is related to aeolus project or puppet, but if I try run aeolus-cleanup and/or aeolus-configure I'm still gettig following error: 
[root@mkoci-f16 ~]# aeolus-cleanup
warning: Could not retrieve fact fqdn
notice: /Stage[main]/Aeolus::Conductor::Disabled/Rails::Drop::Db[drop_aeolus_database]/Exec[drop_rails_database]/returns: Couldn't drop conductor : #<PGError: FATAL:  password authentication failed for user "aeolus"
...
(Mon Jan 09 19:21:38 +0100 2012 Puppet (warning): Could not retrieve fact fqdn)
...

Version-Release number of selected component (if applicable):
# rpm -qa | grep 'aeolus\|imagefactory-\|oz-\|iwhd'
imagefactory-jeosconf-ec2-fedora-1.0.0rc1-1.fc16.noarch
rubygem-aeolus-cli-0.4.0-0.20120105171410git2c6b457.fc16.noarch
aeolus-conductor-0.9.0-0.20120105223209git5e068fe.fc16.noarch
iwhd-1.2-1.fc16.x86_64
aeolus-configure-2.6.0-0.20120105171403gitf0043e8.fc16.noarch
imagefactory-1.0.0rc1-1.fc16.noarch
rubygem-imagefactory-console-0.4.0-6.fc16.noarch
aeolus-conductor-daemons-0.9.0-0.20120105223209git5e068fe.fc16.noarch
rubygem-aeolus-image-0.4.0-0.20120105171419git8108b42.fc16.noarch
aeolus-all-0.9.0-0.20120105223209git5e068fe.fc16.noarch
aeolus-conductor-doc-0.9.0-0.20120105223209git5e068fe.fc16.noarch
imagefactory-jeosconf-ec2-rhel-1.0.0rc1-1.fc16.noarch
oz-0.8.0-0.20111219203204git5775e9d.fc16.noarch
puppet version is: 
# rpm -qa|grep puppet
puppet-2.6.12-1.fc16.noarch

How reproducible:
always on my F16 test server

Steps to Reproduce:
1. run aeolus-cleanup{aeolus-connfigure}

  
Actual results:
A warning

Expected results:
No warnings/errors

Additional info:
n/a

Comment 1 John Eckersberg 2012-01-12 21:03:29 UTC
This behavior is from puppet (or more specifically, facter).  The fqdn fact is pieced together from the hostname and domain facts.  The domain fact works like this (taken directly from the source):

# Resolution:
#   On UNIX (excluding Darwin), first try and use the hostname fact,
#   which uses the hostname system command, and then parse the output
#   of that.
#   Failing that it tries the dnsdomainname system command.
#   Failing that it uses /etc/resolv.conf and takes the domain from that, or as
#   a final resort, the search from that.
#   Otherwise returns nil.

You will probably also see messages like 'dnsdomainname: Unknown host', since facter just shells out to the dnsdomainname command.

If your host cannot determine it's domain using any of the methods above, then you will end up getting the fqdn warning.

The easiest workaround if you really want the warning to go away would be to add a domain entry in /etc/resolv.conf.

There's not much we can do in configure to suppress that since it comes directly from puppet, so I am going to go ahead and close this.


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