Bug #2325
closed
No A record created in domain when provisioning an ec2 vm
Description
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
Updated by Anonymous almost 12 years ago
broken by:
https://github.com/theforeman/foreman/commit/8838eb42a2a292f50126966d3fa768edad3a237a
app/models/orchestration/dns.rb
- !domain.nil? and !domain.proxy.nil? and managed?
+ name.present? and ip.present? and !domain.nil? and !domain.proxy.nil? and managed?
Reverting that change causes DNS records to get created for ec2 hosts again.
Updated by Dominic Cleal almost 12 years ago
- Category set to DNS
- Target version set to 1.2.0
Updated by Ohad Levy over 11 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset 3b6d152746d63444ce0ae2044cec4cbb8f224882.