Bug 968109 - No A record created in domain when provisioning image based vm
Summary: No A record created in domain when provisioning image based vm
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-29 02:46 UTC by Sam Kottler
Modified: 2019-09-26 13:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-18 18:36:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sam Kottler 2013-05-29 02:46:58 UTC
Description of problem:
When I provision a new vm in ec2 and I choose a domain on my Foreman server no CNAME or A record is created. I see the following output, which doesn't indicate anything is happening with DNS locally. It would be great to get a CNAME pointing at the EC2 server name. Not sure why I need (or would be able) to select a domain if it's not going to set up a record.

If this ends up not being a bug I'd like to request as a feature that a CNAME be created.

new In Progress
completed - Settings up compute instance test2.ec2.devlab.redhat.com
completed - Acquiring IP address for test2.ec2.devlab.redhat.com
completed - Querying instance details for test2.ec2.devlab.redhat.com
completed - Preparing Post installation script for test2.ec2.devlab.redhat.com
running - Waiting for test2.ec2.devlab.redhat.com to come online
pending - Enable Certificate generation for test2.ec2.devlab.redhat.com
pending - Configuring instance test2.ec2.devlab.redhat.com via SSH

Additional info:
Fixed upstream in 022c4060d3e7a06519fcfe76f09d255877c15d85.

Comment 1 Mike McCune 2013-05-29 22:36:46 UTC
mass-triage since these are all POST/MODIFIED

Comment 2 Dominic Cleal 2013-09-18 18:36:49 UTC
Shipped in MDP1.


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