Activity log for bug #1588781
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2016-06-03 11:22:51 | Arthur Svechnikov | bug | added bug | ||
| 2016-06-03 11:22:59 | Arthur Svechnikov | fuel: milestone | 10.0 | ||
| 2016-06-03 11:23:02 | Arthur Svechnikov | fuel: assignee | Arthur Svechnikov (asvechnikov) | ||
| 2016-06-03 11:23:53 | OpenStack Infra | fuel: status | New | In Progress | |
| 2016-06-03 11:25:53 | Arthur Svechnikov | nominated for series | fuel/newton | ||
| 2016-06-03 11:25:53 | Arthur Svechnikov | bug task added | fuel/newton | ||
| 2016-06-03 11:25:53 | Arthur Svechnikov | nominated for series | fuel/mitaka | ||
| 2016-06-03 11:25:53 | Arthur Svechnikov | bug task added | fuel/mitaka | ||
| 2016-06-03 11:26:01 | Arthur Svechnikov | fuel/mitaka: milestone | 9.0 | ||
| 2016-06-03 11:26:06 | Arthur Svechnikov | fuel/mitaka: assignee | Arthur Svechnikov (asvechnikov) | ||
| 2016-06-03 11:34:20 | Michael Polenchuk | fuel/mitaka: status | New | Confirmed | |
| 2016-06-03 11:34:37 | Michael Polenchuk | fuel/newton: importance | Undecided | High | |
| 2016-06-03 11:34:42 | Michael Polenchuk | fuel/mitaka: importance | Undecided | High | |
| 2016-06-03 12:09:29 | Dmitry Klenov | tags | area-python feature-cpu-pinning feature-dpdk | ||
| 2016-06-03 12:35:25 | Arthur Svechnikov | description | Detailed bug description: NIC's NUMA affinity is incorrect Steps to reproduce: Using Machine with multiple NUMA's 1. Open Interfaces response raw data and Node mete numa_topology data Expected results: NIC has numa_node according to bus_info Actual result: NIC info: [ { "name": "enp10s0f0", ... "interface_properties": { ... "numa_node": null, }, "bus_info": "0000:81:00.0" }, ] Node's numa_topology.numa_nodes info: [ { "pcidevs": [ "0000:81:00.0", "0000:81:00.1" ], "cpus": [...], "id": 2, "memory": 67644473344 }, ... ] Reproducibility: <put your information here> Workaround: <put your information here> Impact: <put your information here> Description of the environment: | Detailed bug description: NIC's NUMA affinity is incorrect Steps to reproduce: Using Machine with multiple NUMA's 1. Open Interfaces response raw data and Node mete numa_topology data Expected results: NIC has numa_node according to bus_info Actual result: NIC info: [ { "name": "enp10s0f0", ... "interface_properties": { ... "numa_node": null, }, "bus_info": "0000:81:00.0" }, ] Node's numa_topology.numa_nodes info: [ { "pcidevs": [ "0000:81:00.0", "0000:81:00.1" ], "cpus": [...], "id": 2, "memory": 67644473344 }, ... ] Reproducibility: <put your information here> Workaround: <put your information here> Impact: <put your information here> Description of the environment: Fuel 9.0 build id 395 | |
| 2016-06-03 13:27:51 | OpenStack Infra | fuel: status | In Progress | Fix Committed | |
| 2016-06-03 13:30:32 | OpenStack Infra | fuel/mitaka: status | Confirmed | In Progress | |
| 2016-06-03 14:27:39 | Arthur Svechnikov | fuel/newton: status | Fix Committed | In Progress | |
| 2016-06-06 18:00:48 | OpenStack Infra | fuel/mitaka: status | In Progress | Fix Committed | |
| 2016-06-07 15:05:59 | Arthur Svechnikov | fuel/newton: status | In Progress | Fix Committed | |
| 2016-06-14 14:54:20 | Sergii | fuel/mitaka: status | Fix Committed | Fix Released |
