Bug 1033243 - False Positive Warning when executing foreman_client.sh
Summary: False Positive Warning when executing foreman_client.sh
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-foreman-installer
Version: 4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 4.0
Assignee: Jason Guiditta
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks: 1034998 RHOS-Foreman-Deployability
TreeView+ depends on / blocked
 
Reported: 2013-11-21 18:49 UTC by james labocki
Modified: 2013-12-20 00:38 UTC (History)
9 users (show)

Fixed In Version: openstack-foreman-installer-0.0.23-1.el6ost
Doc Type: Enhancement
Doc Text:
An error message that may occur when 'foreman_client.sh' is executed has been amended for clarity. A subsequent message will now follow indicating that the error message can be ignored under a specific circumstance.
Clone Of:
: 1034998 (view as bug list)
Environment:
Last Closed: 2013-12-20 00:38:15 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1859 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2013-12-21 00:01:48 UTC

Description james labocki 2013-11-21 18:49:08 UTC
When executing foreman_client.sh

Warning: Unable to fetch my node definition, but the agent run will continue:

    Warning: Error 400 on SERVER: Failed to find osp2 via exec: Execution of '/etc/puppet/node.rb osp2' returned 1:

I was told this is safe to ignore. Can we suppress the error, tell the user it's safe to ignore, or add notes to documentation?

Comment 2 Dominic Cleal 2013-11-22 10:18:13 UTC
We can't suppress the error without suppressing cases when we do need to know about its failure, nor can I think of a good way of making the message more user friendly.

I'd suggest adding an "echo" to the foreman_client.sh script in o-f-i to let the user know this will happen, and/or to the documentation.

Comment 3 Jason Guiditta 2013-11-26 20:36:21 UTC
Patch posted:
https://github.com/redhat-openstack/astapor/pull/58

I also added a clone of this to docs so it can hopefully get into the guide as well.

Comment 4 Jason Guiditta 2013-12-02 21:28:47 UTC
This is merged upstream, will flip to modified once it goes into an rpm

Comment 7 Crag Wolfe 2013-12-18 19:45:18 UTC
Verified that running foreman_client.sh displays the following output as the last thing it shows:

NOTE: If you saw an error above including:
'Warning: 400 on SERVER: Failed to find....'
This may be ignored, as it means this host was unknown to Foreman at the start
of the Puppet run.

Comment 10 errata-xmlrpc 2013-12-20 00:38:15 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1859.html


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