[jira] [Created] (CLOUDSTACK-8684) Upgrade from 4.3.1 to 4.5.1 does not update resource for existing XenServer 6.0.2 hosts
Carlos Reategui created CLOUDSTACK-8684: --- Summary: Upgrade from 4.3.1 to 4.5.1 does not update resource for existing XenServer 6.0.2 hosts Key: CLOUDSTACK-8684 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8684 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Upgrade Affects Versions: 4.5.1 Environment: I was upgrading from ACS 4.3.1 to 4.5.1. Hosts are running XenServer 6.0.2 Reporter: Carlos Reategui 4.5.1 got rid of the specific XS 6.0.2 resource since it was the same as the 6.0 one. However the upgrade script does not update the resource column in the host table for pre-existing entries that still point to the old 602 resource. Change was done here: https://github.com/apache/cloudstack/commit/81c5e184ba998a6ccd75dfffad32cbe5dbc8c2ec The error I got after upgrade was: 2015-07-28 00:00:43,097 WARN [c.c.r.DiscovererBase] (ClusteredAgentManager Timer:ctx-ac79289c) Unable to find class com.cloud.hypervisor.xenserver.resource.XenServer602Resource java.lang.ClassNotFoundException: com.cloud.hypervisor.xenserver.resource.XenServer602Resource -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7674) Upgrade to 4.3.1 did not update broadcast_uri in networks table for basic zone type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161537#comment-14161537 ] Carlos Reategui commented on CLOUDSTACK-7674: - Not sure that will fix my problem. My vlan table got updated properly by this code. The problem was the networks table. from my prior backup: INSERT INTO `vlan` VALUES (1,'5ebc3075-2946-4be4-9e7a-f32a86e7edfc','untagged','172.30.45.1','255.255.255.0','172.30.45.100-172.30.45.174','DirectAttached',1,204,200,NULL,NULL,NULL); after update: INSERT INTO `vlan` VALUES (1,'5ebc3075-2946-4be4-9e7a-f32a86e7edfc','vlan://untagged','172.30.45.1','255.255.255.0','172.30.45.100-172.30.45.174','DirectAttached',1,204,200,NULL,NULL,NULL); As you can see the vlan_id got updated properly. The problem for me was that the broadcast_uri for the guest network in the `networks` table stayed NULL. > Upgrade to 4.3.1 did not update broadcast_uri in networks table for basic > zone type > --- > > Key: CLOUDSTACK-7674 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7674 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Upgrade >Affects Versions: 4.3.1 > Environment: CS Manager on Ubuntu 12.04 from standard repo > Hosts: XenServer 6.0.2 > Zone: Basic > Network Offering: DefaultSharedNetworkOffering >Reporter: Carlos Reategui >Priority: Critical > > In previous versions, the broadcast_uri in the Networks table was NULL for > Guest network in a Basic Zone with a network offering of > DefaultSharedNetworkOffering. From 4.3.1 (maybe 4.3.0 too but not sure) it > can not be NULL and must be set to "vlan://untagged". The upgrade scripts do > not do this and therefore one is unable to create new instances. > I don't know if this affect other hypervisors besides XenServer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7674) Upgrade to 4.3.1 did not update broadcast_uri in networks table for basic zone type
Carlos Reategui created CLOUDSTACK-7674: --- Summary: Upgrade to 4.3.1 did not update broadcast_uri in networks table for basic zone type Key: CLOUDSTACK-7674 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7674 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, Upgrade Affects Versions: 4.3.1 Environment: CS Manager on Ubuntu 12.04 from standard repo Hosts: XenServer 6.0.2 Zone: Basic Network Offering: DefaultSharedNetworkOffering Reporter: Carlos Reategui In previous versions, the broadcast_uri in the Networks table was NULL for Guest network in a Basic Zone with a network offering of DefaultSharedNetworkOffering. From 4.3.1 (maybe 4.3.0 too but not sure) it can not be NULL and must be set to "vlan://untagged". The upgrade scripts do not do this and therefore one is unable to create new instances. I don't know if this affect other hypervisors besides XenServer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7405) ec2 metadata service requires trailing / for listing items
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109271#comment-14109271 ] Carlos Reategui commented on CLOUDSTACK-7405: - I sent this to the dev list but thought I should include here too: Here are examples comparing released 4.3 vs AWS EC2 (I am also including the headers and in the case of user-data only the headers): ACS 4.3 $ curl -I http://172.30.45.101/latest/user-data/ HTTP/1.1 404 Not Found Date: Mon, 25 Aug 2014 15:53:18 GMT Server: Apache Vary: Accept-Encoding Content-Type: text/html; charset=iso-8859-1 $ curl -I http://172.30.45.101/latest/user-data HTTP/1.1 200 OK Date: Mon, 25 Aug 2014 15:53:23 GMT Server: Apache Last-Modified: Mon, 11 Aug 2014 22:34:05 GMT ETag: "10240-0-5006227053140;500622334a140” Accept-Ranges: bytes $ curl -i http://172.30.45.101/latest/meta-data HTTP/1.1 404 Not Found Date: Mon, 25 Aug 2014 15:54:25 GMT Server: Apache Vary: Accept-Encoding Content-Length: 214 Content-Type: text/html; charset=iso-8859-1 404 Not Found Not Found The requested URL /latest/meta-data was not found on this server. $ curl -i http://172.30.45.101/latest/meta-data/ HTTP/1.1 200 OK Date: Mon, 25 Aug 2014 15:54:32 GMT Server: Apache Last-Modified: Mon, 11 Aug 2014 22:34:05 GMT ETag: "1024a-88-5006227053140;500622334a140" Accept-Ranges: bytes Content-Length: 136 service-offering availability-zone local-ipv4 local-hostname public-ipv4 public-hostname instance-id vm-id public-keys cloud-identifier $ curl -i http://172.30.45.101/latest/meta-data/local-ipv4; echo HTTP/1.1 200 OK Date: Mon, 25 Aug 2014 15:55:39 GMT Server: Apache Last-Modified: Mon, 11 Aug 2014 22:34:05 GMT ETag: "10250-d-5006227053140;500622334a140" Accept-Ranges: bytes Content-Length: 13 172.30.45.123 $ curl -i http://172.30.45.101/latest/meta-data/local-ipv4/; echo HTTP/1.1 404 Not Found Date: Mon, 25 Aug 2014 15:55:45 GMT Server: Apache Vary: Accept-Encoding Content-Length: 232 Content-Type: text/html; charset=iso-8859-1 404 Not Found Not Found The requested URL /metadata/172.30.45.123/local-ipv4/ was not found on this server. On AWS EC2 $ curl -I http://169.254.169.254/latest/user-data HTTP/1.0 200 OK Content-Type: application/octet-stream Accept-Ranges: bytes ETag: "590463714" Last-Modified: Thu, 03 Apr 2014 23:10:13 GMT Content-Length: 4790 Connection: close Date: Mon, 25 Aug 2014 15:57:15 GMT Server: EC2ws $ curl -I http://169.254.169.254/latest/user-data/ HTTP/1.0 200 OK Content-Type: application/octet-stream Accept-Ranges: bytes ETag: "590463714" Last-Modified: Thu, 03 Apr 2014 23:10:13 GMT Content-Length: 4790 Connection: close Date: Mon, 25 Aug 2014 15:57:20 GMT Server: EC2ws $ curl -i http://169.254.169.254/latest/meta-data HTTP/1.0 301 Moved Permanently Location: http://169.254.169.254/latest/meta-data/ Content-Length: 0 Connection: close Date: Mon, 25 Aug 2014 15:58:00 GMT Server: EC2ws $ curl -i http://169.254.169.254/latest/meta-data/; echo HTTP/1.0 200 OK Content-Type: text/plain Accept-Ranges: bytes ETag: "1606042795" Last-Modified: Thu, 03 Apr 2014 23:10:13 GMT Content-Length: 268 Connection: close Date: Mon, 25 Aug 2014 15:58:50 GMT Server: EC2ws ami-id ami-launch-index ami-manifest-path block-device-mapping/ hostname iam/ instance-action instance-id instance-type kernel-id local-hostname local-ipv4 mac metrics/ network/ placement/ profile public-hostname public-ipv4 public-keys/ reservation-id security-groups $ curl -i http://169.254.169.254/latest/meta-data/local-ipv4; echo HTTP/1.0 200 OK Content-Type: text/plain Accept-Ranges: bytes ETag: "916027669" Last-Modified: Thu, 03 Apr 2014 23:10:13 GMT Content-Length: 12 Connection: close Date: Mon, 25 Aug 2014 16:00:32 GMT Server: EC2ws 10.250.5.124 $ curl -i http://169.254.169.254/latest/meta-data/local-ipv4/; echo HTTP/1.0 200 OK Content-Type: text/plain Accept-Ranges: bytes ETag: "916027669" Last-Modified: Thu, 03 Apr 2014 23:10:13 GMT Content-Length: 12 Connection: close Date: Mon, 25 Aug 2014 16:00:36 GMT Server: EC2ws 10.250.5.124 > ec2 metadata service requires trailing / for listing items > -- > > Key: CLOUDSTACK-7405 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7405 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI >Reporter: Scott Moser >Priority: Minor > > This came to me through bug reports to cloud-init: > https://bugs.launchpad.net/cloud-init/+bug/1356855 > and > https://bugs.launchpad.net/cloud-init/+bug/1311107 > Apparently, the EC2 metadata service that cloudstack provides returns a 404 > for "dictionary" entries that do not have a trailing /. > Example (as reported to me, i have no first hand experience). > $ wget http://1
[jira] [Commented] (CLOUDSTACK-4778) cloudstack-sysvmadm gives an error on Ubuntu
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059980#comment-14059980 ] Carlos Reategui commented on CLOUDSTACK-4778: - also affects 4.3 > cloudstack-sysvmadm gives an error on Ubuntu > > > Key: CLOUDSTACK-4778 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4778 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Upgrade >Affects Versions: 4.2.0 >Reporter: Kirk Kosinski >Priority: Minor > Labels: ubuntu, upgrade > > When running the cloudstack-sysvmadm on a Ubuntu management server, the > following error is seen: > /usr/bin/cloudstack-sysvmadm: line 21: /etc/rc.d/init.d/functions: No such > file or directory > The script is trying to source a file (/etc/rc.d/init.d/functions) that does > not exist on Ubuntu 12.04. The script should be updated to work properly on a > Ubuntu management server. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6952) Building from Source Doc needs updating
Carlos Reategui created CLOUDSTACK-6952: --- Summary: Building from Source Doc needs updating Key: CLOUDSTACK-6952 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6952 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.4.0 Environment: Ubuntu 12.04.4 Reporter: Carlos Reategui http://cloudstack-installation.readthedocs.org/en/latest/building_from_source.html needs the following updates: Building DEB packages section: - maven 3 is now part of the standard precise repo. No need to add ppa. See http://packages.ubuntu.com/precise/maven - The pre-reqs say not to use tomcat 6.0.35 however tomcat6 default in 12.04 is currently 6.0.35. I would have edited the doc in github but wasn't sure what the preferred way to fix this one was. - change mvn3 command to mvn. assumes above change to install default rather than from ppa. - 'mvn -P deps' gave me a warning that deps profile does not exist. - 'dpkg-buildpackage -uc -us' fails tomcat6 dependency if one manually sets up tomcat 6.0.33 since dpkg doesn't know about it. Need to add -d option, however not sure how safe that is since other dependencies will not be checked. - packages are available in the parent path (i.e. ../*.deb) but the doc doesn't mention that and therefore the commands to create the apt repo won't work. Not sure if this is a difference since I built from git rather than from the tar file linked in the doc. Also should review https://github.com/apache/cloudstack/blob/4.4/INSTALL.md and make sure it is consistent with this doc and some of the above apply to it as well. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-4411) AWS API installation broken in 4.1
Carlos Reategui created CLOUDSTACK-4411: --- Summary: AWS API installation broken in 4.1 Key: CLOUDSTACK-4411 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4411 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: AWSAPI Affects Versions: 4.1.0 Environment: CS 4.1 upgraded from 4.0.2 using (deb http://cloudstack.apt-get.eu/ubuntu precise 4.1) Ubuntu 12.04 Reporter: Carlos Reategui After upgrading from 4.0.2 to 4.1 I installed aws-api with: $ apt-get install cloudstack-awsapi I ran into the following bugs in the AWS API installation: 1) Wrong permissions for awsapi log path. To fix do the following:: $ chgrp cloud /var/log/cloudstack/awsapi; $ chmod g+w /var/log/cloudstack/awsapi 2) cloud-bridge db not created: To fix I found: /usr/share/cloudstack-bridge/setup/deploy-db-bridge.sh and ran it. However it reset my cloud PW so I had to set it back to what I had for the other processes to work. 3) Can't find: crypto.properties xes.keystore Installer moved them to /etc/cloudstack/management/ so I moved them back to /usr/share/cloudstack-management/webapps7080/awsapi/WEB-INF/classes/. It now starts. 4) Can not find end point reference. I am still stuck. cloudstack-aws-api-register appears to have worked but am now getting: Jul 31, 2013 3:54:41 PM org.apache.axis2.engine.AxisEngine receive SEVERE: The service cannot be found for the endpoint reference (EPR) http://localhost:7080/awsapi/services/AmazonEC2/ -- 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
[jira] [Commented] (CLOUDSTACK-1713) EC2 REST API: AWS API Installation Problems
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726663#comment-13726663 ] Carlos Reategui commented on CLOUDSTACK-1713: - There is still a problem with this at least in the debian packaging. I had to move the xes.keystore and crypto.properties back to /usr/share/cloudstack-management/webapps7080/awsapi/WEB-INF/classes/ from /etc/cloudstack/management in order to get it to start properly. This is CS4.1 on ubuntu 12.04 installed using apt-get. I am still having some issues and maybe need to move some other files over. > EC2 REST API: AWS API Installation Problems > --- > > Key: CLOUDSTACK-1713 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1713 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.1.0, 4.2.0 >Reporter: Chandan Purushothama >Assignee: Pradeep Soundararajan >Priority: Blocker > Fix For: 4.1.0, 4.2.0 > > > Further bug report conversations of CS-1557 will be done here. Since the bug > CS-1557 was initially filed for missing cloudbridge database, I filed this > bug to keep track of other issues related to aws-api installation. -- 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
[jira] [Created] (CLOUDSTACK-3866) Upgrade 4.0 to 4.1 docs need further clarification
Carlos Reategui created CLOUDSTACK-3866: --- Summary: Upgrade 4.0 to 4.1 docs need further clarification Key: CLOUDSTACK-3866 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3866 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Carlos Reategui Section 4.1 Step 5: This is redundant. Management server was already stopped in step 2 Step 8: - .d through .h: These are only necessary on KVM hosts. Text should explain that like it does in 9.c - should add instructions to purge old cloud-client and cloud-server using dpkg --purge. - missing instruction of when it is ok to start management server that was installed in c. Step 10: This will only work if unauthenticated API interface is enabled. Should include a link to Developer Guide Section 4.3.1 to explain how to do so (http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Developers_Guide/whats-new-in-api-3.0.html#enabling-port-8096). Step 11: Add clarification that this is done on the management server. Because the note is labeled "For Xen Hosts: Copy vhd-utils" it may cause someone to think they need to do this on the hosts. -- 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
