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 30925109D9 for ; Fri, 9 Aug 2013 09:40:50 +0000 (UTC) Received: (qmail 50293 invoked by uid 500); 9 Aug 2013 09:40:49 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 50273 invoked by uid 500); 9 Aug 2013 09:40:48 -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 50258 invoked by uid 500); 9 Aug 2013 09:40:48 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 50249 invoked by uid 99); 9 Aug 2013 09:40:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Aug 2013 09:40:48 +0000 Date: Fri, 9 Aug 2013 09:40:48 +0000 (UTC) From: "Jayapal Reddy (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-4184) VM password reset works inconsistently 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-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734595#comment-13734595 ] Jayapal Reddy commented on CLOUDSTACK-4184: ------------------------------------------- Tried with the parallel vm deployment, It is reproduced for me. Deployed VMs by hitting enter many times on browser URL bar with below API. http://localhost:8096/client/api?command=deployVirtualMachine&zoneId=6505bbdd-1916-4da1-91c9-f6cae36472e9&templateId=560f9436-a5dd-4905-895e-9407e82263ab&hypervisor=XenServer&serviceOfferingId=dc53a8fb-2b3c-4c95-acef-42e3d9c386f8&networkIds=4c479909-fed1-4338-9d0d-f6159d6a9d5e&response=json&account=admin&domainid=1 Please see attached serve_password.sh debug logs after all vms started. | instance_name | private_ip_address | +---------------+--------------------+ | i-2-103-QA | 10.1.1.148 | | i-2-105-QA | 10.1.1.56 | | i-2-107-QA | 10.1.1.93 | | i-2-108-QA | 10.1.1.125 | | i-2-109-QA | 10.1.1.43 | | i-2-110-QA | 10.1.1.63 | | i-2-111-QA | 10.1.1.150 | | i-2-112-QA | 10.1.1.95 | | i-2-113-QA | 10.1.1.209 | | i-2-114-QA | 10.1.1.195 | | i-2-115-QA | 10.1.1.179 | | i-2-117-QA | 10.1.1.239 | | i-2-118-QA | 10.1.1.121 | | i-2-119-QA | 10.1.1.130 | | i-2-120-QA | 10.1.1.154 | | i-2-121-QA | 10.1.1.144 | | i-2-122-QA | 10.1.1.45 | | i-2-123-QA | 10.1.1.23 | | i-2-124-QA | 10.1.1.185 | | i-2-125-QA | 10.1.1.140 | +---------------+--------------------+ root@r-85-QA:~# cat /var/cache/cloud/passwords 10.1.1.93=bS9smbbhc 10.1.1.125=tK3pbmvtq 10.1.1.43=mK2jgiggq 10.1.1.63=iX9uneamd 10.1.1.150=eE8ttqfzf 10.1.1.95=sF6tdkvby 10.1.1.195=eH4izxkak 10.1.1.209=dY6zamgjj 10.1.1.130=bW3zhzzev 10.1.1.121=fG3bgtnbd 10.1.1.239=gS9yjxdxs 10.1.1.120=hT6nznqdu 10.1.1.179=mK7jmjbnd 10.1.1.140=pR6ngtxpg 10.1.1.185=hY3zzixzb 10.1.1.23=uM7jnenfj 10.1.1.45=iD6kpzqjm 10.1.1.144=cX6fvpdvg 10.1.1.154=qB6jutuak In VM boot log success case: Starting cloud-set-guest-password: Changing password for user root. passwd: all authentication tokens updated successfully. --2013-08-09 00:46:17-- http://10.1.1.1:8080/ Connecting to 10.1.1.1:8080... connected. HTTP request sent, awaiting response... 200 No headers, assuming HTTP/0.9 Length: unspecified Saving to: `STDOUT' [<=> ] 0 --.-K/s saved_password [ <=> ] 16 --.-K/s in 0s 2013-08-09 00:46:17 (1.53 MB/s) - `-' saved [16] [ OK ] > VM password reset works inconsistently > -------------------------------------- > > Key: CLOUDSTACK-4184 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4184 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Virtual Router > Affects Versions: 4.2.0 > Reporter: Jayapal Reddy > Priority: Blocker > Fix For: 4.2.0 > > > 1. When password reset fails for one vm then password reset is not working then on. > 2. In router the password entries are made properly. > 3. serve password script is giving the password correctly but the vm did not recieved it > Here are the logs: > === serve_password.sh debug logs > + PASSWD_FILE=/var/cache/cloud/passwords > + ip=10.1.1.143 > + logger -t cloud 'serve_password called to service a request for 10.1.1.143.' > + read input > + '[' 'GET / HTTP/1.0' == '' ']' > ++ sed 's/^[ \t]*//' > ++ cut -d: -f2 > ++ grep DomU_Request: > ++ echo GET / HTTP/1.0 > + request= > + '[' '' '!=' '' ']' > + read input > + '[' 'User-Agent: Wget/1.11.4 Red Hat modified' == '' ']' > ++ sed 's/^[ \t]*//' > ++ cut -d: -f2 > ++ grep DomU_Request: > ++ echo User-Agent: Wget/1.11.4 Red Hat modified > + request= > + '[' '' '!=' '' ']' > + read input > + '[' 'Accept: */*' == '' ']' > ++ sed 's/^[ \t]*//' > ++ cut -d: -f2 > ++ grep DomU_Request: > ++ echo Accept: redundant_router/arping_gateways.sh.templ redundant_router/backup.sh.templ redundant_router/check_bumpup.sh redundant_router/check_heartbeat.sh.templ redundant_router/checkrouter.sh.templ redundant_router/conntrackd.conf.templ redundant_router/disable_pubip.sh redundant_router/enable_pubip.sh.templ redundant_router/fault.sh.templ redundant_router/heartbeat.sh.templ redundant_router/keepalived.conf.templ redundant_router/master.sh.templ redundant_router/primary-backup.sh.templ redundant_router/services.sh > + request= > + '[' '' '!=' '' ']' > + read input > + '[' 'Host: 10.1.1.1:8080' == '' ']' > ++ sed 's/^[ \t]*//' > ++ cut -d: -f2 > ++ grep DomU_Request: > ++ echo Host: 10.1.1.1:8080 > + request= > + '[' '' '!=' '' ']' > + read input > + '[' 'Connection: Keep-Alive' == '' ']' > ++ sed 's/^[ \t]*//' > ++ cut -d: -f2 > ++ grep DomU_Request: > ++ echo Connection: Keep-Alive > + request= > + '[' '' '!=' '' ']' > + read input > + '[' 'DomU_Request: send_my_password' == '' ']' > ++ sed 's/^[ \t]*//' > ++ cut -d: -f2 > ++ grep DomU_Request: > ++ echo DomU_Request: send_my_password > + request=send_my_password > + '[' send_my_password '!=' '' ']' > + break > + '[' send_my_password == send_my_password ']' > ++ get_value /var/cache/cloud/passwords 10.1.1.143 > ++ local filename=/var/cache/cloud/passwords > ++ local keyname=10.1.1.143 > ++ cut -d= -f2 > ++ grep -i 10.1.1.143= /var/cache/cloud/passwords > + password=bG9wrskhw > + '[' bG9wrskhw == '' ']' > + logger -t cloud 'serve_password sent a password to 10.1.1.143.' > + echo bG9wrskhw > bG9wrskhw > + unlock_exit 0 passwdlock 1 > + releaseLockFile passwdlock 1 > + __LOCKDIR=/tmp > + __LOCKFILE='/tmp/*-29091-passwdlock.lock' > + __locked=1 > + '[' 1 == 1 ']' > + rm /tmp/1375947770244011718-29091-passwdlock.lock > + exit 0 > ^C > root@r-36-QA:~# ps aux | grep socat > root 29139 0.0 0.8 4788 1024 pts/0 S 07:42 0:00 socat -lf /var/log/cloud.log TCP4-LISTEN:8080,reuseaddr,crnl,bind=10.1.1.1 SYSTEM:/opt/cloud/bin/serve_password.sh "$SOCAT_PEERADDR" > root 29141 0.0 0.6 3796 804 pts/0 S+ 07:43 0:00 grep socat > root@r-36-QA:~# > ====== Guest vm cloud-set-guest-password script logs > PASSWORD_SERVER_IP=10.1.1.1 > + '[' -n 10.1.1.1 ']' > + logger -t cloud 'Found password server IP 10.1.1.1 in /var/lib/dhclient/dhclient-eth0.leases' > + logger -t cloud 'Sending request to password server at 10.1.1.1' > ++ wget -q -t 3 -T 20 -O - --header 'DomU_Request: send_my_password' 10.1.1.1:8080 > + password= > ++ echo > ++ tr -d '\r' > + password= > + '[' 0 -eq 0 ']' > + logger -t cloud 'Got response from server at 10.1.1.1' > + case $password in > + logger -t cloud 'Password server at 10.1.1.1 did not have any password for the VM' > + continue > + for DHCP_FILE in '$DHCP_FOLDERS' > + '[' -f '/var/lib/dhcp3/*' ']' > + '[' 0 == 0 ']' > + '[' 0 == 1 ']' > + logger -t cloud 'Did not need to change password.' > + exit 0 > [root@v3 init.d]# -- 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