6502171f39
bug 9663: do account permission check against the volume when create snapshot
...
status 9663: resolved fixed
2011-05-03 11:33:35 -07:00
64a7f72dc0
bug:9702 removing duplicate scripts/vm/hypervisor/kvm/pingtest.sh
...
correcting path for sshkey for in scripts/pingtest.sh
2011-05-03 14:12:37 -04:00
99badfd54c
Fixed NPE in listNetworks
2011-05-03 10:21:44 -07:00
e3ed681be6
listNetworks: allow seeing Guest system network in Basic zone
2011-05-03 10:21:44 -07:00
3e6cabc31b
Fixed the bug in listNetworks when isSystem parameter was ignored if it was specified along with account/domainId parameter
2011-05-03 10:21:44 -07:00
3daa9b0137
bug 9686,9676,9677: Create usage events for existing resources for port forwarding, load balancer and network offering usage
...
status 9686,9676,9677: resolved fixed
2011-05-03 20:03:29 +05:30
76d48485a5
bug 9664: username parameter for API listuser should search for exact string
...
status 9664: resolved fixed
2011-05-03 13:07:21 +05:30
2bb3d0d695
bug 9687: CloudStack UI - Instance page - add "Security Group" tab.
2011-05-02 20:01:56 -07:00
96043d4326
bug 9688: remove orphaned lb/vm mappings as a part of db upgrade (there was a bug in 2.1.x when the LB rule was removed, but mapping was left in the DB)
...
status 9688: resolved fixed
To verify that the rule was removed:
* make sure that there is no record with lb id in load_balancer table
* verify that lb.delete event was generated for this rule
2011-05-02 18:52:50 -07:00
5b28d4bf10
bug 9683: DB upgrade - generate usage_event for source nat ip addresses
...
status 9683: resolved fixed
2011-05-02 15:54:03 -07:00
d8a68a1083
Bug 9666 - hostId and spoolId overlap in op_host_capacity table
...
Changes:
- When a host connects, we check if it has a CPU and RAM entry in capacity table. If the entry is found, the values are updated if possible. If the entry is not found a new one is inserted.
- The searchCriteria used to check if CPU entry is present was wrong. We were passing in a criteria which did not specify capacityType. So for hostId >= 200, the serach would return capacity entries of storage pools also since poolIDs start from 200 onwards.
- Since an entry was found (although the wrong one), we tried to update it. But update does not happen since the capacity ranges dont match.
And a new insert for CPU also does not happen since an entry is found.
- So as a result CPU entries are never inserted in the table for hostIds >=200
- As a fix, corrected the search criteria.
- During VM deployment, when the entry is not found, we get a NPE. Added a null check to avoid that.
2011-05-02 15:33:10 -07:00
3a5b185972
bug 9675: Usage DB upgrade - set missing fields for snapshot.create/snapshot.delete events
...
status 9675: resolved fixed
2011-05-02 15:17:00 -07:00
14e857a978
bug 9674: Usage db upgrade - set resource_name for volume.create/volume.delete usage events
...
status 9674: resolved fixed
2011-05-02 14:29:54 -07:00
3d963cac1b
revert changes. Can't help direct SG case because it breaks VM stopping after upgrade.
2011-05-02 14:26:29 -07:00
cbc26756d8
bug 8745: we decided on not implementing revert on the agent because it really requires business logic above. Stop if the checkSsh doesn't work
2011-05-02 14:26:29 -07:00
175fc53b53
bug 9672: usage db upgrade - set resource_id for NET.IPASSIGN/RELEASE events
...
status 9672: resolved fixed
2011-05-02 14:15:36 -07:00
a225eb3c0e
bug 9682: DB upgrade - create vm.destroy event in usage_events table
...
status 9682: resolved fixed
2011-05-02 13:54:33 -07:00
cc485c021c
fix vm data permission issue, by ssh to domr, chmod to 644
2011-05-02 11:01:52 -04:00
d8a4a5be52
bug 9658: added missing indexes to 2.1.x-2.2.x upgrade files
...
status 9658: resolved fixed
2011-05-01 12:50:26 -07:00
36e4c8625e
bug 9654: db upgrade - set is_security_group_enabled to true for Direct Guest network in Basic zone
...
status 9654: resolved fixed
2011-05-01 11:06:43 -07:00
ad981cb245
misuse instanceName and name, which causes vm sync behavior weirdly
2011-04-29 19:01:21 -07:00
665b60fcde
bug 9649: fixed up the instance names to be the same
2011-04-29 17:36:14 -07:00
b808604dde
bug 9623: set ha_enable to false for consoleProxy vms and service_offering.
...
status 9623: resolved fixed
Also set ram_size to 1024 for console proxy offering during the upgrade
2011-04-29 11:38:53 -07:00
204370fa8b
bug 9643: connect pool is only for shared access
2011-04-29 11:05:56 -07:00
124274ec80
Removed a potentially dangerous
2011-04-29 11:05:55 -07:00
d4dc90d9fc
Fixed a bug in XmlApiDocReader
2011-04-29 10:16:28 -07:00
ed76394b8e
bug 9519 : add index to avoid table locking
2011-04-28 18:41:01 -07:00
3ea4b18311
bug 9638: fixed bunch of DB upgrade bugs
...
status 9638: resolved fixed
2011-04-28 18:18:56 -07:00
5ad7730e06
Modify keys for security groups in java code instead of sql file (need to check if the key exists before dropping it)
2011-04-28 18:18:56 -07:00
1c2935a5ed
bug 8816: Changed private ip address to link local address when displaying virtual routers.
...
merge from master
2011-04-28 18:16:58 -07:00
14d280634e
Added a check for duplicate public networks.
2011-04-28 16:06:17 -07:00
b273d74c35
bug 9456: added the host id that was already tried to avoid list. Added more debug logs in case that condition happens.
2011-04-28 14:43:44 -07:00
a1fa03ab4b
bug 9633: removed schema.level
...
bug 9632: removed direct.attach.security.groups.enabled
2011-04-28 13:49:52 -07:00
71b264322d
1) Don't drop netapp tables during the upgrade.
...
2) SecurityGroups DB upgrade - drop constraints before chaning the name for the network_group table
2011-04-28 13:29:43 -07:00
510b7ab803
Bug 9635 - set java heap size to 1 GB by defaul
...
Resolved: Fixed
2011-04-28 13:30:31 -07:00
9b799ae4b3
More logging to consoleProxy start command
2011-04-28 01:17:03 -07:00
bd0259c59f
bug 9621: set addressFormat during NicProfile creation
...
status 9621: resolved fixed
2011-04-27 23:25:41 -07:00
a4645ac925
bug 9621: dbUpgrade - set reservation strategy to be Create for Guest Nics in Basic zone
...
status 9621: resolved fixed
2011-04-27 22:45:29 -07:00
a35088d545
Fixed upgrade from 2.1.9 to 2.2.x
2011-04-27 21:27:50 -07:00
a9dded4d27
bug 9622: update mode for nics
...
status 9622: resolved fixed
2011-04-27 21:03:20 -07:00
2ba4f60a8b
bug 9619: handle two types of domr name
...
status 9619: resolved fixed
2011-04-27 18:44:05 -07:00
817d76c190
Allow space in datastore name when adding VMFS datastore
2011-04-27 18:39:28 -07:00
a1aefef1f2
bug 9618: fixed a upgrade, resouce name is changed to XenServer56FP1Resource
...
status 9618: resolved fixed
2011-04-27 15:59:34 -07:00
f890c49272
bug 9617: fixed snapshot upgrade from 223 to 224
...
status 9617: resolved fixed
2011-04-27 15:52:05 -07:00
e8e9bbccfb
fixes a bug where management server has conflicts causes problems
2011-04-27 14:07:18 -07:00
e66baae84e
bug 9610: Added VERSION table and related index change
2011-04-27 13:53:19 -07:00
2c64193646
storage stats can be such that it doesn't work if one storage pool cannot be reached.
2011-04-27 13:53:19 -07:00
fc784f1530
Bug 9585 - Existing Data Disk is being destroyed and recreated on Stop and Start of a User VM.
...
Changes:
- When the ROOT volume of a VM is found to be READY, changed planner to reuse the pool for every volume(root or data) that is READY and that has a pool not in maintenance and not in avoid state
- If ROOT volume is not ready, we dont care about the DATA disk. Both would get re-allocated.
- When a pool is reused for a ready volume, Planner does not call storagepool allocators. And such volumes are not assigned a pool in the deployment destination returned by the planner. Accordingly StorageManager :: prepare method wont recreate these volumes since they are not mentioned in the destination.
2011-04-27 11:56:14 -07:00
57086d0323
Bug 9586 - NPE during host allocation
...
- This NPE happened when starting the DomR and its Volume's podId was null.
- This case should never happen that podId of a Volume is null.
- It looks like this is a side-effect of some other bug- most likely another DomR and basic networking issue (9578)
- While reviewing this bug, found out that we need not use the RecreateHostAllocator anymore. Using it actually is not good, since this allocator ignores what is passed to it in the plan by the DeploymentPlanner and lists pods once again.
- Changed components.xml to use FirstFitRoutingAllocator instead.
2011-04-27 11:56:05 -07:00
c909057b90
bug 9595 : Negative resource counts exception when destroying VM account
...
Avoiding double decrement for same VM instance
2011-04-27 23:40:04 +05:30
alena
David Nalley
kishan
nit
Jessica Wang
prachi
Alex Huang
Edison Su
anthony
Kelven Yang
will
keshav
Frank
Murali Reddy