Back to bug 1919855
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Stephen Finucane | 2021-01-25 10:01:30 UTC | Status | NEW | ON_DEV |
| Stephen Finucane | 2021-01-25 10:01:53 UTC | Keywords | Reopened | |
| Stephen Finucane | 2021-01-25 10:01:55 UTC | Assignee | nova-maint | stephenfin |
| Stephen Finucane | 2021-01-25 10:05:57 UTC | Link ID | OpenStack gerrit 772277 | |
| Blocks | 1872314 | |||
| Depends On | 1872314 | |||
| Stephen Finucane | 2021-02-02 14:26:58 UTC | Doc Text | Cause: The Compute service (nova) sanitizes the instance display name provided when creating instance(s). This sanitized display name is used for DNS purposes when DNS integration is enabled in the Networking service (Neutron). However, the sanitization did not replace periods ('.'), which could result in display names being recognized as Fully Qualified Domain Names (FQDNs). Consequence: The sanitization used by the Compute service could produce invalid hostnames when certain instance display names were used. For example, 'rhel-8.4' since numeric TLDs ('4') are not permissible. When these instance names were used and DNS integration was enabled in the Networking service, the Networking service would reject the invalid hostname resulting in a failure to create the instance and a HTTP 500 server error from the Compute service. Fix: Periods are now replaced by hyphens in instance names. Result: The sanitization of the instance display names to generate the hostname is improved and hostnames will no longer be parsed as FQDNs. Instance display names are not affected and will continue to allow free-form strings. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Stephen Finucane | 2021-02-02 14:40:22 UTC | Status | ON_DEV | MODIFIED |
| Fixed In Version | openstack-nova-20.4.2-2.20210127094933.8378786.el8ost | |||
| Artom Lifshitz | 2021-02-05 19:06:36 UTC | Target Milestone | --- | Alpha |
| RHEL Program Management | 2021-02-05 19:06:44 UTC | Target Release | --- | 16.2 (Train on RHEL 8.4) |
| errata-xmlrpc | 2021-02-19 13:22:50 UTC | Status | MODIFIED | ON_QA |
| Red Hat Bugzilla | 2021-02-26 09:49:34 UTC | CC | agreentr | |
| Irina | 2021-04-14 11:12:08 UTC | Doc Text | Cause: The Compute service (nova) sanitizes the instance display name provided when creating instance(s). This sanitized display name is used for DNS purposes when DNS integration is enabled in the Networking service (Neutron). However, the sanitization did not replace periods ('.'), which could result in display names being recognized as Fully Qualified Domain Names (FQDNs). Consequence: The sanitization used by the Compute service could produce invalid hostnames when certain instance display names were used. For example, 'rhel-8.4' since numeric TLDs ('4') are not permissible. When these instance names were used and DNS integration was enabled in the Networking service, the Networking service would reject the invalid hostname resulting in a failure to create the instance and a HTTP 500 server error from the Compute service. Fix: Periods are now replaced by hyphens in instance names. Result: The sanitization of the instance display names to generate the hostname is improved and hostnames will no longer be parsed as FQDNs. Instance display names are not affected and will continue to allow free-form strings. | When an instance is created, the Compute (nova) service sanitizes the instance display name to generate a valid hostname when DNS integration is enabled in the Networking (neutron) service. Before this update, the sanitization did not replace periods ('.') in instance names, for example, 'rhel-8.4'. This could result in display names being recognized as Fully Qualified Domain Names (FQDNs) which produced invalid hostnames. When instance names contained periods and DNS integration was enabled in the Networking service, the Networking service would reject the invalid hostname resulting in a failure to create the instance and a HTTP 500 server error from the Compute service. With this update, periods are now replaced by hyphens in instance names to prevent hostnames being parsed as FQDNs. You can continue to use free-form strings for instance display names. |
| Pavan | 2021-06-12 18:47:20 UTC | Status | ON_QA | VERIFIED |
| CC | pkesavar | |||
| Red Hat Bugzilla | 2021-07-01 12:47:25 UTC | CC | zili | |
| Miguel Garcia | 2021-07-07 12:10:49 UTC | Status | VERIFIED | MODIFIED |
| Irina | 2021-07-07 13:15:39 UTC | Link ID | Red Hat Issue Tracker RHOSPDOC-741 | |
| errata-xmlrpc | 2021-07-07 13:57:25 UTC | Status | MODIFIED | ON_QA |
| Pavan | 2021-07-19 13:43:53 UTC | Status | ON_QA | VERIFIED |
| James Smith | 2021-07-30 00:56:38 UTC | CC | jamsmith | |
| Doc Text | When an instance is created, the Compute (nova) service sanitizes the instance display name to generate a valid hostname when DNS integration is enabled in the Networking (neutron) service. Before this update, the sanitization did not replace periods ('.') in instance names, for example, 'rhel-8.4'. This could result in display names being recognized as Fully Qualified Domain Names (FQDNs) which produced invalid hostnames. When instance names contained periods and DNS integration was enabled in the Networking service, the Networking service would reject the invalid hostname resulting in a failure to create the instance and a HTTP 500 server error from the Compute service. With this update, periods are now replaced by hyphens in instance names to prevent hostnames being parsed as FQDNs. You can continue to use free-form strings for instance display names. | When an instance is created, the Compute (nova) service sanitizes the instance display name to generate a valid hostname when DNS integration is enabled in the Networking (neutron) service. + Before this update, the sanitization did not replace periods ('.') in instance names, for example, 'rhel-8.4'. This could result in display names being recognized as Fully Qualified Domain Names (FQDNs) which produced invalid hostnames. When instance names contained periods and DNS integration was enabled in the Networking service, the Networking service would reject the invalid hostname resulting in a failure to create the instance and a HTTP 500 server error from the Compute service. + With this update, periods are now replaced by hyphens in instance names to prevent hostnames being parsed as FQDNs. You can continue to use free-form strings for instance display names. |
||
| Irina | 2021-08-12 11:06:36 UTC | CC | igallagh | |
| Greg Rakauskas | 2021-09-09 21:10:39 UTC | CC | gregraka | |
| Doc Text | When an instance is created, the Compute (nova) service sanitizes the instance display name to generate a valid hostname when DNS integration is enabled in the Networking (neutron) service. + Before this update, the sanitization did not replace periods ('.') in instance names, for example, 'rhel-8.4'. This could result in display names being recognized as Fully Qualified Domain Names (FQDNs) which produced invalid hostnames. When instance names contained periods and DNS integration was enabled in the Networking service, the Networking service would reject the invalid hostname resulting in a failure to create the instance and a HTTP 500 server error from the Compute service. + With this update, periods are now replaced by hyphens in instance names to prevent hostnames being parsed as FQDNs. You can continue to use free-form strings for instance display names. | When an instance is created, the Compute service (nova) sanitizes the instance display name to generate a valid hostname when DNS integration is enabled in the Networking service (neutron). + Before this update, the sanitization did not replace periods ('.') in instance names, for example, 'rhel-8.4'. This could result in display names being recognized as Fully Qualified Domain Names (FQDNs) which produced invalid hostnames. When instance names contained periods and DNS integration was enabled in the Networking service, the Networking service would reject the invalid hostname resulting in a failure to create the instance and a HTTP 500 server error from the Compute service. + With this update, periods are now replaced by hyphens in instance names to prevent hostnames being parsed as FQDNs. You can continue to use free-form strings for instance display names. |
||
| errata-xmlrpc | 2021-09-15 00:11:29 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2021-09-15 07:11:11 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2021-09-15 07:11:11 UTC | |||
| errata-xmlrpc | 2021-09-15 07:11:33 UTC | Link ID | Red Hat Product Errata RHEA-2021:3483 | |
| Greg Rakauskas | 2021-10-13 19:13:17 UTC | CC | ndeevy | |
| Doc Text | When an instance is created, the Compute service (nova) sanitizes the instance display name to generate a valid hostname when DNS integration is enabled in the Networking service (neutron). + Before this update, the sanitization did not replace periods ('.') in instance names, for example, 'rhel-8.4'. This could result in display names being recognized as Fully Qualified Domain Names (FQDNs) which produced invalid hostnames. When instance names contained periods and DNS integration was enabled in the Networking service, the Networking service would reject the invalid hostname resulting in a failure to create the instance and a HTTP 500 server error from the Compute service. + With this update, periods are now replaced by hyphens in instance names to prevent hostnames being parsed as FQDNs. You can continue to use free-form strings for instance display names. | When an instance is created, the Compute service (nova) sanitizes the instance display name to generate a valid hostname when DNS integration is enabled in the Networking service (neutron). + Before this update, the sanitization did not replace periods ('.') in instance names, for example, 'rhel-8.4'. This could result in display names being recognized as Fully Qualified Domain Names (FQDNs) which produced invalid hostnames. When instance names contained periods and DNS integration was enabled in the Networking service, the Networking service rejected the invalid hostname, which resulted in a failure to create the instance and a HTTP 500 server error from the Compute service. + With this update, periods are now replaced by hyphens in instance names to prevent hostnames being parsed as FQDNs. You can continue to use free-form strings for instance display names. |
||
| ndeevy | 2021-10-18 08:55:36 UTC | CC | ndeevy | |
| Red Hat One Jira (issues.redhat.com) | 2021-12-28 16:58:03 UTC | Link ID | Red Hat Issue Tracker OSP-2953 | |
| Luigi Tamagnone | 2021-12-29 11:25:40 UTC | CC | ltamagno | |
| Flags | needinfo?(stephenfin) | |||
| Stephen Finucane | 2022-01-05 11:49:53 UTC | Flags | needinfo?(stephenfin) | |
| Artom Lifshitz | 2023-03-21 19:39:37 UTC | QA Contact | nova-maint | osp-dfg-compute |
Back to bug 1919855