[2.3, pod, b1] Virsh pod: autostart for created virtual machines is not enabled

Bug #1742703 reported by Stefan Fleischmann on 2018-01-11
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Medium
Newell Jensen
2.3
Medium
Newell Jensen

Bug Description

When MAAS creates a virtual machine on a Virsh pod, the virtual machine is not marked as automatically started at boot. Hence if the pod reboots all virtual machines created via MAAS will have to be started manually. MAAS should enable autostart for the VMs it creates.

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"

$ dpkg -l | grep maas
ii maas 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS client and command-line interface
ii maas-common 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all Region Controller for MAAS
ii python3-django-maas 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)

Tags: pod Edit Tag help

Related branches

Changed in maas:
importance: Undecided → High
milestone: none → 2.4.0beta1
status: New → Triaged
summary: - Virsh pod: autostart for created virtual machines is not enabled
+ [2.3, pod] Virsh pod: autostart for created virtual machines is not
+ enabled
Changed in maas:
assignee: nobody → Newell Jensen (newell-jensen)
tags: added: pod
summary: - [2.3, pod] Virsh pod: autostart for created virtual machines is not
+ [2.3, pod, b1] Virsh pod: autostart for created virtual machines is not
enabled
Changed in maas:
importance: High → Medium
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers