elements ubuntu-guest and fedora-guest mess up /etc/hosts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Medium
|
Amrith Kumar |
Bug Description
These elements contain the following code:
amrith@
./ubuntu-
./fedora-
amrith@
#!/bin/bash
set -e
set -o xtrace
# CONTEXT: HOST after IMAGE BUILD as SCRIPT USER
# PURPOSE: Set the loopback network in host file
host_name=
echo "127.0.0.1 ${host_name}" >> /etc/hosts
amrith@
#!/bin/bash
set -e
set -o xtrace
# CONTEXT: HOST after IMAGE BUILD as SCRIPT USER
# PURPOSE: Set the loopback network in host file
host_name=
echo "127.0.0.1 ${host_name}" >> /etc/hosts
amrith@
The end result is that the /etc/hosts file on a machine ends up looking like this (shown from an ubuntu machine)
hadoop@h1:~$ more /etc/hosts
127.0.0.1 localhost
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
127.0.0.1 amrith-work
127.0.1.1 h1.novalocal h1
The issue is with the penultimate line, 127.0.0.1 should NOT point to the name of the machine where the guest image was built!
Changed in trove: | |
importance: | Undecided → Medium |
summary: |
- elements ubuntu-guest and fedora-guest mess up /etchosts + elements ubuntu-guest and fedora-guest mess up /etc/hosts |
Changed in trove: | |
milestone: | none → mitaka-3 |
Changed in trove: | |
status: | In Progress → Fix Committed |
Changed in trove: | |
status: | Fix Committed → Fix Released |
https:/ /review. openstack. org/#/c/ 272711/