2014-03-13 12:52:01 |
Anton Rodionov |
description |
Description of the environment.
Version: 4.1 release
OS: CentOS 6.4
Reference architecture: non-HA
Total number of nodes: 2 (not including Fuel Master)
RAID is in use.
Steps to reproduce.
1. Install the master node.
2. Try to install CentOS to the slave nodes and get the error.
Expected result: OS is installed.
Actual result: Getting the error "Specified non-existent partition 3 on partition command."
The customer has found the workaround: Applying this https://docs.google.com/file/d/0B4szgxpvz2aCUFpTNXR2NVhiNHc (initram debug image) helps, the path for the partitions are correctly generated and CentOS installs.
Impact: the customer has found a workaround but the fix should probably be included in the future versions.
Trying to set up OpenStack with Mirantis Fuel 4.1.
One machine acting as Fuel. Two machines to be set in the OpenStack cluster (HP DL 380 G5, HP DL320G5s), one as controller, one as compute.
New problem after installing Mirantis Fuel 4.1, after deploying configuration, the following error is shown:
"The following error was found while parsing the kickstart configuration file:
The following error occurred on line 2:
Specified non-existent partition 3 on partition command."
------------------------------------------------------------------------
One way to bypass the problem was to install https://docs.google.com/file/d/0B4szgxpvz2aCUFpTNXR2NVhiNHc (initram debug image). When this is applied, the path for the partitions are correctly generated and CentOS installs.
We think the problem is within this file: https://github.com/stackforge/fuel-web/blob/master/bin/agent?source=c
that section:
detailed_meta[:disks] << {
:name => dname,
:model => binfo[:model],
:size => (binfo[:size].to_i * block_size),
:disk => block[:disk],
:extra => block[:extra],
:removable => block[:removable]
}
So there must be a difference in how the partition are found between the fuel_debug and the 4.1 version.
Here is what seems to work: https://dl.dropboxusercontent.com/u/18136096/correctAgent |
Description of the environment.
Version: 4.1 release
OS: CentOS 6.4
Reference architecture: non-HA
Total number of nodes: 2 (not including Fuel Master)
RAID is in use.
Steps to reproduce.
1. Install the master node.
2. Try to install CentOS to the slave nodes and get the error.
Expected result: OS is installed.
Actual result: Getting the error "Specified non-existent partition 3 on partition command."
The customer has found the workaround: Applying this https://docs.google.com/file/d/0B4szgxpvz2aCUFpTNXR2NVhiNHc (initram debug image) helps, the path for the partitions are correctly generated and CentOS installs.
Impact: the customer has found a workaround but the fix should probably be included in the future versions.
Original messages from customer:
Trying to set up OpenStack with Mirantis Fuel 4.1.
One machine acting as Fuel. Two machines to be set in the OpenStack cluster (HP DL 380 G5, HP DL320G5s), one as controller, one as compute.
New problem after installing Mirantis Fuel 4.1, after deploying configuration, the following error is shown:
"The following error was found while parsing the kickstart configuration file:
The following error occurred on line 2:
Specified non-existent partition 3 on partition command."
------------------------------------------------------------------------
One way to bypass the problem was to install https://docs.google.com/file/d/0B4szgxpvz2aCUFpTNXR2NVhiNHc (initram debug image). When this is applied, the path for the partitions are correctly generated and CentOS installs.
We think the problem is within this file: https://github.com/stackforge/fuel-web/blob/master/bin/agent?source=c
that section:
detailed_meta[:disks] << {
:name => dname,
:model => binfo[:model],
:size => (binfo[:size].to_i * block_size),
:disk => block[:disk],
:extra => block[:extra],
:removable => block[:removable]
}
So there must be a difference in how the partition are found between the fuel_debug and the 4.1 version.
Here is what seems to work: https://dl.dropboxusercontent.com/u/18136096/correctAgent |
|