Bug 1326930 - rhel-osp-director: deployment with sat6 fails with "No Satellite detected at https://FQDN/\n"
Summary: rhel-osp-director: deployment with sat6 fails with "No Satellite detected at ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: 8.0 (Liberty)
Assignee: Angus Thomas
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-13 19:13 UTC by Alexander Chuzhoy
Modified: 2016-04-13 20:50 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-13 20:50:26 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.