Activity log for bug #1790569
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2018-09-04 03:29:12 | fupingxie | bug | added bug | ||
| 2018-09-04 03:29:41 | fupingxie | nova: assignee | fupingxie (fpxie) | ||
| 2018-09-04 08:08:16 | OpenStack Infra | nova: status | New | In Progress | |
| 2018-09-06 14:01:00 | Matt Riedemann | nova: status | In Progress | Incomplete | |
| 2018-09-07 06:28:42 | OpenStack Infra | nova: status | Incomplete | In Progress | |
| 2018-09-12 03:10:22 | fupingxie | description | If rabbitMQ get error when creating a VM and resources has already allocated on node-1, the allocated resource can not be removed when rabbitMQ become OK and the VM has started on node-2 successfully. | If rabbitMQ get error when migrating a VM and resources has already allocated on node-1, the allocated resource can not be removed when rabbitMQ become OK and the VM has started on node-2 successfully. | |
| 2018-09-12 03:32:56 | fupingxie | description | If rabbitMQ get error when migrating a VM and resources has already allocated on node-1, the allocated resource can not be removed when rabbitMQ become OK and the VM has started on node-2 successfully. | resources allocated can not be cleaned. 1. Migrate an Instance VM-1 from node-0 to node-1. 2. Scheduler recieved the message and claim resouces for VM-1 on node-1. 3. However, if RabbitMQ exception for pressure overload or other reason, conductor can not received a response , and migration becomes error. 4. At last, the resources allocated for VM-1 on node-1 leaved that, can not be cleaned. | |
| 2019-05-07 12:16:11 | Matt Riedemann | tags | migrate resource-tracker | ||
| 2019-05-07 12:22:02 | Matt Riedemann | nova: status | In Progress | Incomplete | |
| 2019-05-07 12:22:05 | Matt Riedemann | nova: assignee | fupingxie (fpxie) | ||
| 2019-07-07 04:17:23 | Launchpad Janitor | nova: status | Incomplete | Expired |
