Actions
Bug #45571
openwhen provisioning smithi machines with centos 8, `hostname --fqdn` does not always produce the correct output
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
When I use `teuthology-lock -v --lock-many 1 -m smithi --os-type centos --os-version 8.1` to provision a machine, sometimes `hostname --fqdn` provides a fully qualified domain name and sometimes it does not.
For example, earlier today I ran the the above command and locked smithi057.front.sepia.ceph.com. I then interact as follows:
ivancich@teuthology:~ $ ssh smithi057.front.sepia.ceph.com Activate the web console with: systemctl enable --now cockpit.socket Last login: Fri May 15 17:36:17 2020 from 172.21.0.51 [ivancich@smithi057 ~]$ hostname --fqdn smithi057 [ivancich@smithi057 ~]$ cat /etc/hosts 172.21.15.57 smithi057 smithi057 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 [ivancich@smithi057 ~]$
If I were to edit the first line of /etc/hosts so it's:
172.21.15.57 smithi057.front.sepia.ceph.com smithi057
then `hostname --fqdn` works as expected.
The reason why this is an issue is that the s3 protocol uses a hash of data that includes the fully-qualified domain name, and if there's a discrepancy here, the s3 protocol request is rejected.
Updated by J. Eric Ivancich almost 4 years ago
In case I wasn't clear, sometimes when I provision a Centos 8 smithi, everything works as expected. It's hit and miss.
Updated by J. Eric Ivancich almost 4 years ago
- Related to Feature #46422: rgw: orphan list teuthology test & fully-qualified domain issue added
Actions