Bug 1269182 - hosted-engine accepts FQDNs with underscore while the engine correctly fails on that
Summary: hosted-engine accepts FQDNs with underscore while the engine correctly fails ...
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: General
Version: 1.2.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-3.6.1
: 1.3.1
Assignee: Rafael Martins
QA Contact: Nikolai Sednev
Depends On: 1221176
Blocks: 1284979
TreeView+ depends on / blocked
Reported: 2015-10-06 14:35 UTC by Sandro Bonazzola
Modified: 2016-02-17 07:39 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
"hosted-engine --deploy" used to accept FQDNs with underscores, that are invalid and were already refused by "engine-setup". "hosted-engine --deploy" now refuses FQDNs with undescores as well.
Clone Of: 1221176
Last Closed: 2016-02-17 07:39:18 UTC
oVirt Team: Integration
rule-engine: ovirt-3.6.z+
sherold: planning_ack+
sbonazzo: devel_ack+
istein: testing_ack+

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
oVirt gerrit 46823 0 None None None Never
oVirt gerrit 46986 0 ovirt-hosted-engine-setup-1.3 MERGED packaging: setup: do not accept '_' character in FQDN Never
oVirt gerrit 46987 0 None None None Never
oVirt gerrit 47784 0 ovirt-hosted-engine-setup-1.3 MERGED packaging: setup: validate full fqdn Never

Description Sandro Bonazzola 2015-10-06 14:35:13 UTC
+++ This bug was initially created as a clone of Bug #1221176 +++

Description of problem:
ovirt-hosted-engine-setup doesn't complain trying to deploy on an host with '_' in its name while the engine than correctly refuse to add the host not validating its name.

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup.noarch       1.2.4-0.0.master.20150513073740.git86111d0.el7

How reproducible:

Steps to Reproduce:
1. set an hostname with '_' in the name
2. launch hosted-engine --deploy

Actual results:
It accepts the wrong hostname

Expected results:
It should complain about the hostname being invalid due to RFC952

Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2015-10-19 10:56:24 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Gil Klein 2016-02-17 07:39:18 UTC
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA

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