Changes to object store removes SecondaryStorage host from the host
table. This affects the test where we identify the secondary storage nfs
host to login to where we verify if the snapshot is present on the
physical resource.
* added base classes for imagestore/stagingstore operations
* fixed the test to check only if NFS is used as backing store
TODO: Fix for s3 based storage layer
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
While finding endpoint to send the migrate volume command, in case of zone wide storage pool, storage engine is picking a host among all connected hosts randomly. Hence a host may be from different cluster t
Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>
Detail: Cloudstack tries to stop VMs all the time, for all sorts of reasons,
but usually just to get into a known state. Libvirt throws an exception of
'Domain not found' when attempting to stop a VM that doesn't exist. This causes
problems for troubleshooting real issues. Domain not found should equate
to success if trying to stop.
BUG-ID: CLOUDSTACK-4011
Bugfix-for: 4.2
Signed-off-by: Marcus Sorensen <marcus@betterservers.com> 1375825281 -0600
System template upgrade is not required during 4.0 upgrade since we handle the same during 4.2 upgrade. So removing the system template update during 4.0 upgrade.
portable IP is trying to insert network id as physical network id
ensuring network id, physical network id, source network id are properly
set for portable ip in user_ip_address and vlan tables
Introduced new column format for volumes as per the hypervisor by joining the storage pool and cluster table. Since pre 4.2 storage pool will always have cluster id populated.
Signed off by : nitin mehta<nitin.mehta@citrix.com>
In external network after network GC the network n/w cidr changes.
In this case the static nat enable vm ip also chagnes. So updated the new
vm ip address in user_ip_address table.
After upgrade the SSVM was staying in connecting/alert state. This was because
while handling the processConnect command for ssvm the management server was
trying to template sync. For resource limit calculation it was trying to get the
remote size of the template. If the template was no longer available a number
format exception was thrown. The process connect wasn't getting completed and
the ssvm used to stay in connecting/alert state. While creating template from
snapshot cloudstack looks for up and enabled ssvms and because there wasn't
any available (as the ssvm was in coonecting/alert state) it used to pick the
wrong resource (LocalNfs*Resource) instead of the NfsSecondaryStorageResource.
Fixed the issue by making sure number format exceptions are avoided so that
SSVM moves to the right state.
When adding an S3 secondary storage, the administrator will
now be shown help for each input field making it friendlier
to use.
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
1. correcting the log_test_exceptions decorator so nose testrunner can
detect and document the running test
2. correct the wait for network cleanup -> network.gc
3. Remove commented skips
4. Sanitize host passwords
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
(cherry picked from commit 04df5d289ca9394c7f647fb94e5289160a2d3467)
KVM.snapshot.enabled is lowercased by f025db95 to keep the configs
uniformly lower-case. But it missed the upgrade script and the
references in SnapshotManagerImpl. This commit will fix the issue in all
locations
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
Prasanna Santhanam
Radhika PC
Sateesh Chodapuneedi
Likitha Shetty
Sanjay Tripathi
Wei Zhou
Min Chen
Marcus Sorensen
Edison Su
frank
Rajesh Battala
Alena Prokharchyk
rayeesn
Wido den Hollander
SrikanteswaraRao Talluri
Bharat Kumar
Harikrishna Patnala
Murali Reddy
Nitin Mehta
Jayapal
Devdeep Singh
Thomas O'Dowd
ashutoshkelkar