cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanna Santhanam (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-549) Rebuild system/network vm at destruction
Date Sat, 23 Mar 2013 18:23:14 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Prasanna Santhanam resolved CLOUDSTACK-549.
-------------------------------------------

    Resolution: Incomplete

Doesn't destroying/marking the system VMs bring back new system VMs? This assuming the NFS
failure was repaired.
                
> Rebuild system/network vm at destruction
> ----------------------------------------
>
>                 Key: CLOUDSTACK-549
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-549
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Ioannis Charalampidis
>
> It would be very helpful if the system VMs (including the network service providers)
were rebuilt upon destruction; or even if there was an option "rebuild" in the VM interface.
> In a test cluster, we had a corruption in an NFS mount that rendered 2 system VMs unable
to boot (everything else looked fine). However there was no simple way to rebuild / re-deploy
only the damaged system VMs and I chose to re-install CloudStack as the fastest solution.
That's because after deleting the damaged VMs they never came up again and after deleting
the zone I had to wait for very long timeouts before everything was clean to re-create it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message