[1.8] probe-and-enlist-hardware for virsh doesn't keep domain as hostname

Bug #1445965 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Mike Pontillo

Bug Description

probe-and-enlist hardware needs to keep the domain name as default when adding new machines, otherwise, it should have an option to create new hsotnames when adding VM's.

Related branches

Changed in maas:
importance: Undecided → Critical
status: New → Confirmed
milestone: none → 1.8.0
summary: - Cannot probe-and-enlist hardware
+ [1.8.0b3] Cannot probe-and-enlist hardware
summary: - [1.8.0b3] Cannot probe-and-enlist hardware
+ [1.8.0b3] probe-and-enlist-hardware for virsh/esxi/vmware needs to keep
+ domain name as hostname
summary: - [1.8.0b3] probe-and-enlist-hardware for virsh/esxi/vmware needs to keep
- domain name as hostname
+ [1.8.0b3] probe-and-enlist-hardware for virsh/esxi/vmware doesn't keep
+ domain as hostname
description: updated
Changed in maas:
status: Confirmed → Triaged
importance: Critical → High
summary: - [1.8.0b3] probe-and-enlist-hardware for virsh/esxi/vmware doesn't keep
- domain as hostname
+ [1.8] probe-and-enlist-hardware for virsh doesn't keep domain as
+ hostname
Changed in maas:
assignee: nobody → Mike Pontillo (mpontillo)
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
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.