Red Hat Bugzilla – Bug 1131659
Cannot create host if the domain name starts with "."
Last modified: 2017-02-23 16:04:02 EST
Description of problem: Cannot create host if the domain name starts with "." Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a new domain starting with "." (.mydomain.com) 2. Try to create a new host using the domain 3. webUI says invalid name Actual results: The webUI says the system name is invalid Expected results: The webUI should parse if the domain name starts with "."
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Created redmine issue http://projects.theforeman.org/issues/7164 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/7164 has been closed ------------- Ori Rabin Applied in changeset commit:4717b0ea52a6b43c84e9ffef28863934b546010c.
One leading "." is now stripped from domain. *** This bug is verified in upstream. This fix should eventually land in future downstream builds *** Version Tested: RHEL 66 / RHEL 7 foreman-ovirt-1.8.0-0.develop.201412111740git287d974.el6.noarch qe-foreman-rhel66.usersys.redhat.com-puppet-client-1.0-1.noarch foreman-gce-1.8.0-0.develop.201412111740git287d974.el6.noarch ruby193-rubygem-foreman-tasks-0.6.10-2.el6.noarch rubygem-hammer_cli_foreman-0.1.4-1.201412111235git2131f5d.el6.noarch foreman-release-1.8.0-0.develop.201412111740git287d974.el6.noarch qe-foreman-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch qe-foreman-rhel66.usersys.redhat.com-qpid-client-cert-1.0-1.noarch ruby193-rubygem-foreman_docker-0.2.0-2.el6.noarch ruby193-rubygem-foreman_discovery-1.4.1-1.el6.noarch ruby193-rubygem-foreman_bootdisk-4.0.2-1.el6.noarch foreman-libvirt-1.8.0-0.develop.201412111740git287d974.el6.noarch qe-foreman-rhel66.usersys.redhat.com-apache-1.0-1.noarch qe-foreman-rhel66.usersys.redhat.com-parent-cert-1.0-1.noarch foreman-1.8.0-0.develop.201412111740git287d974.el6.noarch foreman-vmware-1.8.0-0.develop.201412111740git287d974.el6.noarch foreman-selinux-1.8.0-0.develop.201411281557gitf4a857f.el6.noarch foreman-proxy-1.8.0-0.develop.201412111700gita7c8c34.el6.noarch foreman-postgresql-1.8.0-0.develop.201412111740git287d974.el6.noarch qe-foreman-rhel66.usersys.redhat.com-foreman-proxy-1.0-1.noarch qe-foreman-rhel66.usersys.redhat.com-qpid-broker-1.0-1.noarch katello-ca-consumer-qe-foreman-rhel66.usersys.redhat.com-1.0-1.noarch foreman-compute-1.8.0-0.develop.201412111740git287d974.el6.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410gitc96619d.git.0.37f3704.el6.noarch
This bug is slated to be released with Satellite 6.1.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1592