[regression] It is not possible to resolve slave nodes by host names
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Alex Schultz | ||
Mitaka |
Fix Released
|
High
|
Maksim Malchuk |
Bug Description
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:/
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-$
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_
172
cat /etc/fuel_release:
9.0
cat /etc/fuel_
mitaka-9.0
rpm -qa | egrep 'fuel|astute|
fuel-release-
fuel-misc-
python-
fuel-openstack
fuel-provision
python-
fuel-9.
fuel-nailgun-
rubygem-
fuel-library9.
fuel-agent-
fuel-ui-
fuel-setup-
nailgun-
shotgun-
network-
fuel-bootstrap
fuel-migrate-
fuelmenu-
fuel-notify-
fuel-ostf-
fuel-mirror-
fuel-utils-
[root@nailgun ~]#
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
tags: | added: area-build |
tags: | removed: area-build |
tags: | added: area-library |
tags: | added: on-verification |
tags: | added: on-verification |
no longer affects: | fuel/newton |
Changed in fuel: | |
assignee: | Matthew Mosesohn (raytrac3r) → Fuel Sustaining (fuel-sustaining-team) |
tags: | added: team-bugfix |
tags: | added: release-notes |
tags: | added: on-verification |
tags: |
added: release-notes-done removed: release-notes |
Ivan, what's in your /etc/resolv.conf? Did you repeat running fuelmenu after deployment?