Back to bug 1672972
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Matthew Booth | 2019-02-08 15:40:51 UTC | Keywords | Triaged | |
| CC | mbooth | |||
| Matthew Booth | 2019-02-08 15:41:44 UTC | Priority | unspecified | medium |
| melanie witt | 2019-02-11 19:00:16 UTC | CC | mwitt | |
| Nilesh | 2019-02-26 10:29:38 UTC | CC | nchandek | |
| vivek koul | 2019-04-24 03:21:00 UTC | Priority | medium | high |
| Severity | medium | high | ||
| melanie witt | 2019-06-12 23:02:26 UTC | Status | NEW | ASSIGNED |
| Assignee | nova-maint | mwitt | ||
| melanie witt | 2019-06-12 23:03:34 UTC | Keywords | FutureFeature | |
| Target Release | --- | 16.0 (T) | ||
| Summary | After a Nova compute shutdown, the instances' state held by the hypervisor is not updated | [OSP16][RFE] After a Nova compute shutdown, the instances' state held by the hypervisor is not updated | ||
| melanie witt | 2019-06-17 18:32:33 UTC | Status | ASSIGNED | ON_DEV |
| melanie witt | 2019-06-18 22:37:17 UTC | Status | ON_DEV | ASSIGNED |
| Link ID | OpenStack gerrit 666181 | |||
| melanie witt | 2019-06-18 22:38:00 UTC | Status | ASSIGNED | ON_DEV |
| Lee Yarwood | 2019-06-21 10:05:09 UTC | CC | lyarwood | |
| Target Milestone | --- | Upstream M3 | ||
| Reartes Guillermo | 2019-06-24 16:33:17 UTC | CC | greartes | |
| Erwan Gallen | 2019-06-25 15:51:47 UTC | CC | egallen | |
| RHEL Program Management | 2019-06-25 15:57:46 UTC | Target Release | 16.0 (T) | --- |
| RHEL Program Management | 2019-06-28 09:16:40 UTC | Target Release | --- | 16.0 (T) |
| Erwan Gallen | 2019-06-28 09:26:13 UTC | Summary | [OSP16][RFE] After a Nova compute shutdown, the instances' state held by the hypervisor is not updated | [RFE] After a Nova compute shutdown, the instances' state held by the hypervisor is not updated |
| Sean Cohen | 2019-07-10 03:13:20 UTC | Target Release | 16.0 (T) | --- |
| CC | scohen | |||
| RHEL Program Management | 2019-07-10 03:13:26 UTC | Target Release | --- | 16.0 (T) |
| RHEL Program Management | 2019-07-10 12:52:47 UTC | Target Release | 16.0 (T) | --- |
| Russell Bryant | 2019-07-10 13:15:30 UTC | CC | rbryant | |
| RHEL Program Management | 2019-07-11 14:49:49 UTC | Keywords | ZStream | |
| melanie witt | 2019-09-09 21:03:11 UTC | Link ID | OpenStack gerrit 666181 | OpenStack gerrit 679181 |
| Target Milestone | Upstream M3 | --- | ||
| melanie witt | 2019-09-10 23:29:36 UTC | Status | ON_DEV | NEW |
| melanie witt | 2019-10-16 15:07:16 UTC | Status | NEW | ON_DEV |
| Target Release | --- | 17.0 (V) | ||
| RHEL Program Management | 2019-10-16 15:07:23 UTC | Target Release | 17.0 (V) | --- |
| melanie witt | 2019-10-18 20:47:10 UTC | Keywords | Patch | |
| melanie witt | 2019-11-04 23:20:53 UTC | Keywords | Patch | |
| Status | ON_DEV | POST | ||
| melanie witt | 2019-11-04 23:31:39 UTC | Status | POST | MODIFIED |
| Fixed In Version | openstack-nova-20.1.0-0.20191102011931.a22b825.el8 | |||
| melanie witt | 2020-01-15 17:01:54 UTC | Target Release | --- | 17.0 |
| Target Milestone | --- | Upstream M1 | ||
| RHEL Program Management | 2020-01-15 17:02:00 UTC | Target Release | 17.0 | --- |
| RHEL Program Management | 2020-03-03 05:23:53 UTC | Target Release | --- | 17.0 |
| Stephen Finucane | 2020-04-27 10:13:37 UTC | CC | sfinucan | |
| Target Upstream Version | Ussuri | |||
| Matthew Booth | 2021-04-19 10:31:23 UTC | CC | mbooth | |
| Stephen Finucane | 2021-06-15 16:11:09 UTC | Target Milestone | Upstream M1 | Alpha |
| Erwan Gallen | 2021-06-27 21:04:53 UTC | Priority | high | medium |
| RHEL Program Management | 2021-07-21 12:16:21 UTC | Target Release | 17.0 | --- |
| Erwan Gallen | 2021-07-30 16:27:16 UTC | Target Milestone | Alpha | z1 |
| RHEL Program Management | 2021-07-30 16:27:25 UTC | Target Release | --- | 17.0 |
| melanie witt | 2021-08-16 16:19:32 UTC | Blocks | 1994072 | |
| Red Hat Bugzilla | 2022-03-25 18:50:19 UTC | CC | nchandek | |
| Red Hat One Jira (issues.redhat.com) | 2022-03-25 18:59:13 UTC | Link ID | Red Hat Issue Tracker OSP-3146 | |
| Jon Schlueter | 2022-04-25 19:16:25 UTC | Status | MODIFIED | ON_QA |
| RHEL Program Management | 2022-07-05 15:19:59 UTC | CC | spower | |
| Target Release | 17.0 | --- | ||
| Jon Schlueter | 2022-07-11 16:51:43 UTC | Status | ON_QA | MODIFIED |
| Erwan Gallen | 2022-09-01 19:47:39 UTC | Priority | medium | low |
| James Parker | 2022-09-29 15:27:57 UTC | CC | jparker | |
| RHEL Program Management | 2022-09-29 15:28:06 UTC | Target Release | --- | 17.1 |
| melanie witt | 2022-10-27 21:02:49 UTC | Fixed In Version | openstack-nova-20.1.0-0.20191102011931.a22b825.el8 | openstack-nova-23.2.2-1.20221021161917.a9e8162.el9osttrunk |
| OSP Team | 2022-11-04 06:01:26 UTC | Fixed In Version | openstack-nova-23.2.2-1.20221021161917.a9e8162.el9osttrunk | openstack-nova-23.2.2-1.20221021161917.a9e8162.el9ost |
| errata-xmlrpc | 2022-11-29 14:53:18 UTC | Status | MODIFIED | ON_QA |
| melanie witt | 2022-12-01 19:39:04 UTC | Blocks | 2150082 | |
| melanie witt | 2022-12-01 19:51:15 UTC | Target Milestone | z1 | ga |
| Mikey Ariel | 2023-01-02 15:01:38 UTC | CC | mariel | |
| Artom Lifshitz | 2023-03-21 19:11:11 UTC | QA Contact | nova-maint | osp-dfg-compute |
| James Parker | 2023-05-09 19:52:37 UTC | Status | ON_QA | VERIFIED |
| James Parker | 2023-05-09 19:57:42 UTC | CC | igallagh, joflynn | |
| Flags | needinfo?(igallagh) needinfo?(joflynn) | |||
| Bogdan Dobrelya | 2023-05-17 13:52:34 UTC | Status | VERIFIED | NEW |
| CC | bdobreli | |||
| Bogdan Dobrelya | 2023-05-17 13:55:02 UTC | Status | NEW | VERIFIED |
| Sree | 2023-05-17 13:59:25 UTC | CC | skovili | |
| Irina | 2023-05-22 13:30:24 UTC | Flags | needinfo?(igallagh) | |
| Artom Lifshitz | 2023-05-29 16:18:47 UTC | CC | alifshit | |
| Doc Text | Feature: Add custom policy that allows operators to expose the host_status field in the `show server details` response to give users a hint that the host that their instance is on has something wrong with it. Reason: Previously, if an instance's compute host was unreachable from the controller, the instance would show up as ACTIVE, potentially misleading the user into thinking everything was fine, when in fact they were unable to connect to their instance because the compute host was unreachable/down. Result: If the host_status is UNKNOWN or DOWN, users have a clue that their instance on that host might be unreachable. | |||
| Doc Type | If docs needed, set a value | Enhancement | ||
| Joanne O'Flynn | 2023-06-07 12:34:41 UTC | Doc Text | Feature: Add custom policy that allows operators to expose the host_status field in the `show server details` response to give users a hint that the host that their instance is on has something wrong with it. Reason: Previously, if an instance's compute host was unreachable from the controller, the instance would show up as ACTIVE, potentially misleading the user into thinking everything was fine, when in fact they were unable to connect to their instance because the compute host was unreachable/down. Result: If the host_status is UNKNOWN or DOWN, users have a clue that their instance on that host might be unreachable. | This enhancement adds a custom policy that allows operators to expose the *host_status* field in the output of the `show server details` command to indicate to the user that the host that their instance is on is unreachable. Previously, if the Compute host of an instance was unreachable from the Controller, the instance was set to ACTIVE, potentially misleading the user into thinking that the Compute host was operating as normal, when in fact they were unable to connect to their instance because the Compute host was unreachable. With this enhancement, if the *host_status* is `UNKNOWN` or `DOWN`, users know that their instance on that host might be unreachable. |
| Flags | needinfo?(joflynn) | |||
| Artom Lifshitz | 2023-06-07 16:47:13 UTC | Flags | needinfo?(joflynn) | |
| melanie witt | 2023-06-07 16:53:13 UTC | Doc Text | This enhancement adds a custom policy that allows operators to expose the *host_status* field in the output of the `show server details` command to indicate to the user that the host that their instance is on is unreachable. Previously, if the Compute host of an instance was unreachable from the Controller, the instance was set to ACTIVE, potentially misleading the user into thinking that the Compute host was operating as normal, when in fact they were unable to connect to their instance because the Compute host was unreachable. With this enhancement, if the *host_status* is `UNKNOWN` or `DOWN`, users know that their instance on that host might be unreachable. | This enhancement adds a custom policy that allows operators to expose the `UNKNOWN` *host_status* in the output of the `show server details` command to indicate to non-admin users that the host that their instance is on is possibly unreachable. Previously, there was no way for operators to expose *host_status* limited only to the `UNKNOWN` status to non-admin users. This meant that users could see their instance as ACTIVE without being able to see any *host_status*. With this enhancement, if the operator as configured it, non-admin users will be able to see if *host_status* is `UNKNOWN` to make them aware that the host their instance is on might be unreachable, despite it being ACTIVE. |
| Joanne O'Flynn | 2023-06-08 13:45:13 UTC | Flags | needinfo?(joflynn) | needinfo?(mwitt) |
| melanie witt | 2023-06-08 16:31:37 UTC | Flags | needinfo?(mwitt) | |
| James Smith | 2023-06-09 04:17:58 UTC | Doc Text | This enhancement adds a custom policy that allows operators to expose the `UNKNOWN` *host_status* in the output of the `show server details` command to indicate to non-admin users that the host that their instance is on is possibly unreachable. Previously, there was no way for operators to expose *host_status* limited only to the `UNKNOWN` status to non-admin users. This meant that users could see their instance as ACTIVE without being able to see any *host_status*. With this enhancement, if the operator as configured it, non-admin users will be able to see if *host_status* is `UNKNOWN` to make them aware that the host their instance is on might be unreachable, despite it being ACTIVE. | This enhancement adds a custom policy that allows operators to expose the `UNKNOWN` *host_status* in the output of the `show server details` command. This status indicates to non-admin users that the host that their instance is on is possibly unreachable. + Previously, there was no way for operators to expose *host_status* limited only to the `UNKNOWN` status to non-admin users. This meant that users could see their instance as ACTIVE without being able to see any *host_status*. + Now the operator can configure the policy so that non-admin users can see if *host_status* is `UNKNOWN`, indicating that the host running their instance might be unreachable, despite it being ACTIVE. |
| CC | jamsmith | |||
| Joanne O'Flynn | 2023-06-09 09:30:14 UTC | Doc Text | This enhancement adds a custom policy that allows operators to expose the `UNKNOWN` *host_status* in the output of the `show server details` command. This status indicates to non-admin users that the host that their instance is on is possibly unreachable. + Previously, there was no way for operators to expose *host_status* limited only to the `UNKNOWN` status to non-admin users. This meant that users could see their instance as ACTIVE without being able to see any *host_status*. + Now the operator can configure the policy so that non-admin users can see if *host_status* is `UNKNOWN`, indicating that the host running their instance might be unreachable, despite it being ACTIVE. | This enhancement helps cloud users determine if the reason they are unable to access an "ACTIVE" instance is because the Compute node that hosts the instance is unreachable. RHOSP administrators can now configure the `NovaShowHostStatus` and `NovaApiHostStatusPolicy` parameters to enable a custom policy that displays the "UNKNOWN" `host_status` to cloud users when they run the `openstack show server details` command, if the host Compute node is unreachable. |
| Joanne O'Flynn | 2023-06-09 10:31:36 UTC | Doc Text | This enhancement helps cloud users determine if the reason they are unable to access an "ACTIVE" instance is because the Compute node that hosts the instance is unreachable. RHOSP administrators can now configure the `NovaShowHostStatus` and `NovaApiHostStatusPolicy` parameters to enable a custom policy that displays the "UNKNOWN" `host_status` to cloud users when they run the `openstack show server details` command, if the host Compute node is unreachable. | This enhancement helps cloud users determine if the reason they are unable to access an "ACTIVE" instance is because the Compute node that hosts the instance is unreachable. RHOSP administrators can now configure the following parameters to enable a custom policy that provides a status in the `host_status` field to cloud users when they run the `openstack show server details` command, if the host Compute node is unreachable: + * `NovaApiHostStatusPolicy`: Specifies the role the custom policy applies to. * `NovaShowHostStatus`: Specifies the level of host status to show to the cloud user, for example, "UNKNOWN". |
| Ian Frangs | 2023-08-03 15:46:23 UTC | Flags | needinfo?(mwitt) | |
| errata-xmlrpc | 2023-08-16 00:01:46 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-08-16 01:09:21 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-08-16 01:09:21 UTC | |||
| errata-xmlrpc | 2023-08-16 01:10:49 UTC | Link ID | Red Hat Product Errata RHEA-2023:4577 |
Back to bug 1672972