Note:
It works fine on MOS 9.0 #154 and doesn't work on MOS 9.0 #172.
The priority changed to Critical for 9.0 because:
1. It is a regression issue
2. It affects all customers
3. we have fix on review which already merged to master
4. The user impact is the following:
a) Users can't work with fuel slave nodes using hostnames like 'ssh node-1', but we have a lot of documentation / screencasts where we use these hostnames
b) scripts for previous versions of fuel should be rewritten because of this regression issue
c) Some OSTF tests fail, example of related issue: https://bugs.launchpad.net/fuel/+bug/1592876
Steps To Reproduce:
1. Configure OpenStack environment with Fuel 9.0 (I've used build #172), set DNS server to 8.8.8.8 in environment settings. Deploy the cloud.
2. Login to master node via ssh
3. Run "fuel nodes" command
4. Try to login to OpenStack nodes using hostnames like "ssh node-1" (it worked on MOS 7.0 and 8.0)
5. Check /etc/resolv.conf
Expected Result:
User can login to nodes using host name pattern "node-$ID_OF_SLAVE_NODE"
Actual Result:
Fuel master node can't resolve such host names:
[root@nailgun ~]# fuel nodes
id | status | name | cluster | ip | mac | roles | pending_roles | online | group_id
---|----------|------------------|---------|------------|-------------------|----------------------------|---------------|--------|---------
5 | ready | Untitled (f1:e5) | 1 | 10.109.0.5 | 64:32:01:f0:f1:e5 | base-os, cinder, compute | | True | 1
1 | ready | Untitled (a4:93) | 1 | 10.109.0.7 | 64:39:f1:5b:a4:93 | base-os, controller, mongo | | True | 1
3 | discover | Untitled (98:d0) | None | 10.109.0.3 | 64:6c:f8:bd:98:d0 | | | True | None
4 | discover | Untitled (f6:d1) | None | 10.109.0.4 | 64:fe:20:be:f6:d1 | | | True | None
2 | discover | Untitled (d9:1c) | None | 10.109.0.6 | 64:5f:6e:d3:d9:1c | | | True | None
[root@nailgun ~]# ssh node-1
ssh: Could not resolve hostname node-1: Name or service not known
[root@nailgun ~]# cat /etc/resolv.conf
# Generated by NetworkManager
search test.domain.local
nameserver 8.8.8.8
[root@nailgun ~]# shotgun2 short-report
cat /etc/fuel_build_id:
172
cat /etc/fuel_build_number:
172
cat /etc/fuel_release:
9.0
cat /etc/fuel_openstack_version:
mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
fuel-release-9.0.0-1.mos6331.noarch
fuel-misc-9.0.0-1.mos8275.noarch
python-packetary-9.0.0-1.mos131.noarch
fuel-openstack-metadata-9.0.0-1.mos8635.noarch
fuel-provisioning-scripts-9.0.0-1.mos8635.noarch
python-fuelclient-9.0.0-1.mos302.noarch
fuel-9.0.0-1.mos6331.noarch
fuel-nailgun-9.0.0-1.mos8635.noarch
rubygem-astute-9.0.0-1.mos736.noarch
fuel-library9.0-9.0.0-1.mos8275.noarch
fuel-agent-9.0.0-1.mos272.noarch
fuel-ui-9.0.0-1.mos2646.noarch
fuel-setup-9.0.0-1.mos6331.noarch
nailgun-mcagents-9.0.0-1.mos736.noarch
shotgun-9.0.0-1.mos87.noarch
network-checker-9.0.0-1.mos72.x86_64
fuel-bootstrap-cli-9.0.0-1.mos272.noarch
fuel-migrate-9.0.0-1.mos8275.noarch
fuelmenu-9.0.0-1.mos265.noarch
fuel-notify-9.0.0-1.mos8275.noarch
fuel-ostf-9.0.0-1.mos923.noarch
fuel-mirror-9.0.0-1.mos131.noarch
fuel-utils-9.0.0-1.mos8275.noarch
[root@nailgun ~]#
Ivan, what's in your /etc/resolv.conf? Did you repeat running fuelmenu after deployment?