| 2014-09-29 22:05:01 |
Sam Stoelinga |
bug |
|
|
added bug |
| 2014-09-29 22:05:01 |
Sam Stoelinga |
attachment added |
|
sosreport-node-39-20140929215504-fba4.tar.xz https://bugs.launchpad.net/bugs/1375481/+attachment/4219651/+files/sosreport-node-39-20140929215504-fba4.tar.xz |
|
| 2014-09-29 22:05:35 |
Sam Stoelinga |
attachment added |
|
fuel-snapshot-2014-09-29_22-21-04.tgz https://bugs.launchpad.net/fuel/+bug/1375481/+attachment/4219652/+files/fuel-snapshot-2014-09-29_22-21-04.tgz |
|
| 2014-09-29 22:06:39 |
Sam Stoelinga |
description |
Description: When deploying an Ubuntu environment on custom hardware the LVM volumes won't get created succesfully. Note when using CentOS environment on the same hardware it works as it should.
Fuel version: 5.1
build_id: "2014-09-17_21-40-34"
build_number: "11"
Steps to reproduce:
1. Use same hardware environment as sos-report
2. Deploy Ubuntu environment
Actual results:
Deployment failed because it couldn't create the LVM volumes
Expected results:
Deployment succeeds for both CentOS and Ubuntu |
Description: When deploying an Ubuntu environment on custom hardware the LVM volumes won't get created succesfully. Note when using CentOS environment on the same hardware it works as it should.
Fuel version: 5.1
build_id: "2014-09-17_21-40-34"
build_number: "11"
Steps to reproduce:
1. Use same hardware environment as sos-report
2. Deploy Ubuntu environment
Actual results:
Deployment failed because it couldn't create the LVM volumes
Expected results:
Deployment succeeds for both CentOS and Ubuntu
Interesting log to see of fuel master is /var/log/remote/10.10.10.24/root.log |
|
| 2014-09-29 22:11:58 |
Sam Stoelinga |
description |
Description: When deploying an Ubuntu environment on custom hardware the LVM volumes won't get created succesfully. Note when using CentOS environment on the same hardware it works as it should.
Fuel version: 5.1
build_id: "2014-09-17_21-40-34"
build_number: "11"
Steps to reproduce:
1. Use same hardware environment as sos-report
2. Deploy Ubuntu environment
Actual results:
Deployment failed because it couldn't create the LVM volumes
Expected results:
Deployment succeeds for both CentOS and Ubuntu
Interesting log to see of fuel master is /var/log/remote/10.10.10.24/root.log |
Description: When deploying an Ubuntu environment on custom hardware the LVM volumes won't get created succesfully. Note when using CentOS environment on the same hardware it works as it should.
The attachment sosreport-node-39 includes all the system information of node that has the problematic hardware.
Fuel version: 5.1
build_id: "2014-09-17_21-40-34"
build_number: "11"
Steps to reproduce:
1. Use same hardware environment as sos-report
2. Deploy Ubuntu environment
Actual results:
Deployment failed because it couldn't create the LVM volumes
Expected results:
Deployment succeeds for both CentOS and Ubuntu
Interesting log to see of fuel master is /var/log/remote/10.10.10.24/root.log |
|
| 2014-09-30 00:47:58 |
Sam Stoelinga |
description |
Description: When deploying an Ubuntu environment on custom hardware the LVM volumes won't get created succesfully. Note when using CentOS environment on the same hardware it works as it should.
The attachment sosreport-node-39 includes all the system information of node that has the problematic hardware.
Fuel version: 5.1
build_id: "2014-09-17_21-40-34"
build_number: "11"
Steps to reproduce:
1. Use same hardware environment as sos-report
2. Deploy Ubuntu environment
Actual results:
Deployment failed because it couldn't create the LVM volumes
Expected results:
Deployment succeeds for both CentOS and Ubuntu
Interesting log to see of fuel master is /var/log/remote/10.10.10.24/root.log |
Description: When deploying an Ubuntu environment on custom hardware the LVM volumes won't get created succesfully. Note when using CentOS environment on the same hardware it works as it should.
The attachment sosreport-node-39 includes all the system information of node that has the problematic hardware.
After first using CentOS to deploy the nodes, which clears the previous disk partitions and then deploy ubuntu it's working fine. So it seems this issue is also specific to existing partitioning and ubuntu not able to cleanly delete previous existing partitioning.
Fuel version: 5.1
build_id: "2014-09-17_21-40-34"
build_number: "11"
Steps to reproduce:
1. Use same hardware environment as sos-report
2. Deploy Ubuntu environment
Actual results:
Deployment failed because it couldn't create the LVM volumes
Expected results:
Deployment succeeds for both CentOS and Ubuntu
Interesting log to see of fuel master is /var/log/remote/10.10.10.24/root.log |
|
| 2014-09-30 05:24:20 |
Mike Scherbakov |
fuel: milestone |
|
6.0 |
|
| 2014-09-30 06:54:01 |
Mike Scherbakov |
fuel: assignee |
|
Vladimir Kozhukalov (kozhukalov) |
|
| 2014-10-01 03:12:08 |
Nastya Urlapova |
fuel: importance |
Undecided |
High |
|
| 2014-10-01 14:34:54 |
Vladimir Kozhukalov |
bug |
|
|
added subscriber Vladimir Kozhukalov |
| 2014-10-01 18:29:50 |
Sam Stoelinga |
attachment added |
|
remote.tar.gz https://bugs.launchpad.net/fuel/+bug/1375481/+attachment/4221717/+files/remote.tar.gz |
|
| 2014-10-06 10:00:31 |
Vladimir Kuklin |
fuel: status |
New |
Confirmed |
|
| 2014-11-18 17:17:12 |
OpenStack Infra |
fuel: status |
Confirmed |
In Progress |
|
| 2014-11-25 15:58:30 |
OpenStack Infra |
fuel: status |
In Progress |
Fix Committed |
|
