[
https://issues.apache.org/jira/browse/CLOUDSTACK-9589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665082#comment-15665082
]
ASF GitHub Bot commented on CLOUDSTACK-9589:
--------------------------------------------
Github user jburwell commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1759#discussion_r87896137
--- Diff: setup/db/db/schema-480to481-cleanup.sql ---
@@ -18,3 +18,6 @@
--;
-- Schema cleanup from 4.8.0 to 4.8.1;
--;
+
+DELETE FROM `cloud`.`host_details` where name = 'vmName' and value in
(select name from `cloud`.`vm_instance` where state = 'Expunging' and
hypervisor_type ='BareMetal');
--- End diff --
Why is this change scoped only to the baremetal hypervisor? It would seem
that it should apply to all hypervisors.
> vmName entries from host_details table for the VM's whose state is Expunging
> should be deleted during upgrade from older versions
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9589
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9589
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Baremetal
> Affects Versions: 4.4.4
> Environment: Baremetal zone
> Reporter: subhash yedugundla
> Fix For: 4.8.1
>
>
> Having vmName entries for VMs in 'expunging' states would cause with
> deploying VMs with matching host tags fail. So removing them during upgrade
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
