Hostname not fully set during Fuelmenu and breaks rabbitmq
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
Medium
|
Fuel Sustaining | ||
Mitaka |
Won't Fix
|
Medium
|
Fuel Sustaining |
Bug Description
Summary: Fuel 9.0 - Despite the inclusion of hostnamectl in Fuelmenu from bug https:/
The net effect is that rabbitmq gets broken and won't start by still being configured for the default fuel.domain.tld hostname.
Further Details:
- To reproduce, install a fuel server using default settings except hostname. Change the hostname to some new name.
- When fuel server completes and boots up to login prompt, login and compare /etc/hostname, /etc/hosts, and output of hostname command, uname -n, and hostnamectl status. There will be a mix of default and new hostname.
- /etc/hosts and /etc/hostname will have the new name.
- hostname command and uname -n will show the default fuel name. sysctl kernel.hostname shows the still default hostname present from the utsname structure.
Also, hostnamectl status will show mix of names. Example:
[root@fuel ~]# hostnamectl
Static hostname: maui
Transient hostname: fuel.domain.tld
Icon name: computer-vm
Chassis: vm
Machine ID: 9fe38d589a64466
Boot ID: 61ee4120e2064c5
Virtualization: kvm
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:
Kernel: Linux 3.10.0-
Architecture: x86-64
Also as a result, rabbitmq fails to start due to default fuel name still present in /etc/rabbitmq/
Final notes:
Rebooting the fuel server now again manually will yield the correct hostname when the server comes back up. But the damage has already been done to rabbitmq server.
Changed in fuel: | |
status: | Incomplete → Confirmed |
importance: | Undecided → Medium |
milestone: | none → 9.2 |
tags: | added: area-library |
Changed in fuel: | |
status: | Confirmed → Won't Fix |
What fuel version is it?