Bug 1112383
| Summary: | bind uses example.com when values are updated | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Dan Radez <dradez> |
| Component: | rhel-osp-installer | Assignee: | Dan Radez <dradez> |
| Status: | CLOSED NOTABUG | QA Contact: | Omri Hochman <ohochman> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.0 (RHEL 6) | CC: | acathrow, adahms, ddomingo, dradez, mburns, rhos-maint, sclewis, slong |
| Target Milestone: | ga | ||
| Target Release: | 5.0 (RHEL 7) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
The domain and foreman URL values will not set the host's hostname. Before the Red Hat Enterprise OpenStack Platform Installer is started:
* The hosts' hostname must be set
* The /etc/hosts file should have an entry that matches the hostname of the host.
Additionally, the foreman URL should use a FQDN that can be resolved by the nodes to be provisioned.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-07-10 23:20:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I've got a basic patch for this that sets the hostname and updates /etc/hosts. We're struggling with the facts somehow being cached. Once the networking setup is complete the configuration for http and dns still use the old values for the domain and hostname. After working through possible solutions and a discussion with Hugh we've come to the conclusion that the installer should not allow you to change the hostname. This is because kafo is unable to elegantly update the hostname due to the way it sort of snapshots facts during installation. Instead there should be an installation note that suggests the hostname should be set ahead of time. Action for this bz may include restricting the domain and foreman url from being edited. I'll discuss this with marek and update the bz. Hi Dan, I've set the type to 'Known Issue' and edited the doc text. But if this issue will continue through the next release, please raise a documentation bug to have the Foreman doco updated as well. thanks, Summer |
Description of problem: when the dns domain and foreman url values are updated the values that get put into /var/named/dynamic/db.{domain} do not reflect the values passed to the installer. Version-Release number of selected component (if applicable): How reproducible: every time Steps to Reproduce: 1. set domain and foreman url to something other than default vaules 2. 3. Actual results: installation fails, can't resolve livecd.example.com but the foreman url was entered as something different Expected results: bind should be configured properly. Additional info: