Ubuntu classic deploy stuck with 'No kernel modules were found'

[Oleg S. Gelbukh]

Description of the environment.

Output of http://fuel-master-node:8000/api/version/:

{"build_id": "2015-05-27_17-33-07", "build_number": "474", "release_versions": {"2014.1.3-5.1.1": {"VERSION": {"build_id": "2014-12-03_01-07-36", "ostf_sha": "64cb59c681658a7a55cc2c09d079072a41beb346", "build_number": "48", "api": "1.0", "nailgun_sha": "500e36d08a45dbb389bf2bd97673d9bff48ee84d", "production": "docker", "fuelmain_sha": "7626c5aeedcde77ad22fc081c25768944697d404", "astute_sha": "ef8aa0fd0e3ce20709612906f1f0551b5682a6ce", "feature_groups": ["mirantis"], "release": "5.1.1", "fuellib_sha": "a3043477337b4a0a8fd166dc83d6cd5d504f5da8"}}, "2014.2-6.0": {"VERSION": {"build_id": "2014-12-26_14-25-46", "ostf_sha": "a9afb68710d809570460c29d6c3293219d3624d4", "build_number": "58", "api": "1.0", "nailgun_sha": "5f91157daa6798ff522ca9f6d34e7e135f150a90", "production": "docker", "fuelmain_sha": "81d38d6f2903b5a8b4bee79ca45a54b76c1361b8", "astute_sha": "16b252d93be6aaa73030b8100cf8c5ca6a970a91", "feature_groups": ["mirantis"], "release": "6.0", "fuellib_sha": "fde8ba5e11a1acaf819d402c645c731af450aff0"}}, "2014.2.2-6.1": {"VERSION": {"build_id": "2015-05-27_17-33-07", "build_number": "474", "api": "1.0", "fuel-library_sha": "05b59b7c9279222de734295535d86f53dd3d4225", "nailgun_sha": "ac8668cc06368fe22330e293c9ce8655d46846bd", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-6.1", "production": "docker", "python-fuelclient_sha": "e19f1b65792f84c4a18b5a9473f85ef3ba172fce", "astute_sha": "5d570ae5e03909182db8e284fbe6e4468c0a4e3e", "fuel-ostf_sha": "4cd2fef040ae9e7645a6b17a7cb44d3cd8fbe0be", "release": "6.1", "fuelmain_sha": "6b5712a7197672d588801a1816f56f321cbceebd"}}}, "auth_required": true, "api": "1.0", "fuel-library_sha": "05b59b7c9279222de734295535d86f53dd3d4225", "nailgun_sha": "ac8668cc06368fe22330e293c9ce8655d46846bd", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-6.1", "production": "docker", "python-fuelclient_sha": "e19f1b65792f84c4a18b5a9473f85ef3ba172fce", "astute_sha": "5d570ae5e03909182db8e284fbe6e4468c0a4e3e", "fuel-ostf_sha": "4cd2fef040ae9e7645a6b17a7cb44d3cd8fbe0be", "release": "6.1", "fuelmain_sha": "6b5712a7197672d588801a1816f56f321cbceebd"}

Operating System: Ubuntu
Reference Architecture: Multinode HA
Network model: Neutron+VLAN
Related Projects installed: None

Steps to reproduce:
1. Create a new cluster
2. Select Ubuntu 14.04
3. Select Ceph storage stack
4. Leave other settings intact
5. In Settings tab, check Provisioning Method: 'Classic'
6. Add node to environment with:
fuel node set --env ENV_ID --node NODE_ID --role controller
7. Start provisioning:
fuel node --node NODE_ID --provision

Expected result:
Node is provisioned, running Ubuntu 14.04 operating system.

Actual result:
Fuel API: Node ends up in 'error' state.
Node terminal console: Debian installer stuck in state depicted on screenshot. Error message is "No kernel modules were found" at stage "Download installer components".

Workaround:
Delete files in '/var/www/nailgun/ubuntu/x86_64/images/'. New versions of netboot kernel/initrd will be downloaded upon the provisioning of the next node.
See more details on this bug under the following link:
https://bugs.launchpad.net/ubuntu/+bug/1407714/comments/10

Impact:
Provisioning in 'classic' mode cannot be completed. No node can be installed in the environment.

[Sergii Golovatiuk (sgolovatiuk)]

Please follow https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Test_and_report_bugs

What's the version of build? How can we reproduce the steps?

[Oleg S. Gelbukh (gelbuhos)]

Sergii, please, see the updated description.

[Oleg S. Gelbukh (gelbuhos)]

I verified the workaround by deleting kernel/initrd files for netboot from `/var/www/nailgun/ubuntu/x86_64/images' directory. Upon the next provisioning, `download-debian-installer' script updates images and provisioning succeeds.

[Dmitry Pyzhov (dpyzhov)]

The issue is that downloaded kernel/initrd became outdated and needs to be redownloaded

[Ihor Kalnytskyi (ikalnytskyi)]

I believe that the best we can offer right now is to download netboot kernels each time we start provisioning for the cluster.

[Oleg S. Gelbukh (gelbuhos)]

Igor, I second you on this.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/187970

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/187970
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=b2d7bc92c226b96ac432a68858e7d84947193963
Submitter: Jenkins
Branch: master

commit b2d7bc92c226b96ac432a68858e7d84947193963
Author: Igor Kalnitsky <email address hidden>
Date: Wed Jun 3 14:43:09 2015 +0300

    Download debian netboot installer each time

    Currently if debian netboot installer is already downloaded we skip
    downloading and start provisioning. It's an error-prone approach
    because the installer may stuck if its kernel version mismatch
    archive's kernel version. This patch starts to download debian
    installer each time we start provisioning.

    Closes-Bug: #1461206

    Change-Id: Ia6b8653461e604ae05f306406e8a3515a593fc53
    Signed-off-by: Igor Kalnitsky <email address hidden>