Bug 1326930

Summary: rhel-osp-director: deployment with sat6 fails with "No Satellite detected at https://FQDN/\n"
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: rhosp-directorAssignee: Angus Thomas <athomas>
Status: CLOSED NOTABUG QA Contact: Arik Chernetsky <achernet>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: dbecker, jslagle, mburns, morazi, rhel-osp-director-maint, sasha
Target Milestone: ga   
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-13 20:50:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Alexander Chuzhoy 2016-04-13 19:13:04 UTC 
rhel-osp-director: deployment with sat6 fails with "No Satellite detected at https://FQDN/\n"

Environment:
openstack-tripleo-heat-templates-kilo-0.8.14-7.el7ost.noarch
openstack-puppet-modules-7.0.17-1.el7ost.noarch
instack-undercloud-2.2.7-4.el7ost.noarch
openstack-tripleo-heat-templates-0.8.14-7.el7ost.noarch


Steps to reproduce:
Try to deploy with this command:

openstack overcloud deploy --templates --control-scale 3 --compute-scale 1 --ceph-storage-scale 1   --neutron-network-type vxlan --neutron-tunnel-types vxlan  --ntp-server 10.5.26.10 --timeout 90 -e /usr/share/openstack-tripleo-heat-templates/environments/storage-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e network-environment.yaml --rhel-reg --reg-method satellite --reg-sat-url http://FQDN/ --reg-activation-key <KEY> --reg-org <ORG>

Result:

  "output_values": {
    "deploy_stdout": "No Satellite detected at https://FQDN/\n",
    "deploy_stderr": "",
    "deploy_status_code": 1
  },


Expected result:

Successful deployment.
Comment 2 James Slagle 2016-04-13 19:27:24 UTC 
does FQDN resolve to a satellite hostname in your environment? if not, it is expected to fail exactly as you have shown.

if FQDN isn't what you're actually testing with, please provide the exact deployment command used, and the exact error.
Comment 3 Alexander Chuzhoy 2016-04-13 20:50:26 UTC 
Had an issue with my setup, affecting name resolution on some of the OC nodes.