Activity log for bug #1804549

Date Who What changed Old value New value Message
2018-11-22 00:27:19 Andres Rodriguez bug added bug
2018-11-22 00:27:29 Andres Rodriguez summary [2.5, UI, regression] Deploy KVM host - If the default deployment OS is non bionic+, clicking Register as MAAS KVM host doesn't set bionic [2.5, UI] Deploy KVM host - If the default deployment OS is non bionic+, clicking Register as MAAS KVM host doesn't set bionic
2018-11-22 00:27:33 Andres Rodriguez maas: importance Undecided High
2018-11-22 00:27:36 Andres Rodriguez maas: milestone 2.5.0rc2
2018-11-22 00:27:43 Andres Rodriguez maas: assignee Anthony Dillon (ya-bo-ng)
2018-11-22 00:27:45 Andres Rodriguez maas: status New Triaged
2018-11-22 00:29:45 Andres Rodriguez attachment added 01-kvm-deploy-bug.png https://bugs.launchpad.net/maas/+bug/1804549/+attachment/5215138/+files/01-kvm-deploy-bug.png
2018-11-22 00:30:10 Andres Rodriguez attachment added 02-clicking-removes-os.png https://bugs.launchpad.net/maas/+bug/1804549/+attachment/5215139/+files/02-clicking-removes-os.png
2018-11-22 00:30:27 Andres Rodriguez description If the selected deployment OS is *not* bionic+, e.g. it is Xenial, clicking on 'Register as MAAS KVM host' doesn't automatically set bionic, but rather, it removes the selection and allows the deployment (which is tracked in (https://bugs.launchpad.net/maas/+bug/1804547) 1. Import Xenial/Bionic images 2. Select Xenial as the deployment OS 3. Click on 'Register MAAS KVM host' -> the OS selection gets reset to nothing instead of auto-selecting Bionic 4. It allows it to be deployed without setting the OS (see https://bugs.launchpad.net/maas/+bug/1804547) If the selected deployment OS is *not* bionic+, e.g. it is Xenial, clicking on 'Register as MAAS KVM host' doesn't automatically set bionic, but rather, it removes the selection and allows the deployment (which is tracked in (https://bugs.launchpad.net/maas/+bug/1804547) 1. Import Xenial/Bionic images 2. Select Xenial as the deployment OS (see 01-kvm-deploy-bug.png) 3. Click on 'Register MAAS KVM host' -> the OS selection gets reset to nothing instead of auto-selecting Bionic 4. It allows it to be deployed without setting the OS (see https://bugs.launchpad.net/maas/+bug/1804547)
2018-11-22 00:30:42 Andres Rodriguez description If the selected deployment OS is *not* bionic+, e.g. it is Xenial, clicking on 'Register as MAAS KVM host' doesn't automatically set bionic, but rather, it removes the selection and allows the deployment (which is tracked in (https://bugs.launchpad.net/maas/+bug/1804547) 1. Import Xenial/Bionic images 2. Select Xenial as the deployment OS (see 01-kvm-deploy-bug.png) 3. Click on 'Register MAAS KVM host' -> the OS selection gets reset to nothing instead of auto-selecting Bionic 4. It allows it to be deployed without setting the OS (see https://bugs.launchpad.net/maas/+bug/1804547) If the selected deployment OS is *not* bionic+, e.g. it is Xenial, clicking on 'Register as MAAS KVM host' doesn't automatically set bionic, but rather, it removes the selection and allows the deployment (which is tracked in (https://bugs.launchpad.net/maas/+bug/1804547) 1. Import Xenial/Bionic images 2. Select Xenial as the deployment OS 3. Click on 'Register MAAS KVM host' -> the OS selection gets reset to nothing instead of auto-selecting Bionic (see 02-clicking-removes-os.png ) 4. It allows it to be deployed without setting the OS (see https://bugs.launchpad.net/maas/+bug/1804547)
2018-11-22 00:31:26 Andres Rodriguez description If the selected deployment OS is *not* bionic+, e.g. it is Xenial, clicking on 'Register as MAAS KVM host' doesn't automatically set bionic, but rather, it removes the selection and allows the deployment (which is tracked in (https://bugs.launchpad.net/maas/+bug/1804547) 1. Import Xenial/Bionic images 2. Select Xenial as the deployment OS 3. Click on 'Register MAAS KVM host' -> the OS selection gets reset to nothing instead of auto-selecting Bionic (see 02-clicking-removes-os.png ) 4. It allows it to be deployed without setting the OS (see https://bugs.launchpad.net/maas/+bug/1804547) If the selected deployment OS is *not* bionic+, e.g. it is Xenial, clicking on 'Register as MAAS KVM host' doesn't automatically set bionic, but rather, it removes the selection and allows the deployment (which is tracked in (https://bugs.launchpad.net/maas/+bug/1804547) 1. Import Xenial/Bionic images 2. Select Xenial as the deployment OS 3. Click on 'Register MAAS KVM host' -> the OS selection gets reset to nothing instead of auto-selecting Bionic (see 02-clicking-removes-os.png ) 4. It allows it to be deployed without setting the OS (see https://bugs.launchpad.net/maas/+bug/1804547) The expected result is that when clicking 'Register MAAS KVM host' is clicked, 'bionic' is auto-selected as the latest available LTS. PS. The information about LTS is already available in the commissioning OS< because the only supported commissioning OS are LTS.
2018-11-22 17:27:30 Anthony Dillon merge proposal linked https://code.launchpad.net/~ya-bo-ng/maas/+git/maas/+merge/359202
2018-11-27 14:33:09 Andres Rodriguez maas: status Triaged In Progress
2018-11-28 15:46:44 MAAS Lander maas: status In Progress Fix Committed
2018-11-30 23:55:15 Andres Rodriguez maas: status Fix Committed Fix Released