Description of problem: Use oo-install to add a new node into an existing env, after installation, no DNS for this new node is added. Version-Release number of selected component (if applicable): oo-install-ose-2.0b-20131111-2053 How reproducible: Always Steps to Reproduce: 1. Following https://access.redhat.com/site/articles/492873 2. Run oo-install to set up an env. 3. Run oo-install to add a new node into this env. Actual results: DNS record for new node is not added. Expected results: DNS record for new node should be added. Additional info:
I agree that this should be attempted; it will not always work reliably, however, so the user docs should always reflect that they need to check and possibly fix host DNS entries.
oo-install OSE launcher will now ssh to the broker after configuring a new node and use oo-register-dns to add a record for the host. oo-register-dns doesn't leave a bad exit code when it fails so at this point I don't think failure will be detected. But for most installs this should work.
Seen like the related fix patch are: https://github.com/openshift/openshift-extras/commit/1b1620dfad3a149591640b3b2af0752de3ebe386#diff-56a2e821f8b9d3bebe1a4cfcf7694314 and https://github.com/openshift/openshift-extras/commit/926aaa869c7857125958de1902b9f6609db0669b#diff-06b86fae435286edf4f83cba3f9117a7 But currently the latest oo-install version is oo-install-20131125-2001, the installation script in oo-install is out-of-date, pls refer to BZ#1036041 for more details, so verfication is blocked by BZ#1036041.
install.openshift.com and install.openshift.com/ose have been updated to oo-install-20131213-1454
Verified this bug with oo-install-20131213-2058, and PASS. Before adding new node: # named-checkzone -Dj hosts.example.com /var/named/dynamic/hosts.example.com.db zone hosts.example.com/IN: hosts.example.com/MX 'mail.hosts.example.com' has no address records (A or AAAA) zone hosts.example.com/IN: loaded serial 2011112904 hosts.example.com. 1 IN SOA bb.hosts.example.com. hostmaster.hosts.example.com. 2011112904 60 15 1800 10 hosts.example.com. 1 IN NS bb.hosts.example.com. hosts.example.com. 1 IN MX 10 mail.hosts.example.com. bb.hosts.example.com. 1 IN A 10.4.59.171 OK Run oo-install to add new node: <--snip--> Running 'define_hosts' step on 10.4.59.171 (bb.hosts.example.com) Copying deployment scripts to target 10.4.59.171. Executing deployment script on 10.4.59.171 (bb.hosts.example.com). You can watch the full log with: ssh root.59.171 'tail -f /tmp/openshift-deploy.log' Warning: Permanently added '10.4.59.171' (RSA) to the list of known hosts. OpenShift: Completed updating host DNS entries. --> Here is adding DNS record All installer steps are complete. Please reboot newly-installed systems to complete the deployment. After script is completed: # named-checkzone -Dj hosts.example.com /var/named/dynamic/hosts.example.com.db zone hosts.example.com/IN: hosts.example.com/MX 'mail.hosts.example.com' has no address records (A or AAAA) zone hosts.example.com/IN: loaded serial 2011112906 hosts.example.com. 1 IN SOA bb.hosts.example.com. hostmaster.hosts.example.com. 2011112906 60 15 1800 10 hosts.example.com. 1 IN NS bb.hosts.example.com. hosts.example.com. 1 IN MX 10 mail.hosts.example.com. bb.hosts.example.com. 180 IN A 10.4.59.171 node.hosts.example.com. 180 IN A 10.4.59.156 OK