From 46bc03a96fe3d4e8b8a4a1ebd4d227d9aa925ac0 Mon Sep 17 00:00:00 2001 From: Joe Brockmeier Date: Fri, 19 Apr 2013 16:47:57 -0500 Subject: [PATCH] Adding to known issues, this should be finished now. --- docs/en-US/Release_Notes.xml | 646 +++++++++++++++++++++++++++++++---- 1 file changed, 571 insertions(+), 75 deletions(-) diff --git a/docs/en-US/Release_Notes.xml b/docs/en-US/Release_Notes.xml index d46339b19f5..181bb071806 100644 --- a/docs/en-US/Release_Notes.xml +++ b/docs/en-US/Release_Notes.xml @@ -4120,6 +4120,502 @@ under the License. console proxy does not support any keymaps besides us, jp + + + CLOUDSTACK-77 + + + console proxy display issues + + + + + CLOUDSTACK-79 + + + CloudStack 3.0.4: firewall rules not restored on KVM host + + + + + CLOUDSTACK-105 + + + /tmp/stream-unix.####.###### stale sockets causing inodes to run out on Xenserver + + + + + CLOUDSTACK-107 + + + Network domain guest suffix is not getting programmed as part of hostnames on Guest VMs that are part of Isolated and Shared Guest Networks + + + + + CLOUDSTACK-133 + + + Multiple DHCP Servers are being created on the shared network on using multiple Network Ranges from the same shared network. + + + + + CLOUDSTACK-155 + + + HA checks lead to unnecessary Compute Node reboot when Primary Storage is in Maintenance Mode + + + + + CLOUDSTACK-187 + + + CloudStack reports incorrect CPU & RAM usage values for hosts in Basic zone + + + + + CLOUDSTACK-207 + + + "listCapacity API is not able to list clusterwide capacities when used with "sortby=Usage" parameter" + + + + + CLOUDSTACK-234 + + + create/delete firewa/lb/pf rule: send ip assoc command just for the IP for which you are creating the rule + + + + + CLOUDSTACK-236 + + + Network Offering IDs are being exposed to the Regular User Account in the UpdateNetworkCmd Error message + + + + + CLOUDSTACK-237 + + + StopVMCommand reported success in spite of failing to stop a VM which got stuck during installation from an ISO + + + + + CLOUDSTACK-238 + + + vpn:fail to connect to vpnserver using non-sourceNAT IP + + + + + CLOUDSTACK-242 + + + haproxy listens on all interfaces on VR + + + + + CLOUDSTACK-243 + + + "On management server, security for remote JMX connections is disabled" + + + + + CLOUDSTACK-244 + + + RPC port on SSVM is open on all interfaces + + + + + CLOUDSTACK-252 + + + "UpdateNetwork Operation on a guest network that is currently using Virtual Router for Lb services to a network offering that uses "F5" for Lb services Fails due to MySQLIntegrityConstraintViolationException." + + + + + CLOUDSTACK-255 + + + Null pointer exception while creating portforwarding rule after performing UpdateNetworkCmd + + + + + CLOUDSTACK-272 + + + Delete failure message for network with a VM is not informative + + + + + CLOUDSTACK-280 + + + Exception thrown on going to Step 5 of Add VM Instance - CloudRuntimeException: Tags are not defined for physical network in the zone id=1 + + + + + CLOUDSTACK-281 + + + "On Updating the VMWare Traffic Labels of existing Physical Networks to Invalid Values; Triggering a ReconnectHost Command, successfully reconnected the ESXi host instead of reporting an Alert" + + + + + CLOUDSTACK-298 + + + putting host in maintenance mode while creating snapshot ,host resorce state stuck in "ErrorInMaintenance mode" and snapshot creation fail Unable to migrate due to Requested operation is not valid: cannot migrate domain with 1 snapshots + + + + + CLOUDSTACK-305 + + + AWS APi - "Rolling back the transaction" seen in management server logs , everytime a soap call is made. + + + + + CLOUDSTACK-308 + + + ec2-describe-instances - Instance type is always retuned as "m1.small" + + + + + CLOUDSTACK-310 + + + Failed to add host - Plugin error + + + + + CLOUDSTACK-324 + + + "Cannot edit default security group rules, default security group blocks all inbound traffic." + + + + + CLOUDSTACK-338 + + + Unique Names of Disk and Service Offerings in the database are prefixed with "Cloud.com" String + + + + + CLOUDSTACK-425 + + + Check image type is qcow2 before actually installing + + + + + CLOUDSTACK-440 + + + create networks in advanced zone with out VLAN isolation + + + + + CLOUDSTACK-568 + + + Source template id is recorded incorrectly. + + + + + CLOUDSTACK-643 + + + KVM snapshots deleted on UI/API do not physically delete from secondary storage + + + + + CLOUDSTACK-797 + + + Remove or fix unknown classes in cloud-api + + + + + CLOUDSTACK-970 + + + when a template is deleted and then copied over again , it is still marked as "Removed" in template_zone_ref table. + + + + + CLOUDSTACK-989 + + + marvin: jsonHelper deserialization results in unfilled attributes + + + + + CLOUDSTACK-1007 + + + Not able to delete Shared network because of not being able to stop the router. + + + + + CLOUDSTACK-1187 + + + Handle network creation failures when persistent is set to true + + + + + CLOUDSTACK-1199 + + + External DNS not being added to reslov.conf + + + + + CLOUDSTACK-1209 + + + VPC VR starts despite NPE + + + + + CLOUDSTACK-1304 + + + "mvn -pl :cloud-client-ui jetty:run" strips permission of files in script/ + + + + + CLOUDSTACK-1352 + + + "KVM 6.3 snapshot - when snapshot of ROOT volume is being created, snapshot of data volume remains in Creating state" + + + + + CLOUDSTACK-1393 + + + Install scripts shows wrong path to copy vhd-util + + + + + CLOUDSTACK-1413 + + + Need something to concretely identify the version of the code in a particular build + + + + + CLOUDSTACK-1424 + + + Failed with NPE while deleting account when there are snapshots created for this account instances + + + + + CLOUDSTACK-1439 + + + Baremetal - UI/API security group unable to set egress rule > UI displays args.context.networks is undefined + + + + + CLOUDSTACK-1581 + + + IPV6 - UI - IPV6 DNS entries should not be exposed for Basic Zone. + + + + + CLOUDSTACK-1638 + + + Network plugins won't be notified VM migration. + + + + + CLOUDSTACK-1673 + + + AWS Regions - Events - User disable / Domain Delete event does not include the UUID of the user/domain that was disabled. + + + + + CLOUDSTACK-1717 + + + AWS Regions - Local region entry that gets added by default should not include "/api" for its end_point.Also the endpoint should have the actual hostname instead of localhost." + + + + + CLOUDSTACK-1752 + + + IPV6 - Router of a ipv6 network has external ipv4 dns entries programmed in /etc/resolv.conf + + + + + CLOUDSTACK-1758 + + + CloudPlatform CS-17541 SSVM test cases failing in VMware with 4.1 builds + + + + + CLOUDSTACK-1771 + + + "IPv6 - Network restart for a dual network , results in the ipv4 address of the router to be changed. After netwpork restart , name resolution of the Vms fail." + + + + + CLOUDSTACK-1775 + + + "AWS Regions - Events Framework - Events relating to User/Domain/Account are not being published to the RabbitMQ server expect for USER-DISABLE,DOMAIN-DELETE and ACCOUNT.DISABLE event." + + + + + CLOUDSTACK-1794 + + + We are allowed to create Egress rules for Shared networks. + + + + + CLOUDSTACK-1819 + + + AWS Regions - Issues seen when trying to move a zone from 1 region to another. + + + + + CLOUDSTACK-1868 + + + GetVmStatsCommand throws NullPointerException with VMWare + + + + + CLOUDSTACK-1885 + + + Broken testcases in 4.1 + + + + + CLOUDSTACK-1899 + + + SRX firewall external devices - static NAT does not function + + + + + CLOUDSTACK-1948 + + + users can no longer set global limits to -1 (e.g. pagesize) + + + + + CLOUDSTACK-1965 + + + 15.8. External Firewalls and Load Balancers Section is Incomplete + + + + + CLOUDSTACK-1969 + + + Ubuntu fresh Install- SystemIntegrityChecker looking for "schema-40to410.sql" wrong location and failed to start MS + + + + + CLOUDSTACK-1970 + + + Ubuntu - "cloudstack-setup-management" not available in "/usr/bin" + + + + + CLOUDSTACK-2024 + + + cloudstack-setup-management with https not works (incorrect path and missing keystore file) + + + + + CLOUDSTACK-2053 + + + [BUG] userdata.sh on router VM fixes for if else logic and missing meta-data + + @@ -4200,17 +4696,17 @@ under the License. Restart the agent: -service cloud-agent stop -killall jsvc -service cloudstack-agent start + service cloud-agent stop + killall jsvc + service cloudstack-agent start During the upgrade, log4j-cloud.xml was simply copied over, so the logs will continue to be added to /var/log/cloud/agent/agent.log. There's nothing wrong with this, but if you prefer to be consistent, you can change this by copying over the sample configuration file: -cd /etc/cloudstack/agent -mv log4j-cloud.xml.dpkg-dist log4j-cloud.xml -service cloudstack-agent restart + cd /etc/cloudstack/agent + mv log4j-cloud.xml.dpkg-dist log4j-cloud.xml + service cloudstack-agent restart @@ -4230,11 +4726,11 @@ service cloudstack-agent restart Start by opening /etc/yum.repos.d/cloudstack.repo on any systems that have &PRODUCT; packages installed. This file should have content similar to the following: -[apache-cloudstack] -name=Apache CloudStack -baseurl=http://cloudstack.apt-get.eu/rhel/4.0/ -enabled=1 -gpgcheck=0 + [apache-cloudstack] + name=Apache CloudStack + baseurl=http://cloudstack.apt-get.eu/rhel/4.0/ + enabled=1 + gpgcheck=0 If you are using the community provided package repository, change the baseurl to http://cloudstack.apt-get.eu/rhel/4.1/ If you're using your own package repository, change this line to read as appropriate for your 4.1.0 repository. @@ -4256,9 +4752,9 @@ gpgcheck=0 Restart the agent: -service cloud-agent stop -killall jsvc -service cloudstack-agent start + service cloud-agent stop + killall jsvc + service cloudstack-agent start @@ -4271,12 +4767,12 @@ service cloudstack-agent start # tail -f sysvm.log The output to sysvm.log will look something like this: -Stopping and starting 1 secondary storage vm(s)... -Done stopping and starting secondary storage vm(s) -Stopping and starting 1 console proxy vm(s)... -Done stopping and starting console proxy vm(s). -Stopping and starting 4 running routing vm(s)... -Done restarting router(s). + Stopping and starting 1 secondary storage vm(s)... + Done stopping and starting secondary storage vm(s) + Stopping and starting 1 console proxy vm(s)... + Done stopping and starting console proxy vm(s). + Stopping and starting 4 running routing vm(s)... + Done restarting router(s). @@ -4438,17 +4934,17 @@ Done restarting router(s). Restart the agent: -service cloud-agent stop -killall jsvc -service cloudstack-agent start + service cloud-agent stop + killall jsvc + service cloudstack-agent start During the upgrade, log4j-cloud.xml was simply copied over, so the logs will continue to be added to /var/log/cloud/agent/agent.log. There's nothing wrong with this, but if you prefer to be consistent, you can change this by copying over the sample configuration file: -cd /etc/cloudstack/agent -mv log4j-cloud.xml.dpkg-dist log4j-cloud.xml -service cloudstack-agent restart + cd /etc/cloudstack/agent + mv log4j-cloud.xml.dpkg-dist log4j-cloud.xml + service cloudstack-agent restart @@ -4468,11 +4964,11 @@ service cloudstack-agent restart Start by opening /etc/yum.repos.d/cloudstack.repo on any systems that have &PRODUCT; packages installed. This file should have content similar to the following: -[apache-cloudstack] -name=Apache CloudStack -baseurl=http://cloudstack.apt-get.eu/rhel/4.0/ -enabled=1 -gpgcheck=0 + [apache-cloudstack] + name=Apache CloudStack + baseurl=http://cloudstack.apt-get.eu/rhel/4.0/ + enabled=1 + gpgcheck=0 If you are using the community provided package repository, change the baseurl to http://cloudstack.apt-get.eu/rhel/4.1/ If you're using your own package repository, change this line to read as appropriate for your 4.1.0 repository. @@ -4494,9 +4990,9 @@ gpgcheck=0 Restart the agent: -service cloud-agent stop -killall jsvc -service cloudstack-agent start + service cloud-agent stop + killall jsvc + service cloudstack-agent start @@ -4968,17 +5464,17 @@ service cloudstack-agent start Restart the agent: -service cloud-agent stop -killall jsvc -service cloudstack-agent start + service cloud-agent stop + killall jsvc + service cloudstack-agent start During the upgrade, log4j-cloud.xml was simply copied over, so the logs will continue to be added to /var/log/cloud/agent/agent.log. There's nothing wrong with this, but if you prefer to be consistent, you can change this by copying over the sample configuration file: -cd /etc/cloudstack/agent -mv log4j-cloud.xml.dpkg-dist log4j-cloud.xml -service cloudstack-agent restart + cd /etc/cloudstack/agent + mv log4j-cloud.xml.dpkg-dist log4j-cloud.xml + service cloudstack-agent restart @@ -4998,11 +5494,11 @@ service cloudstack-agent restart Start by opening /etc/yum.repos.d/cloudstack.repo on any systems that have &PRODUCT; packages installed. This file should have content similar to the following: -[apache-cloudstack] -name=Apache CloudStack -baseurl=http://cloudstack.apt-get.eu/rhel/4.0/ -enabled=1 -gpgcheck=0 + [apache-cloudstack] + name=Apache CloudStack + baseurl=http://cloudstack.apt-get.eu/rhel/4.0/ + enabled=1 + gpgcheck=0 If you are using the community provided package repository, change the baseurl to http://cloudstack.apt-get.eu/rhel/4.1/ If you're using your own package repository, change this line to read as appropriate for your 4.1.0 repository. @@ -5024,9 +5520,9 @@ gpgcheck=0 Restart the agent: -service cloud-agent stop -killall jsvc -service cloudstack-agent start + service cloud-agent stop + killall jsvc + service cloudstack-agent start @@ -5747,31 +6243,31 @@ service cloudstack-agent start deleteUser New response parameters: displaytext, success - - - listVlanIpRanges - New response parameters: endipv6, ip6cidr, ip6gateway, startipv6 - - - updateNetworkOffering - New response parameters: ispersistent - - - listVpnUsers - New response parameters: state - - - listUsers - New response parameters: iscallerchilddomain - - - listIsos - New response parameters: sshkeyenabled - - - - - + + + listVlanIpRanges + New response parameters: endipv6, ip6cidr, ip6gateway, startipv6 + + + updateNetworkOffering + New response parameters: ispersistent + + + listVpnUsers + New response parameters: state + + + listUsers + New response parameters: iscallerchilddomain + + + listIsos + New response parameters: sshkeyenabled + + + + - - + + +