fuel-dev team mailing list archive

Thread
Date
Re: Undeliverable: Re: Controller node ip is not pinging from Compute node

To: "Gandhirajan Mariappan (CW)" <gmariapp@xxxxxxxxxxx>
From: Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>
Date: Thu, 19 Jun 2014 11:28:42 +0400
Cc: "fuel-dev@xxxxxxxxxxxxxxxxxxx" <fuel-dev@xxxxxxxxxxxxxxxxxxx>
In-reply-to: <844268da-7000-4ade-93a5-212885bb139c@brocade.local>
Gandhirajan,
please remove DL-GRP-ENG-SQA-Open Stack <
DL-GRP-ENG-SQA-OpenStack@xxxxxxxxxxx> from CC.

Brocade network doesn't allow to post external messages to it, and when I
respond, I immediately receive the email below.

Thanks,


On Thu, Jun 19, 2014 at 11:25 AM, <postmaster@brocade.local> wrote:

>  *Delivery has failed to these recipients or groups:*
>
> DL-GRP-ENG-SQA-Open Stack (DL-GRP-ENG-SQA-OpenStack@xxxxxxxxxxx)
> <DL-GRP-ENG-SQA-OpenStack@xxxxxxxxxxx>
>  Your message can't be delivered because delivery to this address is
> restricted.
>
>
>
>
>
>
> *Diagnostic information for administrators:*
>
> Generating server: brocade.local
>
> DL-GRP-ENG-SQA-OpenStack@xxxxxxxxxxx
> #550 5.7.1 RESOLVER.RST.AuthRequired; authentication required ##
>
> Original message headers:
>
> Received: from brm-smtp03.brocade.com (172.16.180.102) by
>  BRMWP-EXCHUB02.corp.brocade.com (172.16.187.99) with Microsoft SMTP Server
>  (TLS) id 14.3.123.3; Thu, 19 Jun 2014 01:25:34 -0600
> Received: from BRMWP-PPMFA04.brocade.com ([144.49.208.41]) by
>  brm-smtp03.brocade.com with Microsoft SMTPSVC(7.5.7601.17514);	 Thu, 19 Jun
>  2014 01:25:33 -0600
> Received: from pps.filterd (BRMWP-PPMFA04.brocade.com [127.0.0.1])	by
>  BRMWP-PPMFA04.brocade.com (8.14.5/8.14.5) with SMTP id s5J7Jb4p030913	for
>  <DL-GRP-ENG-SQA-OpenStack@xxxxxxxxxxx>; Thu, 19 Jun 2014 00:25:34 -0700
> Received: from mail-vc0-x22f.google.com (mail-vc0-x22f.google.com
>  [IPv6:2607:f8b0:400c:c03::22f])	by BRMWP-PPMFA04.brocade.com with ESMTP id
>  1mkuax80b2-1	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT)	for
>  <DL-GRP-ENG-SQA-OpenStack@xxxxxxxxxxx>; Thu, 19 Jun 2014 00:25:33 -0700
> Received: by mail-vc0-f175.google.com with SMTP id hy4so1848762vcb.6
>         for <DL-GRP-ENG-SQA-OpenStack@xxxxxxxxxxx>; Thu, 19 Jun 2014 00:25:32
>  -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>         d=mirantis.com; s=google;
>         h=mime-version:in-reply-to:references:from:date:message-id:subject:to
>          :cc:content-type;
>         bh=mUoPqAnfIUX7hgRKNircLbYdp+dZFb5p2lRaT5SM3V8=;
>         b=Kp1o89FlekUFcTJNfQlKW2tdfzua+DmkBUnB5Cg9C7N2gbYNqyG3UBe3VONHmXl5q0
>          W1gwImPSG5af1tQhIEpE8BbT0aN+MyMKnf9Ob7IAvQQyNuCKutYyGkUf8N6AT9k9jSX7
>          ctm3Yj4a4Yb4bjnxYpdW/zDYh4tw2zzHrMnsY=
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>         d=1e100.net; s=20130820;
>         h=x-gm-message-state:mime-version:in-reply-to:references:from:date
>          :message-id:subject:to:cc:content-type;
>         bh=mUoPqAnfIUX7hgRKNircLbYdp+dZFb5p2lRaT5SM3V8=;
>         b=ICd1/OnRzEtNipME82i10WmgNaEbzBOZhnBHtd+pB6Y8gzqzXdlFYQxZWvt+lFUW1Q
>          PTd+9pmUGnWPKuRLnz/XMA6LsV/a2ohzbgxGqmRA+EHJIfJ2MbAUq3qiJdnHWLvaNyBO
>          UYZgqRBVD/BQJl9syuau6GD7d/Kkb12IeWzE0F8IyU9Q74pHyOIETOPCB+2LbMQpr17c
>          enV4mi2KrSnBDylkTd2PofGVp+lU9W9tSK3MU0nTpwoX8P+2qK8iz3gBykNnZPkQaOY5
>          sID8Z2qEWYlJ0GnkebTvjGg7h+ZIURUGVG3TR9DmtEGueinZpvhjIKYoE9p3bnn6AwVE
>          SuNQ==
> X-Gm-Message-State: ALoCoQnd+j8uoKMqF/4NHA8DPBAVObCvpn4h9I94Bl2261eh5kahENSwCfDnfMcN9P+oP5Bulvo+
> X-Received: by 10.52.72.39 with SMTP id a7mr2121993vdv.13.1403162732616; Thu,
>  19 Jun 2014 00:25:32 -0700 (PDT)
> MIME-Version: 1.0
> Received: by 10.220.165.9 with HTTP; Thu, 19 Jun 2014 00:25:11 -0700 (PDT)
> In-Reply-To: <A9F350798121384390EAAF5A79504CF1030389AC98@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
> References: <A9F350798121384390EAAF5A79504CF1030389AC8E@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
>  <A9F350798121384390EAAF5A79504CF1030389AC95@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
>  <CA+HkNVvnE971x76cxn0CCZvuRunRLcAempLUKCo_9bwWtgLM9g@xxxxxxxxxxxxxx> <A9F350798121384390EAAF5A79504CF1030389AC98@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
> From: Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>
> Date: Thu, 19 Jun 2014 11:25:11 +0400
> Message-ID: <CAKYN3rPRe-x-WCxcFrCT_JF4ZghRTWU4PT8Wwfbx9gY_tg=Udw@xxxxxxxxxxxxxx>
> Subject: Re: [Fuel-dev] Controller node ip is not pinging from Compute node
> To: "Gandhirajan Mariappan (CW)" <gmariapp@xxxxxxxxxxx>
> CC: Sergii Golovatiuk <sgolovatiuk@xxxxxxxxxxxx>,
> 	"fuel-dev@xxxxxxxxxxxxxxxxxxx" <fuel-dev@xxxxxxxxxxxxxxxxxxx>,
> 	DL-GRP-ENG-SQA-Open Stack <DL-GRP-ENG-SQA-OpenStack@xxxxxxxxxxx>, Prakash
>  Kaligotla <pkaligot@xxxxxxxxxxx>
> Content-Type: multipart/related; boundary="20cf307f30f63d93ee04fc2b4856"
> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52,1.0.14,0.0.0000
>  definitions=2014-06-19_01:2014-06-19,2014-06-19,1970-01-01 signatures=0
> X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=7 phishscore=0
>  adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1
>  engine=7.0.1-1402240000 definitions=main-1406190093
> Return-Path: mscherbakov@xxxxxxxxxxxx
> X-OriginalArrivalTime: 19 Jun 2014 07:25:33.0061 (UTC) FILETIME=[A7E7E350:01CF8B8F]
>
>
> Final-Recipient: rfc822;DL-GRP-ENG-SQA-OpenStack@xxxxxxxxxxx
> Action: failed
> Status: 5.7.1
> Diagnostic-Code: smtp;550 5.7.1 RESOLVER.RST.AuthRequired; authentication
> required
> X-Display-Name: DL-GRP-ENG-SQA-Open Stack
>
>
>
> ---------- Forwarded message ----------
> From: Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>
> To: "Gandhirajan Mariappan (CW)" <gmariapp@xxxxxxxxxxx>
> Cc: Sergii Golovatiuk <sgolovatiuk@xxxxxxxxxxxx>, "
> fuel-dev@xxxxxxxxxxxxxxxxxxx" <fuel-dev@xxxxxxxxxxxxxxxxxxx>,
> DL-GRP-ENG-SQA-Open Stack <DL-GRP-ENG-SQA-OpenStack@xxxxxxxxxxx>,
> "Prakash Kaligotla" <pkaligot@xxxxxxxxxxx>
> Date: Thu, 19 Jun 2014 11:25:11 +0400
> Subject: Re: [Fuel-dev] Controller node ip is not pinging from Compute node
> There is no need to tweak configuration to get "nova hypervisor-list"
> output. As I just replied in another thread, it works by default. Please
> try it on Vbox to confirm.
>
> According to your email, you have issues with networking. Did you check
> your networking connectivity, especially over management network?
>
> Thanks,
>
>
> On Thu, Jun 19, 2014 at 11:03 AM, Gandhirajan Mariappan (CW) <
> gmariapp@xxxxxxxxxxx> wrote:
>
>> Hi Sergii/Miroslav,
>>
>>
>>
>> I have shared the “Diagnostic Snapshot” at
>> https://www.dropbox.com/s/79op6pi1vxe9w9l/fuel-snapshot-2014-06-19_04-40-10.tgz
>>
>>
>>
>> *Topology:*
>>
>> Our topology is like below –
>>
>> [image: cid:image007.png@01CF75CF.84E98410]
>>
>> *Query:* nova hypervisor-list is empty in compute node
>>
>>
>>
>> *Steps we tried for ‘neutron agent-list’:*
>>
>> Neutron agent-list was also not listing host-node5 (highlighted below) by
>> default. After we changed the IP address from 192.26.0.3(management
>> network) to 10.24.41.3(public network) in Compute node -> neutron.conf file
>> and restarting neutron service, node-5 agent got listed successfully.
>>
>>
>>
>> *Line modified from 192.26.0.3 to 10.24.41.3 in Compute Node-Neutron.conf
>> file:*
>>
>> connection = mysql://
>> neutron:XXqqP4LM@10.24.41.3:3306/neutron?read_timeout=60
>>
>>
>>
>> *Compute Node – neutron agent-list:*
>>
>> *root@node-6:/etc/neutron# neutron agent-list*
>>
>>
>> *+--------------------------------------+--------------------+--------+-------+----------------+*
>>
>> *| id                                   | agent_type         | host   |
>> alive | admin_state_up |*
>>
>>
>> *+--------------------------------------+--------------------+--------+-------+----------------+*
>>
>> *| 3078a077-101e-49a4-861f-6e79ced41fc6 | Metadata agent     | node-6 |
>> :-)   | True           |*
>>
>> *| 8d00c407-648f-46a2-9a17-ee575c4daf7b | DHCP agent         | node-6 |
>> :-)   | True           |*
>>
>> *| b28cfc33-a8ba-4c4c-b1f0-dbb65b6b1e2c | L3 agent           | node-6 |
>> :-)   | True           |*
>>
>> *| e44d7841-3ab8-46e2-b46e-e1bcf39785e9 | Open vSwitch agent | node-5 |
>> :-)   | True           |*
>>
>> *| eb79f92e-6fd2-4d11-9e2c-024f55353e81 | Open vSwitch agent | node-6 |
>> :-)   | True           |*
>>
>>
>> *+--------------------------------------+--------------------+--------+-------+----------------+*
>>
>>
>>
>> *Steps we tried to display compute node in ‘nova hypervisor-list’:*
>>
>> We have replaced all the references of 192.168.0.3 to 10.24.41.3 in
>> Compute node -> /etc/nova/nova.conf file.
>>
>> Also modified Compute node -> /etc/nova/nova-compute.conf with the below
>> lines -
>>
>>
>>
>>             *[DEFAULT]*
>>
>> *compute_driver=libvirt.LibvirtDriver*
>>
>> *#sql_connection=mysql://nova:gfW4v98X@10.24.41.3/nova?charset=utf8
>> <http://nova:gfW4v98X@10.24.41.3/nova?charset=utf8>*
>>
>> *#sql_connection=mysql://nova:gfW4v98X@10.24.41.3/nova?read_timeout=60
>> <http://nova:gfW4v98X@10.24.41.3/nova?read_timeout=60>*
>>
>> *sql_connection=mysql://nova:gfW4v98X@10.24.41.3/nova?read_timeout=60
>> <http://nova:gfW4v98X@10.24.41.3/nova?read_timeout=60>*
>>
>> *#neutron_url=http://10.24.41.3:9696 <http://10.24.41.3:9696>*
>>
>> *neutron_url=http://10.24.41.3:9696 <http://10.24.41.3:9696>*
>>
>> *neutron_admin_username=neutron*
>>
>> *#neutron_admin_password=password*
>>
>> *neutron_admin_password=TdvGnCTq*
>>
>> *neutron_admin_tenant_name=services*
>>
>> *neutron_region_name=RegionOne*
>>
>> *#neutron_admin_auth_url=http://10.24.41.3:35357/v2.0
>> <http://10.24.41.3:35357/v2.0>*
>>
>> *neutron_admin_auth_url=http://10.24.41.3:35357/v2.0
>> <http://10.24.41.3:35357/v2.0>*
>>
>> *neutron_auth_strategy=keystone*
>>
>> *security_group_api=neutron*
>>
>> *debug=True*
>>
>> *verbose=True*
>>
>> *connection_type=libvirt*
>>
>> *network_api_class=nova.network.neutronv2.api.API*
>>
>> *libvirt_use_virtio_for_bridges=True*
>>
>> *neutron_default_tenant_id=default*
>>
>> *rabbit_userid=nova*
>>
>> *rabbit_password=WENFYGnk*
>>
>>
>>
>> *[libvirt]*
>>
>> *virt_type=kvm*
>>
>> *compute_driver=libvirt.LibvirtDriver*
>>
>> *libvirt_ovs_bridge=br-int*
>>
>> *libvirt_vif_type=ethernet*
>>
>> *libvirt_vif_driver=nova.virt.libvirt.vif.NeutronLinuxBridgeVIFDriver*
>>
>>
>>
>> Thanks and Regards,
>>
>> Gandhi Rajan
>>
>>
>>
>> *From:* Sergii Golovatiuk [mailto:sgolovatiuk@xxxxxxxxxxxx]
>> *Sent:* Wednesday, June 18, 2014 8:18 PM
>> *To:* Gandhirajan Mariappan (CW)
>> *Cc:* fuel-dev@xxxxxxxxxxxxxxxxxxx; Miroslav Anashkin;
>> DL-GRP-ENG-SQA-Open Stack; Prakash Kaligotla
>> *Subject:* Re: [Fuel-dev] Controller node ip is not pinging from Compute
>> node
>>
>>
>>
>> Hi Gandhirajan,
>>
>> From your email it's not clear a topology your have. I am kindly asking
>> to create "Diagnostic snapshot" so we'll be able to analyze it. The link
>> below will help you with the process
>>
>>
>> https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Test_and_report_bugs
>>
>> Thank you.
>>
>> --
>> Mailing list: https://launchpad.net/~fuel-dev
>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~fuel-dev
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Mike Scherbakov
> #mihgen
>
>
>


-- 
Mike Scherbakov
#mihgen
References

Controller node ip is not pinging from Compute node
From: Gandhirajan Mariappan (CW), 2014-06-17
Re: Controller node ip is not pinging from Compute node
From: Gandhirajan Mariappan (CW), 2014-06-18
Re: Controller node ip is not pinging from Compute node
From: Sergii Golovatiuk, 2014-06-18
Re: Controller node ip is not pinging from Compute node
From: Gandhirajan Mariappan (CW), 2014-06-19
Re: Controller node ip is not pinging from Compute node
From: Mike Scherbakov, 2014-06-19