From issues-return-89888-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org Sat Feb 10 18:34:06 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 14DC4180676 for ; Sat, 10 Feb 2018 18:34:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 04A23160C3D; Sat, 10 Feb 2018 17:34:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4FED9160C4D for ; Sat, 10 Feb 2018 18:34:05 +0100 (CET) Received: (qmail 87399 invoked by uid 500); 10 Feb 2018 17:34:04 -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 87382 invoked by uid 500); 10 Feb 2018 17:34:04 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 87379 invoked by uid 99); 10 Feb 2018 17:34:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Feb 2018 17:34:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 7B8ACC10CD for ; Sat, 10 Feb 2018 17:34:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 4jHkhoenIPD9 for ; Sat, 10 Feb 2018 17:34:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 8FF5F5FAC9 for ; Sat, 10 Feb 2018 17:34:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E5609E021A for ; Sat, 10 Feb 2018 17:34:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1C59921E84 for ; Sat, 10 Feb 2018 17:34:00 +0000 (UTC) Date: Sat, 10 Feb 2018 17:34:00 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-10243) Updating metadata might hang on VR on "ip rule show" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-10243?page=3Dcom.atl= assian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D16359546#comment-16359546 ]=20 ASF subversion and git services commented on CLOUDSTACK-10243: -------------------------------------------------------------- Commit ce67726c6d3db6e7db537e76da6217c5d5f4b10e in cloudstack's branch refs= /heads/master from [~widodh] [ https://gitbox.apache.org/repos/asf?p=3Dcloudstack.git;h=3Dce67726 ] CLOUDSTACK-10243: Do not use wait() on Python subprocess (#2421) This might (and does block) in certain situations on the VR as also explained in the Python documentation: https://docs.python.org/2/library/subprocess.html#subprocess.Popen.wait Warning This will deadlock when using stdout=3DPIPE and/or stderr=3DPIPE and the child process generates enough output to a pipe such that it blocks waiting for the OS pipe buffer to accept more data. Use communicate() to avoid that. Using the check_output function handles most of this for us and also provides better error handling. Signed-off-by: Wido den Hollander > Updating metadata might hang on VR on "ip rule show" > ---------------------------------------------------- > > Key: CLOUDSTACK-10243 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-102= 43 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the defa= ult.)=20 > Components: Virtual Router > Affects Versions: 4.10.0.0, 4.11.0.0 > Environment: CloudStack 4.10 - Basic Networking > Reporter: Wido den Hollander > Assignee: Wido den Hollander > Priority: Major > Labels: basic-networking, python, virtual-router > Fix For: Future > > > On a CloudStack 4.10 setup running with Basic Networking we noticed VMs b= eing in the "Starting" state. > After investigating in the VR we show the "ip rule show" command run for = ever and never end. This causes Python scripts to wait and thus never start= the Instance. > This seems to be a issue in=C2=A0CsHelper.py where it uses p.wait() which= might block in certain situations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)