default_min_hwe_kernel: hwe-w is too early to be applied

Bug #1570214 reported by Nobuto Murata
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
maas-deployer
In Progress
Medium
Billy Olsen

Bug Description

ppc64el env I'm currently using requires hwe-w for commissioning. With maas-deployer capability to configure maas settings, I wrote the yaml like below.

====
        settings:
            main_archive: http://archive.ubuntu.com/ubuntu
            maas_name: demo
            default_min_hwe_kernel: hwe-w
====

However setting default_min_hwe_kernel always fails.

====
2016-04-13 17:47:55,052 DEBUG (execc) Executing: 'ssh -i /home/ubuntu/.ssh/id_maas -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o LogLevel=quiet ubuntu@172.X.Y.Z maas maas maas set-config name='default_min_hwe_kernel' value='hwe-w'' stdin='LC_ALL=C'
2016-04-13 17:47:55,582 ERROR (execc)
2016-04-13 17:47:55,583 ERROR (_maas_execute) Command 'ssh -i /home/ubuntu/.ssh/id_maas -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o LogLevel=quiet ubuntu@172.X.Y.X maas maas maas set-config name='default_min_hwe_kernel' value='hwe-w'' failed: rc='2' output=''
2016-04-13 17:47:55,583 ERROR (apply_maas_settings) Unable to set default_min_hwe_kernel to hwe-w
====

It seems default_min_hwe_kernel cannot be set before importing boot images. On the other hand, http_proxy in maas config is required before importing boot images...

[maas_deployer/vmaas/engine.py]
         self.apply_maas_settings(client, maas_config)
         self.wait_for_import_boot_images(client, maas_config)
         self.configure_maas(client, maas_config)

Related branches

Revision history for this message
Zoltan Arnold Nagy (zoltan) wrote :

Just run into this. Any input from the developers on how to solve this?

Changed in maas-deployer:
status: New → In Progress
assignee: nobody → Billy Olsen (billy-olsen)
milestone: none → 0.0.8
importance: Undecided → Medium
Revision history for this message
Billy Olsen (billy-olsen) wrote :

@zoltan,

There's no real work around at the moment other than setting the config after the fact via the maas cli command, e.g. maas <profile> maas set-config name='default_min_hwe_kernel' value='hwe-[vwx]'

Revision history for this message
Jason Furmanek (furmanek) wrote :

Yea, the workaround I've been using is to just use the MAAS CLI to set the hwe kernel.
You don't have to wait until the download of the all the images are done. Once the it starts downloading the boot image you want it will accept the setting using the CLI.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.