DNS setting set by fuel-qa didn't survive reboot of Fuel master node
Bug #1563124 reported by
Sergey Yudin
This bug report is a duplicate of:
Bug #1567957: [regression] It is not possible to resolve slave nodes by host names.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Kyrylo Galanov | ||
Mitaka |
Won't Fix
|
Medium
|
Fuel Library (Deprecated) | ||
Newton |
Confirmed
|
Medium
|
Kyrylo Galanov |
Bug Description
Steps for reproduce
1. Deploy master node
2. Add some string to /etc/resolv.conf
3. Reboot master node by command: shutdown -r now
4. Check /etc/resolv.conf
Actual result:
Lines added manually removed
Expected:
Lines were added manually in the file
Diagnostic:
http://
ISO: fuel-9.
Changed in fuel: | |
assignee: | nobody → Fuel QA Team (fuel-qa) |
importance: | Undecided → Medium |
status: | New → Confirmed |
milestone: | none → 9.0 |
tags: | added: area-qa |
description: | updated |
tags: | removed: need-info |
To post a comment you must log in.
It is not problem in qa area.
After master node reboot file /etc/resolv.conf was cleared
Steps for reproduce
1. Deploy master node
2. Add some string to /etc/resolv.conf
3. Reboot master node by command: shutdown -r now
4. Check /etc/resolv.conf
Actual result:
Lines added manually removed
Expected:
Lines were added manually in the file
Diagnostic: paste.openstack .org/show/ 493011/
http://
ISO: fuel-9. 0-155-2016- 04-04_08- 00-00.iso