Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 630B299A9 for ; Tue, 14 May 2013 10:05:19 +0000 (UTC) Received: (qmail 63827 invoked by uid 500); 14 May 2013 10:05:19 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 63690 invoked by uid 500); 14 May 2013 10:05:19 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 63615 invoked by uid 500); 14 May 2013 10:05:16 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 63609 invoked by uid 99); 14 May 2013 10:05:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 May 2013 10:05:16 +0000 Date: Tue, 14 May 2013 10:05:16 +0000 (UTC) From: "Rajesh Battala (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CLOUDSTACK-2398) [Automation] SSVM test "/usr/local/cloud/systemvm/ssvm-check.sh" failed with permission error MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-2398. ---------------------------------------- Resolution: Won't Fix > [Automation] SSVM test "/usr/local/cloud/systemvm/ssvm-check.sh" failed with permission error > ---------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-2398 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2398 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Template > Affects Versions: 4.2.0 > Environment: Master branch build > KVM > Reporter: Rayees Namathponnan > Assignee: Rajesh Battala > Priority: Blocker > Fix For: 4.2.0 > > > Step 1 : Create build from master branch and configure advanced zone > Step 2 : Login to SSVM and run the scipt "/usr/local/cloud/systemvm/ssvm-check.sh" > Result : > SSVM test failed with permission error > root@s-83-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh > ================================================ > First DNS server is 10.223.110.254 > PING 10.223.110.254 (10.223.110.254): 56 data bytes > 64 bytes from 10.223.110.254: icmp_seq=0 ttl=61 time=1.223 ms > 64 bytes from 10.223.110.254: icmp_seq=1 ttl=61 time=1.029 ms > --- 10.223.110.254 ping statistics --- > 2 packets transmitted, 2 packets received, 0% packet loss > round-trip min/avg/max/stddev = 1.029/1.126/1.223/0.097 ms > Good: Can ping DNS server > ================================================ > Good: DNS resolves download.cloud.com > ================================================ > NFS is currently mounted > Mount point is /var/lib/nfs/rpc_pipefs > touch: cannot touch `/var/lib/nfs/rpc_pipefs/foo': Permission denied > ERROR: Cannot write to mount point > You need to export with norootsquash > Mount point is /mnt/SecStorage/f075e82d-2e08-36c6-b6ba-25b692666b98 > Good: Can write to mount point > ================================================ > Management server is 10.223.49.195. Checking connectivity. > Good: Can connect to management server port 8250 > ================================================ > Good: Java process is running > ================================================ > Tests Complete. Look for ERROR or WARNING above. > root@s-83-VM:~# > Note : > > SSVM test cases failing due to this > >This test case passed on May 4th build > > This environement created with latest available template in Jenkins.cloudstack.org -- 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