Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1304714 - [RFE] Check for working DNS before configuring the overcloud services
[RFE] Check for working DNS before configuring the overcloud services
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-validations (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
high Severity high
: Upstream M1
: 13.0 (Queens)
Assigned To: Ana Krivokapic
Udi
: FutureFeature, Triaged
Depends On:
Blocks: 1442136
  Show dependency tree / graph
 
Reported: 2016-02-04 07:52 EST by Attila Darazs
Modified: 2018-06-27 09:26 EDT (History)
20 users (show)

See Also:
Fixed In Version: openstack-tripleo-validations-8.1.1-0.20180119231917.2ff3c79.el7ost
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-06-27 09:26:22 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 524304 None master: MERGED tripleo-validations: Add a validation to check for working DNS (I8862266d5bb15e5bef0b6714858ad7e327ea9991) 2018-02-07 08:54 EST
Red Hat Product Errata RHEA-2018:2086 normal SHIPPED_LIVE Red Hat OpenStack Platform 13.0 Enhancement Advisory 2018-06-28 15:51:39 EDT

  None (edit)
Description Attila Darazs 2016-02-04 07:52:40 EST 
Description of problem:
We recently debugged a bug that was the result of non-working DNS resolution and made RabbitMQ fail during deployment without helpful errors, as the socket bindings got really slow without working DNS.

This highlighted the need for a DNS check during the network validation, maybe with a configurable host to resolve that will work even in environments where the resolution is limited to local names.

This idea came out of bug #1304423
Comment 2 Mike Burns 2016-04-07 17:07:13 EDT 
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.
Comment 4 Jaromir Coufal 2016-09-30 03:36:59 EDT 
-> Validations
Comment 5 Ola Pavlenko 2016-11-23 10:41:04 EST 
Could you please update the status of this RFE?
Comment 6 Tomas Sedovic 2016-11-24 06:31:49 EST 
No update. We didn't have time to work on this (so it won't be in OSP 10).
Comment 7 Ola Pavlenko 2016-12-12 09:38:17 EST 
Potential candidate for M-3
Comment 16 Udi 2018-04-09 08:23:39 EDT 
Verified in: openstack-tripleo-validations-8.4.0-1.el7ost.noarch

This was implemented as a pre-deployment validation only, and will run on the undercloud. The user cannot run this on the overcloud during the deployment, before the services are configured, so deployments may still fail if DNS is misconfigured on the overcloud.

Atilla - consider opening a new bug to do a similar test during the deployment, and stop the deployment with a clear error message if DNS is not working. Or re-open this bug if you feel it's not properly completed.
Comment 17 Attila Darazs 2018-04-25 09:05:41 EDT 
Should be fine, clearing needinfo.
Comment 19 errata-xmlrpc 2018-06-27 09:26:22 EDT 
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/RHEA-2018:2086
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.