[provision] additional kernel_params not reflected in ubunut /boot/grub/grub.cfg

[Moshe Levi]

I add intel_iommu=on in the kernel parameters.

I can see is /etc/astute.yaml but not in /boot/grub/grub.cfg

This only happen on ubuntu

The iso was build on the latest code in 12/7/014

[Aleksandr Didenko (adidenko)]

{
    "api": "1.0",
    "astute_sha": "18a6861ecf96e20ead17782ef4ea8d62e7449c14",
    "auth_required": false,
    "build_id": "2014-07-15_02-19-18",
    "build_number": "320",
    "feature_groups": [
        "mirantis"
    ],
    "fuellib_sha": "b2caaea7b0a39f40ff08240da4dab81aaba6e29c",
    "fuelmain_sha": "d12f4ac69a6299130b360e788b098c1f304b28c3",
    "nailgun_sha": "902cbb4ac4995a13dfaedb6a5111f177c1df9ab5",
    "ostf_sha": "9863db951a6e159f4fa6e6861c8331e1af069cf8",
    "production": "docker",
    "release": "5.1"
}

Kernel parameters are not changed in cobbler (see attached cobbler-systems.tgz - it's the content of /var/lib/cobbler/config/systems.d/ dir).

[Aleksandr Didenko (adidenko)]

Diagnostic snapshot attached - Fuel master was used for several deployments, the one with the probem starts around Tue Jul 15 13:44 server time (in logs).

nailgin/api.log:
2014-07-15 13:43:39.980 DEBUG [7f933810e740] (logger) Request PUT /api/clusters/1/attributes from 10.108.0.1:57963 ...."kernel_params":{"kernel":{"weight":45,"type":"text","description":"Default kernel parameters","value":"console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset intel_iommu=on","label":"Initial parameters"},.........

astute/astute.log:
2014-07-15T13:44:01 info: [374] Adding node-1 into cobbler
2014-07-15T13:44:01 debug: [374] Cobsh is initialized with: ...."pm_data"=>{"kernel_params"=>"console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset",.....

[Vladimir Sharshov (vsharshov)]

Aleksandr Didenko (adidenko) logs:

Astute got message where new kernel params not insert in required filed. Information which applied for provisioning state should contain in provisioning state, but:

2014-07-15T13:43:59 debug: [374] Process message from worker queue: ...

    \"pm_data\": {\"kernel_params\": \"console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset\"

but should

    \"pm_data\": {\"kernel_params\": \"console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset intel_iommu=on\"

also this param showed in deployment section:

  \"metadata\": {<...> \"kernel_params\": {\"kernel\": \"console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset intel_iommu=on\"}

this section correct.

For some reason Nailgun do no send data correctly for this case.

This can be proven by Nailgun logs to. If we check Nailgun app.logs:

2014-07-15 13:43:59.007 DEBUG [7f933810e740] (__init__) RPC cast to orchestrator:

    {
        "args": {
            "task_uuid": "3a8bd2aa-4d00-4b12-af6c-429b152b45ca",
            "provisioning_info": {
                "nodes": [
                   {
                    "uid": "1",
                       "ks_meta": {
                            "pm_data": {
                                "kernel_params": "console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset",

        "args": {
            "task_uuid": "74bc69a5-0290-4a8b-b0e0-2c0b893bfa0a",
            "deployment_info": [
                    "kernel_params": {
                        "kernel": "console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset intel_iommu=on",

Aleksandr, do you use web interface or cli to deploy this cluster?

Also i could not reproduce it in 5.1 ISO #343.

Result in /boot/grub/grub.cfg:

        linux /vmlinuz-3.11.0-18-generic root=UUID=abf917c0-df3d-4093-93d9-46f950169749 ro console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset intel_iommu=on

        linux /vmlinuz-3.11.0-18-generic root=UUID=abf917c0-df3d-4093-93d9-46f950169749 ro recovery nomodeset console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset intel_iommu=on

         linux /vmlinuz-3.2.0-65-generic root=UUID=abf917c0-df3d-4093-93d9-46f950169749 ro console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset intel_iommu=on

        linux /vmlinuz-3.2.0-65-generic root=UUID=abf917c0-df3d-4093-93d9-46f950169749 ro recovery nomodeset console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset intel_iommu=on

[Vladimir Sharshov (vsharshov)]

Aleksandr Didenko (adidenko) says that have used web interface to deploy cluster.

[Dima Shulyak (dshulyak)]

root@node-6:~# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.11.0-18-generic root=UUID=2432f580-c283-4c38-a70e-04cdd8a198c8 ro console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset intel_iommu=on

[Dima Shulyak (dshulyak)]

Interesting note:

in provisioning_info - "kernel_params": "console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset",

in deployment_info - "kernel": "console=ttyS0,9600 console=tty0 rootdelay=90 nomodeset intel_iommu=on",

[Dima Shulyak (dshulyak)]

I was able to reproduce it.

If you modify kernel_params after node is added to cluster, this issue will arise

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit fca9b8269cab0e726bc26d8ff3a04d307eb006c3
Author: Dima Shulyak <email address hidden>
Date: Fri Jul 25 14:18:55 2014 +0300

    Use cluster kernel_params if node kernel_params is not set

    Current UX messes with kernel_params setter logic

    If kernel_params is modified after node is added to cluster -
    kernel_params on node wont be changed

    After this fix cluster kernel params will be sended to
    orchestrator if no specific params provided for node

    Change-Id: Ic03aaf92942d9e7f3c568460aaa0bd5d83cdb51b
    Closes-Bug: #1341486