Bug 1313288 - Error: Could not run: Could not retrieve facts for <host>: no address for <host>
Error: Could not run: Could not retrieve facts for <host>: no address for <host>
Status: CLOSED NOTABUG
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
high Severity unspecified
: async
: 7.0 (Kilo)
Assigned To: Angus Thomas
Arik Chernetsky
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-01 05:31 EST by Eduard Barrera
Modified: 2016-03-04 11:29 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-03-04 11:18:23 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Eduard Barrera 2016-03-01 05:31:33 EST
Description of problem:

When deploying the overcloud we are facing the following error:


[stack@bb1-osd01 ~]$ heat deployment-show 41a344f5-350a-4178-8f69-f2be378f7538
{
  "status": "FAILED", 
  "server_id": "20f939f8-6560-4577-9b0a-ffb61f8a606d", 
  "config_id": "1ce38010-e207-4c3d-9926-43db569599c7", 
  "output_values": {
    "deploy_stdout": "", 
    "deploy_stderr": "\u001b[1;31mWarning: Scope(Class[Keystone]): Execution of db_sync does not depend on $enabled anymore. Please use sync_db instead.\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Glance::Registry]): Execution of db_sync does not depend on $manage_service or $enabled anymore. Please use sync_db instead.\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::compute::vncproxy_host'; class ::nova::compute has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::compute::vncproxy_protocol'; class ::nova::compute has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::compute::vncproxy_port'; class ::nova::compute has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::compute::vncproxy_path'; class ::nova::compute has not been evaluated\u001b[0m\n\u001b[1;31mError: nova_admin_password must be set. at /etc/puppet/modules/neutron/manifests/server/notifications.pp:80 on node bb1-ctrl0.adm.cacc.ch\u001b[0m\n\u001b[1;31mError: nova_admin_password must be set. at /etc/puppet/modules/neutron/manifests/server/notifications.pp:80 on node bb1-ctrl0.adm.cacc.ch\u001b[0m\n", 
    "deploy_status_code": 1
  }, 

"""
Error: nova_admin_password must be set. at /etc/puppet/modules/neutron/manifests/server/notifications.pp:80
"""


- I think we are facing the following bug but it's  

  https://bugzilla.redhat.com/show_bug.cgi?id=1292182


The bug its reported against OSP 8 but seems it is also applicable to OSP7. It also not clear to me if there is a workaround there.


Version-Release number of selected component (if applicable):

instack-0.0.7-2.el7ost.noarch
instack-undercloud-2.1.2-36.el7ost.noarch
openstack-puppet-modules-2015.1.8-32.el7ost.noarch
openstack-tripleo-0.0.7-0.1.1664e566.el7ost.noarch
openstack-tripleo-common-0.0.1.dev6-5.git49b57eb.el7ost.noarch
openstack-tripleo-heat-templates-0.8.6-94.el7ost.noarch
openstack-tripleo-image-elements-0.9.6-10.el7ost.noarch
openstack-tripleo-puppet-elements-0.0.1-5.el7ost.noarch
python-rdomanager-oscplugin-0.0.10-22.el7ost.noarch



How reproducible:
always

Steps to Reproduce:
1. Deploy an overcloud
2.
3.

Actual results:
Error: nova_admin_password must be set. at /etc/puppet/modules/neutron/manifests/server/notifications.pp:80
"""


Expected results:
Installation finish successfully


Additional info:

attaching the templates used by customer
Comment 12 Dave Maley 2016-03-04 11:18:23 EST
customer has confirmed the suggested change worked, closing notabug

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