[Openstack] havana dhcp issue

[Paras pradhan]

Hi,

I gpt an instance UP but it doesnot get an IP address. neutron agent-list
lists DHCP agent happy. While booting I see cirros stuck at sending
discover... multiple times. dnsmasq process is running. how do i debug?

Thanks
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] havana dhcp issue

[Paras pradhan]

dnsmaq is running, ip netns doesn't return anything.

-Paras.


On Fri, Nov 8, 2013 at 4:07 PM, Rami Vaknin  wrote:

>  On 11/08/2013 11:35 PM, Paras pradhan wrote:
>
> Hi,
>
>  I gpt an instance UP but it doesnot get an IP address. neutron
> agent-list lists DHCP agent happy. While booting I see cirros stuck at
> sending discover... multiple times. dnsmasq process is running. how do i
> debug?
>
>
> I would start with:
> * ps -efl | grep dnsmasq | grep -v grep - to verify that the dnsmasq
> process is running, you can also check the conf file appeas in this output
> * ip netns - to get the list of namespaces
> * ip netns exec  tcpdump -i any ... - to
> look for the dhcp offer or arp issues
> * ping each other - instance to dhcp address, and vice versa (the second
> one should be done from within the namespace)
>
>
>  Thanks
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
> --
>
> Thanks,
>
> Rami Vaknin, QE @ Red Hat, TLV, IL.
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] havana dhcp issue

[Paras pradhan]

use_namespace is set to true, iproute is up to date from 12.04 LTS.

This is what I see when tcpdump
-

root@havana:/home/localadmin# tcpdump -i qvo6157a9aa-76
tcpdump: WARNING: qvo6157a9aa-76: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on qvo6157a9aa-76, link-type EN10MB (Ethernet), capture size
65535 bytes
16:46:39.006180 IP6 fe80::40fa:38ff:fee3:a3fa > ff02::16: HBH ICMP6,
multicast listener report v2, 1 group record(s), length 28
16:46:39.784902 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2,
1 group record(s), length 28
16:46:39.824273 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from fa:16:3e:9a:38:1e (oui Unknown), length 280
16:46:39.933463 IP6 :: > ff02::1:ff9a:381e: ICMP6, neighbor solicitation,
who has fe80::f816:3eff:fe9a:381e, length 24
16:46:40.325389 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2,
1 group record(s), length 28
16:46:40.934808 IP6 fe80::f816:3eff:fe9a:381e > ip6-allrouters: ICMP6,
router solicitation, length 16
16:46:42.833239 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from fa:16:3e:9a:38:1e (oui Unknown), length 280
16:46:44.936871 IP6 fe80::f816:3eff:fe9a:381e > ip6-allrouters: ICMP6,
router solicitation, length 16
16:46:45.840668 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from fa:16:3e:9a:38:1e (oui Unknown), length 280
16:46:48.945478 IP6 fe80::f816:3eff:fe9a:381e > ip6-allrouters: ICMP6,
router solicitation, length 16
16:47:00.542029 IP 0.0.0.0 > all-systems.mcast.net: igmp query v2
16:47:00.542036 IP6 fe80::d894:29ff:fe08:5ec > ip6-allnodes: HBH ICMP6,
multicast listener querymax resp delay: 1 addr: ::, length 24
--

Thanks!
Paras.



On Fri, Nov 8, 2013 at 4:26 PM, Rami Vaknin  wrote:

>  On 11/09/2013 12:18 AM, Paras pradhan wrote:
>
> dnsmaq is running, ip netns doesn't return anything.
>
>
> Empty output from "ip netns" can be either not using namespaces (run grep
> "use_namespaces /etc/neutron/l3_agent.ini" to find out) or using wrong
> iproute package.
> Could you please also check what does tcpdump report? could you see the
> discover on the dhcp nic (when using ovs it's a tap-xx nic)? could
> you see an offer sent from that nic?
>
>
>
>  -Paras.
>
>
> On Fri, Nov 8, 2013 at 4:07 PM, Rami Vaknin  wrote:
>
>>  On 11/08/2013 11:35 PM, Paras pradhan wrote:
>>
>> Hi,
>>
>>  I gpt an instance UP but it doesnot get an IP address. neutron
>> agent-list lists DHCP agent happy. While booting I see cirros stuck at
>> sending discover... multiple times. dnsmasq process is running. how do i
>> debug?
>>
>>
>>  I would start with:
>> * ps -efl | grep dnsmasq | grep -v grep - to verify that the dnsmasq
>> process is running, you can also check the conf file appeas in this output
>> * ip netns - to get the list of namespaces
>> * ip netns exec  tcpdump -i any ... - to
>> look for the dhcp offer or arp issues
>> * ping each other - instance to dhcp address, and vice versa (the second
>> one should be done from within the namespace)
>>
>>
>>  Thanks
>>
>>
>> ___
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>>
>> --
>>
>> Thanks,
>>
>> Rami Vaknin, QE @ Red Hat, TLV, IL.
>>
>>
>
>
> --
>
> Thanks,
>
> Rami Vaknin, QE @ Red Hat, TLV, IL.
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] havana dhcp issue

[Paras pradhan]

Yes br-tun is there.  here is the o/p of ovs-ofctl.

-
root@havana:~# ovs-ofctl show br-tun
OFPT_FEATURES_REPLY (xid=0x2): dpid:4e6501755448
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST
SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
 1(patch-int): addr:42:9d:7c:13:4b:58
 config: 0
 state:  0
 speed: 0 Mbps now, 0 Mbps max
 LOCAL(br-tun): addr:4e:65:01:75:54:48
 config: 0
 state:  0
 speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
--

Thanks
Paras.


On Sat, Nov 9, 2013 at 3:44 AM, Igor Cardoso  wrote:

> I guess br-tun is created in a single node as well, someone correct me if
> I'm wrong please.
> What is the output of ovs-ofctl show br-tun ?
>
>
> On 9 November 2013 02:35, Paras pradhan  wrote:
>
>> Yes gre . all (controller plus compute) in a single node though.
>> On Nov 8, 2013 5:17 PM, "Igor Cardoso"  wrote:
>>
>>> Are you using GRE?
>>>
>>>
>>> On 8 November 2013 22:48, Paras pradhan  wrote:
>>>
>>>> use_namespace is set to true, iproute is up to date from 12.04 LTS.
>>>>
>>>> This is what I see when tcpdump
>>>> -
>>>>
>>>> root@havana:/home/localadmin# tcpdump -i qvo6157a9aa-76
>>>> tcpdump: WARNING: qvo6157a9aa-76: no IPv4 address assigned
>>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol
>>>> decode
>>>> listening on qvo6157a9aa-76, link-type EN10MB (Ethernet), capture size
>>>> 65535 bytes
>>>> 16:46:39.006180 IP6 fe80::40fa:38ff:fee3:a3fa > ff02::16: HBH ICMP6,
>>>> multicast listener report v2, 1 group record(s), length 28
>>>> 16:46:39.784902 IP6 :: > ff02::16: HBH ICMP6, multicast listener report
>>>> v2, 1 group record(s), length 28
>>>> 16:46:39.824273 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
>>>> Request from fa:16:3e:9a:38:1e (oui Unknown), length 280
>>>> 16:46:39.933463 IP6 :: > ff02::1:ff9a:381e: ICMP6, neighbor
>>>> solicitation, who has fe80::f816:3eff:fe9a:381e, length 24
>>>> 16:46:40.325389 IP6 :: > ff02::16: HBH ICMP6, multicast listener report
>>>> v2, 1 group record(s), length 28
>>>> 16:46:40.934808 IP6 fe80::f816:3eff:fe9a:381e > ip6-allrouters: ICMP6,
>>>> router solicitation, length 16
>>>> 16:46:42.833239 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
>>>> Request from fa:16:3e:9a:38:1e (oui Unknown), length 280
>>>> 16:46:44.936871 IP6 fe80::f816:3eff:fe9a:381e > ip6-allrouters: ICMP6,
>>>> router solicitation, length 16
>>>> 16:46:45.840668 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
>>>> Request from fa:16:3e:9a:38:1e (oui Unknown), length 280
>>>> 16:46:48.945478 IP6 fe80::f816:3eff:fe9a:381e > ip6-allrouters: ICMP6,
>>>> router solicitation, length 16
>>>> 16:47:00.542029 IP 0.0.0.0 > all-systems.mcast.net: igmp query v2
>>>> 16:47:00.542036 IP6 fe80::d894:29ff:fe08:5ec > ip6-allnodes: HBH ICMP6,
>>>> multicast listener querymax resp delay: 1 addr: ::, length 24
>>>> --
>>>>
>>>> Thanks!
>>>> Paras.
>>>>
>>>>
>>>>
>>>> On Fri, Nov 8, 2013 at 4:26 PM, Rami Vaknin  wrote:
>>>>
>>>>>  On 11/09/2013 12:18 AM, Paras pradhan wrote:
>>>>>
>>>>> dnsmaq is running, ip netns doesn't return anything.
>>>>>
>>>>>
>>>>> Empty output from "ip netns" can be either not using namespaces (run
>>>>> grep "use_namespaces /etc/neutron/l3_agent.ini" to find out) or using 
>>>>> wrong
>>>>> iproute package.
>>>>> Could you please also check what does tcpdump report? could you see
>>>>> the discover on the dhcp nic (when using ovs it's a tap-xx nic)?
>>>>> could you see an offer sent from that nic?
>>>>>
>>>>>
>>>>>
>>>>>  -Paras.
>>>>>
>>>>>
>>>>> On Fri, Nov 8, 2013 at 4:07 PM, Rami Vaknin wrote:
>>>>>
>>>>>>  On 11/08/2013 11:35 PM, Paras pradhan wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>  I gpt an instance UP but it doesnot get an IP addr

Re: [Openstack] havana dhcp issue

[Paras pradhan]

I am also seeing the respawsing in syslog.

--
Nov 11 17:00:12 havana kernel: [ 1019.203880] init: neutron-dhcp-agent main
process (23258) terminated with status 1
Nov 11 17:00:12 havana kernel: [ 1019.203962] init: neutron-dhcp-agent main
process ended, respawning
Nov 11 17:00:13 havana kernel: [ 1019.818240] init: neutron-dhcp-agent main
process (23275) terminated with status 1
Nov 11 17:00:13 havana kernel: [ 1019.818266] init: neutron-dhcp-agent main
process ended, respawning
--

Paras.


On Mon, Nov 11, 2013 at 12:06 PM, Paras pradhan wrote:

> yes.
>
> ii  openvswitch-datapath-dkms1.10.2-0ubuntu2~cloud0
>Open vSwitch datapath module source - DKMS version
>
>
> Thanks
> Paras.
>
>
> On Mon, Nov 11, 2013 at 11:50 AM, Igor Cardoso wrote:
>
>> Flow gre-# is missing... Do you have openvswitch-datapath-dkms installed?
>>
>>
>> On 11 November 2013 16:24, Paras pradhan  wrote:
>>
>>> Yes br-tun is there.  here is the o/p of ovs-ofctl.
>>>
>>> -
>>> root@havana:~# ovs-ofctl show br-tun
>>> OFPT_FEATURES_REPLY (xid=0x2): dpid:4e6501755448
>>> n_tables:254, n_buffers:256
>>> capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
>>> actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC
>>> SET_DL_DST SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
>>>  1(patch-int): addr:42:9d:7c:13:4b:58
>>>  config: 0
>>>  state:  0
>>>  speed: 0 Mbps now, 0 Mbps max
>>>  LOCAL(br-tun): addr:4e:65:01:75:54:48
>>>  config: 0
>>>  state:  0
>>>  speed: 0 Mbps now, 0 Mbps max
>>> OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
>>> --
>>>
>>> Thanks
>>> Paras.
>>>
>>>
>>> On Sat, Nov 9, 2013 at 3:44 AM, Igor Cardoso wrote:
>>>
>>>> I guess br-tun is created in a single node as well, someone correct me
>>>> if I'm wrong please.
>>>> What is the output of ovs-ofctl show br-tun ?
>>>>
>>>>
>>>> On 9 November 2013 02:35, Paras pradhan  wrote:
>>>>
>>>>> Yes gre . all (controller plus compute) in a single node though.
>>>>> On Nov 8, 2013 5:17 PM, "Igor Cardoso"  wrote:
>>>>>
>>>>>> Are you using GRE?
>>>>>>
>>>>>>
>>>>>> On 8 November 2013 22:48, Paras pradhan wrote:
>>>>>>
>>>>>>> use_namespace is set to true, iproute is up to date from 12.04 LTS.
>>>>>>>
>>>>>>> This is what I see when tcpdump
>>>>>>> -
>>>>>>>
>>>>>>> root@havana:/home/localadmin# tcpdump -i qvo6157a9aa-76
>>>>>>> tcpdump: WARNING: qvo6157a9aa-76: no IPv4 address assigned
>>>>>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol
>>>>>>> decode
>>>>>>> listening on qvo6157a9aa-76, link-type EN10MB (Ethernet), capture
>>>>>>> size 65535 bytes
>>>>>>> 16:46:39.006180 IP6 fe80::40fa:38ff:fee3:a3fa > ff02::16: HBH ICMP6,
>>>>>>> multicast listener report v2, 1 group record(s), length 28
>>>>>>> 16:46:39.784902 IP6 :: > ff02::16: HBH ICMP6, multicast listener
>>>>>>> report v2, 1 group record(s), length 28
>>>>>>> 16:46:39.824273 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
>>>>>>> BOOTP/DHCP, Request from fa:16:3e:9a:38:1e (oui Unknown), length 280
>>>>>>> 16:46:39.933463 IP6 :: > ff02::1:ff9a:381e: ICMP6, neighbor
>>>>>>> solicitation, who has fe80::f816:3eff:fe9a:381e, length 24
>>>>>>> 16:46:40.325389 IP6 :: > ff02::16: HBH ICMP6, multicast listener
>>>>>>> report v2, 1 group record(s), length 28
>>>>>>> 16:46:40.934808 IP6 fe80::f816:3eff:fe9a:381e > ip6-allrouters:
>>>>>>> ICMP6, router solicitation, length 16
>>>>>>> 16:46:42.833239 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
>>>>>>> BOOTP/DHCP, Request from fa:16:3e:9a:38:1e (oui Unknown), length 280
>>>>>>> 16:46:44.936871 IP6 fe80::f816:3eff:fe9a:381e > ip6-allrouters:
>>>>>>> ICMP6, router solicitation, length 16
>>>>>>> 16:46:45.840668 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
>>>>>>> BOOTP/DHCP, Request from fa:16:3e

Re: [Openstack] havana dhcp issue

[Paras pradhan]

I figured out this issue.

by default, interface_driver =
neutron.agent.linux.interface.OVSInterfaceDriver and dhcp_driver =
neutron.agent.linux.dhcp.Dnsmasq
in dhcp_agent.ini is commented.

Also, the line interface_driver =
neutron.agent.linux.interface.OVSInterfaceDriver in l3_agent.ini is
commented.

I uncommented them and I can now see qrouter and qdhcp with 'ip netns'

All looks well now.

Thanks
Paras.



On Mon, Nov 11, 2013 at 5:01 PM, Paras pradhan wrote:

> I am also seeing the respawsing in syslog.
>
> --
> Nov 11 17:00:12 havana kernel: [ 1019.203880] init: neutron-dhcp-agent
> main process (23258) terminated with status 1
> Nov 11 17:00:12 havana kernel: [ 1019.203962] init: neutron-dhcp-agent
> main process ended, respawning
> Nov 11 17:00:13 havana kernel: [ 1019.818240] init: neutron-dhcp-agent
> main process (23275) terminated with status 1
> Nov 11 17:00:13 havana kernel: [ 1019.818266] init: neutron-dhcp-agent
> main process ended, respawning
> --
>
> Paras.
>
>
> On Mon, Nov 11, 2013 at 12:06 PM, Paras pradhan wrote:
>
>> yes.
>>
>> ii  openvswitch-datapath-dkms1.10.2-0ubuntu2~cloud0
>>Open vSwitch datapath module source - DKMS version
>>
>>
>> Thanks
>> Paras.
>>
>>
>> On Mon, Nov 11, 2013 at 11:50 AM, Igor Cardoso wrote:
>>
>>> Flow gre-# is missing... Do you have openvswitch-datapath-dkms installed?
>>>
>>>
>>> On 11 November 2013 16:24, Paras pradhan  wrote:
>>>
>>>> Yes br-tun is there.  here is the o/p of ovs-ofctl.
>>>>
>>>> -
>>>> root@havana:~# ovs-ofctl show br-tun
>>>> OFPT_FEATURES_REPLY (xid=0x2): dpid:4e6501755448
>>>> n_tables:254, n_buffers:256
>>>> capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
>>>> actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC
>>>> SET_DL_DST SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
>>>>  1(patch-int): addr:42:9d:7c:13:4b:58
>>>>  config: 0
>>>>  state:  0
>>>>  speed: 0 Mbps now, 0 Mbps max
>>>>  LOCAL(br-tun): addr:4e:65:01:75:54:48
>>>>  config: 0
>>>>  state:  0
>>>>  speed: 0 Mbps now, 0 Mbps max
>>>> OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
>>>> --
>>>>
>>>> Thanks
>>>> Paras.
>>>>
>>>>
>>>> On Sat, Nov 9, 2013 at 3:44 AM, Igor Cardoso wrote:
>>>>
>>>>> I guess br-tun is created in a single node as well, someone correct me
>>>>> if I'm wrong please.
>>>>> What is the output of ovs-ofctl show br-tun ?
>>>>>
>>>>>
>>>>> On 9 November 2013 02:35, Paras pradhan wrote:
>>>>>
>>>>>> Yes gre . all (controller plus compute) in a single node though.
>>>>>> On Nov 8, 2013 5:17 PM, "Igor Cardoso"  wrote:
>>>>>>
>>>>>>> Are you using GRE?
>>>>>>>
>>>>>>>
>>>>>>> On 8 November 2013 22:48, Paras pradhan wrote:
>>>>>>>
>>>>>>>> use_namespace is set to true, iproute is up to date from 12.04 LTS.
>>>>>>>>
>>>>>>>> This is what I see when tcpdump
>>>>>>>> -
>>>>>>>>
>>>>>>>> root@havana:/home/localadmin# tcpdump -i qvo6157a9aa-76
>>>>>>>> tcpdump: WARNING: qvo6157a9aa-76: no IPv4 address assigned
>>>>>>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol
>>>>>>>> decode
>>>>>>>> listening on qvo6157a9aa-76, link-type EN10MB (Ethernet), capture
>>>>>>>> size 65535 bytes
>>>>>>>> 16:46:39.006180 IP6 fe80::40fa:38ff:fee3:a3fa > ff02::16: HBH
>>>>>>>> ICMP6, multicast listener report v2, 1 group record(s), length 28
>>>>>>>> 16:46:39.784902 IP6 :: > ff02::16: HBH ICMP6, multicast listener
>>>>>>>> report v2, 1 group record(s), length 28
>>>>>>>> 16:46:39.824273 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
>>>>>>>> BOOTP/DHCP, Request from fa:16:3e:9a:38:1e (oui Unknown), length 280
>>>>>>>> 16:46:39.933463 IP6 :: > ff02::1:ff9a:381e: ICMP6, neighbor
>>>>>>>> solicitation, who ha

Re: [Openstack] havana dhcp issue

[Paras pradhan]

Nick,

I don't see GRE(odd?) but with others (br-tun,patch-int) are all '0'. It is
a single node installation if that matters.

-Paras.


On Thu, Nov 14, 2013 at 10:36 AM, Nick Maslov  wrote:

> Hi Paras,
>
> I also have speed at 0Mbps on my br-tun for everything (GRE, patch-int) in
> one environment, and 100Mbps on another.
>
> Can you pls provide me with some info about those speed marks? Like, if
> it`s on 0 - that means that no tunnels are working properly?
>
> Thanks
> NM
>
> --
> Nick Maslov
> Sent with Airmail <http://airmailapp.com/tracking>
>
> On November 11, 2013 at 6:41:40 PM, Paras pradhan 
> (pradhanpa...@gmail.com)
> wrote:
>
> Yes br-tun is there.  here is the o/p of ovs-ofctl.
>
> -
>  root@havana:~# ovs-ofctl show br-tun
> OFPT_FEATURES_REPLY (xid=0x2): dpid:4e6501755448
> n_tables:254, n_buffers:256
> capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
> actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST
> SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
>  1(patch-int): addr:42:9d:7c:13:4b:58
>  config: 0
>  state:  0
>  speed: 0 Mbps now, 0 Mbps max
>  LOCAL(br-tun): addr:4e:65:01:75:54:48
>  config: 0
>  state:  0
>  speed: 0 Mbps now, 0 Mbps max
> OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
>  --
>
> Thanks
> Paras.
>
>
> On Sat, Nov 9, 2013 at 3:44 AM, Igor Cardoso  wrote:
>
>> I guess br-tun is created in a single node as well, someone correct me if
>> I'm wrong please.
>> What is the output of ovs-ofctl show br-tun ?
>>
>>
>> On 9 November 2013 02:35, Paras pradhan  wrote:
>>
>>> Yes gre . all (controller plus compute) in a single node though.
>>>  On Nov 8, 2013 5:17 PM, "Igor Cardoso"  wrote:
>>>
>>>> Are you using GRE?
>>>>
>>>>
>>>> On 8 November 2013 22:48, Paras pradhan  wrote:
>>>>
>>>>>  use_namespace is set to true, iproute is up to date from 12.04 LTS.
>>>>>
>>>>> This is what I see when tcpdump
>>>>> -
>>>>>
>>>>>  root@havana:/home/localadmin# tcpdump -i qvo6157a9aa-76
>>>>> tcpdump: WARNING: qvo6157a9aa-76: no IPv4 address assigned
>>>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol
>>>>> decode
>>>>> listening on qvo6157a9aa-76, link-type EN10MB (Ethernet), capture size
>>>>> 65535 bytes
>>>>> 16:46:39.006180 IP6 fe80::40fa:38ff:fee3:a3fa > ff02::16: HBH ICMP6,
>>>>> multicast listener report v2, 1 group record(s), length 28
>>>>> 16:46:39.784902 IP6 :: > ff02::16: HBH ICMP6, multicast listener
>>>>> report v2, 1 group record(s), length 28
>>>>> 16:46:39.824273 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
>>>>> BOOTP/DHCP, Request from fa:16:3e:9a:38:1e (oui Unknown), length 280
>>>>> 16:46:39.933463 IP6 :: > ff02::1:ff9a:381e: ICMP6, neighbor
>>>>> solicitation, who has fe80::f816:3eff:fe9a:381e, length 24
>>>>> 16:46:40.325389 IP6 :: > ff02::16: HBH ICMP6, multicast listener
>>>>> report v2, 1 group record(s), length 28
>>>>> 16:46:40.934808 IP6 fe80::f816:3eff:fe9a:381e > ip6-allrouters: ICMP6,
>>>>> router solicitation, length 16
>>>>> 16:46:42.833239 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
>>>>> BOOTP/DHCP, Request from fa:16:3e:9a:38:1e (oui Unknown), length 280
>>>>> 16:46:44.936871 IP6 fe80::f816:3eff:fe9a:381e > ip6-allrouters: ICMP6,
>>>>> router solicitation, length 16
>>>>> 16:46:45.840668 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
>>>>> BOOTP/DHCP, Request from fa:16:3e:9a:38:1e (oui Unknown), length 280
>>>>> 16:46:48.945478 IP6 fe80::f816:3eff:fe9a:381e > ip6-allrouters: ICMP6,
>>>>> router solicitation, length 16
>>>>> 16:47:00.542029 IP 0.0.0.0 > all-systems.mcast.net: igmp query v2
>>>>> 16:47:00.542036 IP6 fe80::d894:29ff:fe08:5ec > ip6-allnodes: HBH
>>>>> ICMP6, multicast listener querymax resp delay: 1 addr: ::, length 24
>>>>>  --
>>>>>
>>>>> Thanks!
>>>>> Paras.
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Nov 8, 2013 at 4:26 PM, Rami Vaknin wrote:
>>>>>
>>>>>>  On 11/09/2013 12:18 AM, Paras pradhan wrote:
>>>>&

[Openstack] instance block migration

[Paras pradhan]

I have this flag in compute nodes' nova.conf file

--
block_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_NON_SHARED_INC
--

When I try to migrate an instance I see the following error. Basically it
says the instance's files are not found in destination compute node.
Should'nt it copy and create it self?

Stderr: "qemu-nbd: Failed to bdrv_open
'/var/lib/nova/instances/ae8b4bb2-1c87-46d5-9e75-b6f5a619d6ca/disk': No
such file or directory\n"


What am I missing?

Thanks
Paras.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] instance block migration

[Paras pradhan]

I don't see that as nova.conf option. Where do I find it?

-Paras.


On Wed, Dec 4, 2013 at 1:26 AM, sstrato.kong  wrote:

> you have to turn off the ‘config disk’ feature in nova.conf
>
> 2013. 12. 4., 오전 7:41, Paras pradhan  작성:
>
> > I have this flag in compute nodes' nova.conf file
> >
> > --
> >
> block_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_NON_SHARED_INC
> > --
> >
> > When I try to migrate an instance I see the following error. Basically
> it says the instance's files are not found in destination compute node.
> Should'nt it copy and create it self?
> >
> > Stderr: "qemu-nbd: Failed to bdrv_open
> '/var/lib/nova/instances/ae8b4bb2-1c87-46d5-9e75-b6f5a619d6ca/disk': No
> such file or directory\n"
> >
> >
> > What am I missing?
> >
> > Thanks
> > Paras.
> > ___
> > Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > Post to : openstack@lists.openstack.org
> > Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] floating ip (icehouse)

[Paras pradhan]

Hello,

I have a controller, a network and a compute node setup. When I spin an
instance, it gets its ip and it can reach the internet. Then I assign a
floating ip. From dashboard or cli I can see the ip's assoication with the
instanace but I can't ping this floating ip externally or from within the
instance. Where do I look?.  Distro: ubuntu 14.04 with mls.

Thanks
Paras.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] floating ip (icehouse)

[Paras pradhan]

Hi,

This is what I see.

nova net-list

+--+-+--+

| ID   | Label   | CIDR |

+--+-+--+

| 1b35da99-6ba3-431c-b1a9-4b59cbe30316 | ext_net | -|

| ff818534-ecba-4f8b-a4c9-a2f09fe1ee79 | prv | -|

+--+-+--+


nova floating-ip-list

+-+---+---+-+

| Ip  | Server Id | Fixed Ip  | Pool|

+-+---+---+-+

| 192.168.122.100 |   | 50.50.1.6 | ext_net |

+-+---+---+-+


Not any custom firewalls. I can see rules on controller, computer and
network rules installed by openstack.


I can't traceroute the floating ips from the router which has the same
network address.


Paras.



On Wed, Sep 10, 2014 at 2:41 AM, nithish B  wrote:

> Hi,
>Is this ip listed in your network? Kindly confirm that. Also, maybe the
> firewall is configured to drop those packets. Check it up with $traceroute
>  and post the output. That's a start!
>
> Regards,
> Nitish B.
>
> On Tue, Sep 9, 2014 at 9:17 PM, Paras pradhan 
> wrote:
>
>> Hello,
>>
>> I have a controller, a network and a compute node setup. When I spin an
>> instance, it gets its ip and it can reach the internet. Then I assign a
>> floating ip. From dashboard or cli I can see the ip's assoication with the
>> instanace but I can't ping this floating ip externally or from within the
>> instance. Where do I look?.  Distro: ubuntu 14.04 with mls.
>>
>> Thanks
>> Paras.
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] floating ip (icehouse)

[Paras pradhan]

I don't have this problem with havana. The only change is addition of ML2.
Not sure what I missed.

Paras.

On Fri, Sep 12, 2014 at 1:16 AM, nithish B  wrote:

> Well, I'm guessing that the gateway to those IPs are not configured. Else,
> traceroute should have worked. Kindly check if the gateway for that
> floating IPs exists in the host.
>
> Regards,
> Nitish B.
>
> On Wed, Sep 10, 2014 at 10:33 PM, Paras pradhan 
> wrote:
>
>> Hi,
>>
>> This is what I see.
>>
>> nova net-list
>>
>> +--+-+--+
>>
>> | ID   | Label   | CIDR |
>>
>> +--+-+--+
>>
>> | 1b35da99-6ba3-431c-b1a9-4b59cbe30316 | ext_net | -|
>>
>> | ff818534-ecba-4f8b-a4c9-a2f09fe1ee79 | prv | -|
>>
>> +--+-+--+
>>
>>
>> nova floating-ip-list
>>
>> +-+---+---+-+
>>
>> | Ip  | Server Id | Fixed Ip  | Pool|
>>
>> +-+---+---+-+
>>
>> | 192.168.122.100 |   | 50.50.1.6 | ext_net |
>>
>> +-+---+---+-+
>>
>>
>> Not any custom firewalls. I can see rules on controller, computer and
>> network rules installed by openstack.
>>
>>
>> I can't traceroute the floating ips from the router which has the same
>> network address.
>>
>>
>> Paras.
>>
>>
>>
>> On Wed, Sep 10, 2014 at 2:41 AM, nithish B 
>> wrote:
>>
>>> Hi,
>>>Is this ip listed in your network? Kindly confirm that. Also, maybe
>>> the firewall is configured to drop those packets. Check it up with
>>> $traceroute  and post the output. That's a start!
>>>
>>> Regards,
>>> Nitish B.
>>>
>>> On Tue, Sep 9, 2014 at 9:17 PM, Paras pradhan 
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> I have a controller, a network and a compute node setup. When I spin an
>>>> instance, it gets its ip and it can reach the internet. Then I assign a
>>>> floating ip. From dashboard or cli I can see the ip's assoication with the
>>>> instanace but I can't ping this floating ip externally or from within the
>>>> instance. Where do I look?.  Distro: ubuntu 14.04 with mls.
>>>>
>>>> Thanks
>>>> Paras.
>>>>
>>>> ___
>>>> Mailing list:
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>> Post to : openstack@lists.openstack.org
>>>> Unsubscribe :
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>
>>>>
>>>
>>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized

[Paras pradhan]

Can somebody share the nova.conf and neutron.conf from working mitaka? I am
also following the same guide and ran into a problem.

2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions
NoSuchOptError: no such option in group neutron: auth_plugin

Not sure what did I do wrong. It was while launching an instance.


Thanks

Paras.

On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood 
wrote:

> Martinx,
>
> glad to see that you are able to dig into the typo issue. I remember, I
> had to completely re-re-clean install my virtual setup of OpenStack for a
> POC back in 2015 , just because I have had miss-configured my
> neutron.conf's mysql DB connector information.
>
> Cheers!
>
>
> Regards,
> Nasir Mahmood
>
> On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ <
> thiagocmarti...@gmail.com> wrote:
>
>> FIXED!! I knew it was a typo somewhere!   LOL
>>
>>
>> https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02
>>
>> Thank you guys!
>>
>> Sorry about the buzz on TWO mail lists...
>>
>> At least, now we know that Nova silent fail on its start up, if
>> somethings aren't configured according... And there is no verification
>> steps to test the communication between Nova and Neutron.
>>
>>  Mitaka is working now on Xenial! YAY!!
>>
>> I'm about to commit changes to enable OpenvSwitch with DPDK and
>> multi-node deployments, fully automated!
>>
>> Cheers!
>> Thiago
>>
>> On 17 April 2016 at 21:26, Martinx - ジェームズ 
>> wrote:
>>
>>> On 17 April 2016 at 17:39, Martinx - ジェームズ 
>>> wrote:
>>>
 Guys,

  I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the
 following document:

  http://docs.openstack.org/mitaka/install-guide-ubuntu

  Yes, I know, the above document is for installing Mitaka on top of
 Ubuntu 14.04 but, from what I understand, the only difference is that on
 Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, since
 Mitaka is the default on Xenial, so, I can follow that document, right?
  =)

  At first, OpenStack installation goes okay, without any errors, all
 services comes up, etc... However, it is not possible to launch an 
 Instance.

  *** Errors on launching the Instance:

  - Right after launching it:

  https://paste.ubuntu.com/15902503/

  - Spawning it, after Glance finishes the download, similar error a
 second time:

  https://paste.ubuntu.com/15902556/

  What am I missing?

  Apparently, Nova is not authorized to talk with Neutron but, I am
 following the docs (maybe it is just a typo somewhere?)...

  Also, I have an Ansible automation to deploy it, so, it is less error
 prone. And however can help me, will see how I am deploying it.

  I see no error on Admin Dashboard, all services are up.

  NOTE: My Ansible playbooks is in a sense, "
 docs.openstack.org/mitaka/install-guide-ubuntu fully automated", it is
 very close to it, step-by-step.

  How can I debug this? I mean, how can I try to do, what Nova is doing
 (its connection with Neutron), to make sure that the settings are in place
 correctly?

  Here is how I am installing Mitaka on Xenial:

 ---
  1- Install Ubuntu 16.04 server 64-bit on bare-metal;

* Configure your /etc/hostname and /etc/hosts.

DETAILS:
 https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md


  2- Clone the automation:

 cd ~
 git clone https://github.com/tmartinx/svauto.git


  3- Run the automation to install OpenStack (all-in-one)

 cd ~/svauto

./os-deploy.sh --br-mode=LBR --use-dummies --base-os=ubuntu16
 --base-os-upgrade=yes --openstack-release=mitaka --openstack-installation
 --dry-run

ansible-playbook -c local site-openstack.yml --extra-vars
 "openstack_installation=yes"
 ---

  NOTE: If you don't use "--dry-run" option, Ansible will be executed
 automatically by "os-deploy.sh".

  I am sharing the Ansible playbooks, because it will be easier to see
 what I am doing.

  About the relevant configuration blocks, I believe that I have it
 properly configured (I followed Mitaka docs), like this:

  * neutron.conf:
 -

 https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_neutron_aio/templates/mitaka/neutron.conf
 -

  * nova.conf:
 -

 https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_aio/templates/mitaka/nova.conf
 -

  I already installed OpenStack many, many, many times, since Havana
 release, I'm confident that I am doing it right but, of course, maybe I did
 something wrong this time...   =P

  I appreciate any help!

 Thanks!
 Thiago

>>>
>>> Hey guys,
>>>
>>>  I am reviewing everything, to make sure that my automation 

Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized

[Paras pradhan]

Hi Eugen,

Thanks. Log says its an error. Here is the full log.
http://pastebin.com/K1f4pJhB

-Paras.

On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block  wrote:

> Hi Paras,
>
> the option auth_plugin is deprecated (from nova.conf):
>
> ---cut here---
> # Authentication type to load (unknown value)
> # Deprecated group/name - [DEFAULT]/auth_plugin
> auth_type = password
> ---cut here---
>
> But as far as I can tell, you should only get a warning, not an error,
> I've seen some of these warnings in my logs, but it works (I work with
> openSUSE). To get Mitaka working at all I simply tried to set the same
> options as in my working Liberty configs, and then I searched for
> deprecation warnings and additional options mentioned in the Mitaka guide.
>
> Hope this helps!
>
> Regards,
> Eugen
>
>
> Zitat von Paras pradhan :
>
>
> Can somebody share the nova.conf and neutron.conf from working mitaka? I am
>> also following the same guide and ran into a problem.
>>
>> 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions
>> NoSuchOptError: no such option in group neutron: auth_plugin
>>
>> Not sure what did I do wrong. It was while launching an instance.
>>
>>
>> Thanks
>>
>> Paras.
>>
>> On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood 
>> wrote:
>>
>> Martinx,
>>>
>>> glad to see that you are able to dig into the typo issue. I remember, I
>>> had to completely re-re-clean install my virtual setup of OpenStack for a
>>> POC back in 2015 , just because I have had miss-configured my
>>> neutron.conf's mysql DB connector information.
>>>
>>> Cheers!
>>>
>>>
>>> Regards,
>>> Nasir Mahmood
>>>
>>> On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ <
>>> thiagocmarti...@gmail.com> wrote:
>>>
>>> FIXED!! I knew it was a typo somewhere!   LOL
>>>>
>>>>
>>>>
>>>> https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02
>>>>
>>>> Thank you guys!
>>>>
>>>> Sorry about the buzz on TWO mail lists...
>>>>
>>>> At least, now we know that Nova silent fail on its start up, if
>>>> somethings aren't configured according... And there is no verification
>>>> steps to test the communication between Nova and Neutron.
>>>>
>>>>  Mitaka is working now on Xenial! YAY!!
>>>>
>>>> I'm about to commit changes to enable OpenvSwitch with DPDK and
>>>> multi-node deployments, fully automated!
>>>>
>>>> Cheers!
>>>> Thiago
>>>>
>>>> On 17 April 2016 at 21:26, Martinx - ジェームズ 
>>>> wrote:
>>>>
>>>> On 17 April 2016 at 17:39, Martinx - ジェームズ 
>>>>> wrote:
>>>>>
>>>>> Guys,
>>>>>>
>>>>>>  I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the
>>>>>> following document:
>>>>>>
>>>>>>  http://docs.openstack.org/mitaka/install-guide-ubuntu
>>>>>>
>>>>>>  Yes, I know, the above document is for installing Mitaka on top of
>>>>>> Ubuntu 14.04 but, from what I understand, the only difference is that
>>>>>> on
>>>>>> Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, since
>>>>>> Mitaka is the default on Xenial, so, I can follow that document,
>>>>>> right?
>>>>>>  =)
>>>>>>
>>>>>>  At first, OpenStack installation goes okay, without any errors, all
>>>>>> services comes up, etc... However, it is not possible to launch an
>>>>>> Instance.
>>>>>>
>>>>>>  *** Errors on launching the Instance:
>>>>>>
>>>>>>  - Right after launching it:
>>>>>>
>>>>>>  https://paste.ubuntu.com/15902503/
>>>>>>
>>>>>>  - Spawning it, after Glance finishes the download, similar error a
>>>>>> second time:
>>>>>>
>>>>>>  https://paste.ubuntu.com/15902556/
>>>>>>
>>>>>>  What am I missing?
>>>>>>
>>>>>>  Apparently, Nova is not authorized to talk with Neutron but, I am
>>>>>> following the docs (maybe it is just a typo somewhere?)...
>>>>>>

Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized

[Paras pradhan]

Yes I I have it set up in nova.conf and neutron.conf

On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block  wrote:

> And did you change it to auth_type instead of auth_plugin? Also you should
> make sure that this option is in the correct section of your config file,
> for example
>
> [keystone_authtoken]
> ...
> auth_type = password
>
> or
>
> [neutron]
> ...
> auth_type = password
>
>
> Regards,
> Eugen
>
>
> Zitat von Paras pradhan :
>
> Hi Eugen,
>>
>> Thanks. Log says its an error. Here is the full log.
>> http://pastebin.com/K1f4pJhB
>>
>> -Paras.
>>
>> On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block  wrote:
>>
>> Hi Paras,
>>>
>>> the option auth_plugin is deprecated (from nova.conf):
>>>
>>> ---cut here---
>>> # Authentication type to load (unknown value)
>>> # Deprecated group/name - [DEFAULT]/auth_plugin
>>> auth_type = password
>>> ---cut here---
>>>
>>> But as far as I can tell, you should only get a warning, not an error,
>>> I've seen some of these warnings in my logs, but it works (I work with
>>> openSUSE). To get Mitaka working at all I simply tried to set the same
>>> options as in my working Liberty configs, and then I searched for
>>> deprecation warnings and additional options mentioned in the Mitaka
>>> guide.
>>>
>>> Hope this helps!
>>>
>>> Regards,
>>> Eugen
>>>
>>>
>>> Zitat von Paras pradhan :
>>>
>>>
>>> Can somebody share the nova.conf and neutron.conf from working mitaka? I
>>> am
>>>
>>>> also following the same guide and ran into a problem.
>>>>
>>>> 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions
>>>> NoSuchOptError: no such option in group neutron: auth_plugin
>>>>
>>>> Not sure what did I do wrong. It was while launching an instance.
>>>>
>>>>
>>>> Thanks
>>>>
>>>> Paras.
>>>>
>>>> On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood >>> >
>>>> wrote:
>>>>
>>>> Martinx,
>>>>
>>>>>
>>>>> glad to see that you are able to dig into the typo issue. I remember, I
>>>>> had to completely re-re-clean install my virtual setup of OpenStack
>>>>> for a
>>>>> POC back in 2015 , just because I have had miss-configured my
>>>>> neutron.conf's mysql DB connector information.
>>>>>
>>>>> Cheers!
>>>>>
>>>>>
>>>>> Regards,
>>>>> Nasir Mahmood
>>>>>
>>>>> On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ <
>>>>> thiagocmarti...@gmail.com> wrote:
>>>>>
>>>>> FIXED!! I knew it was a typo somewhere!   LOL
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02
>>>>>>
>>>>>> Thank you guys!
>>>>>>
>>>>>> Sorry about the buzz on TWO mail lists...
>>>>>>
>>>>>> At least, now we know that Nova silent fail on its start up, if
>>>>>> somethings aren't configured according... And there is no verification
>>>>>> steps to test the communication between Nova and Neutron.
>>>>>>
>>>>>>  Mitaka is working now on Xenial! YAY!!
>>>>>>
>>>>>> I'm about to commit changes to enable OpenvSwitch with DPDK and
>>>>>> multi-node deployments, fully automated!
>>>>>>
>>>>>> Cheers!
>>>>>> Thiago
>>>>>>
>>>>>> On 17 April 2016 at 21:26, Martinx - ジェームズ >>>>> >
>>>>>> wrote:
>>>>>>
>>>>>> On 17 April 2016 at 17:39, Martinx - ジェームズ >>>>> >
>>>>>>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Guys,
>>>>>>>
>>>>>>>>
>>>>>>>>  I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the
>>>>>>>> following document:
>>>>>>>>
>>>>>>>>  http://docs.openstack.org/mitaka/ins

Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized

[Paras pradhan]

No I still have that error. Other than that I don't see any other errors.

On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block  wrote:

> So I guess the mentioned error should be resolved? Does it work now?
>
>
>
> Zitat von Paras pradhan :
>
> Yes I I have it set up in nova.conf and neutron.conf
>>
>> On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block  wrote:
>>
>> And did you change it to auth_type instead of auth_plugin? Also you should
>>> make sure that this option is in the correct section of your config file,
>>> for example
>>>
>>> [keystone_authtoken]
>>> ...
>>> auth_type = password
>>>
>>> or
>>>
>>> [neutron]
>>> ...
>>> auth_type = password
>>>
>>>
>>> Regards,
>>> Eugen
>>>
>>>
>>> Zitat von Paras pradhan :
>>>
>>> Hi Eugen,
>>>
>>>>
>>>> Thanks. Log says its an error. Here is the full log.
>>>> http://pastebin.com/K1f4pJhB
>>>>
>>>> -Paras.
>>>>
>>>> On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block  wrote:
>>>>
>>>> Hi Paras,
>>>>
>>>>>
>>>>> the option auth_plugin is deprecated (from nova.conf):
>>>>>
>>>>> ---cut here---
>>>>> # Authentication type to load (unknown value)
>>>>> # Deprecated group/name - [DEFAULT]/auth_plugin
>>>>> auth_type = password
>>>>> ---cut here---
>>>>>
>>>>> But as far as I can tell, you should only get a warning, not an error,
>>>>> I've seen some of these warnings in my logs, but it works (I work with
>>>>> openSUSE). To get Mitaka working at all I simply tried to set the same
>>>>> options as in my working Liberty configs, and then I searched for
>>>>> deprecation warnings and additional options mentioned in the Mitaka
>>>>> guide.
>>>>>
>>>>> Hope this helps!
>>>>>
>>>>> Regards,
>>>>> Eugen
>>>>>
>>>>>
>>>>> Zitat von Paras pradhan :
>>>>>
>>>>>
>>>>> Can somebody share the nova.conf and neutron.conf from working mitaka?
>>>>> I
>>>>> am
>>>>>
>>>>> also following the same guide and ran into a problem.
>>>>>>
>>>>>> 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions
>>>>>> NoSuchOptError: no such option in group neutron: auth_plugin
>>>>>>
>>>>>> Not sure what did I do wrong. It was while launching an instance.
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Paras.
>>>>>>
>>>>>> On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood <
>>>>>> nasir.mahm...@gmail.com
>>>>>> >
>>>>>> wrote:
>>>>>>
>>>>>> Martinx,
>>>>>>
>>>>>>
>>>>>>> glad to see that you are able to dig into the typo issue. I
>>>>>>> remember, I
>>>>>>> had to completely re-re-clean install my virtual setup of OpenStack
>>>>>>> for a
>>>>>>> POC back in 2015 , just because I have had miss-configured my
>>>>>>> neutron.conf's mysql DB connector information.
>>>>>>>
>>>>>>> Cheers!
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>> Nasir Mahmood
>>>>>>>
>>>>>>> On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ <
>>>>>>> thiagocmarti...@gmail.com> wrote:
>>>>>>>
>>>>>>> FIXED!! I knew it was a typo somewhere!   LOL
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02
>>>>>>>>
>>>>>>>> Thank you guys!
>>>>>>>>
>>>>>>>> Sorry about the buzz on TWO mail lists...
>>>>>>>>
>>>>>>>> At least, now we know that Nova silent fail

Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized

[Paras pradhan]

Yes . I did. here is my nova.conf. Can you share yours?
http://paste.openstack.org/show/494988/

On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block  wrote:

> Okay, did you restart the respective services on all nodes after the
> changes in your config files? If the same error still occurs then you might
> haven't found all occurrences of the option auth_plugin, did you replace it
> in all config files? I'm just guessing here...
>
>
>
> Zitat von Paras pradhan :
>
> No I still have that error. Other than that I don't see any other errors.
>>
>> On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block  wrote:
>>
>> So I guess the mentioned error should be resolved? Does it work now?
>>>
>>>
>>>
>>> Zitat von Paras pradhan :
>>>
>>> Yes I I have it set up in nova.conf and neutron.conf
>>>
>>>>
>>>> On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block  wrote:
>>>>
>>>> And did you change it to auth_type instead of auth_plugin? Also you
>>>> should
>>>>
>>>>> make sure that this option is in the correct section of your config
>>>>> file,
>>>>> for example
>>>>>
>>>>> [keystone_authtoken]
>>>>> ...
>>>>> auth_type = password
>>>>>
>>>>> or
>>>>>
>>>>> [neutron]
>>>>> ...
>>>>> auth_type = password
>>>>>
>>>>>
>>>>> Regards,
>>>>> Eugen
>>>>>
>>>>>
>>>>> Zitat von Paras pradhan :
>>>>>
>>>>> Hi Eugen,
>>>>>
>>>>>
>>>>>> Thanks. Log says its an error. Here is the full log.
>>>>>> http://pastebin.com/K1f4pJhB
>>>>>>
>>>>>> -Paras.
>>>>>>
>>>>>> On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block  wrote:
>>>>>>
>>>>>> Hi Paras,
>>>>>>
>>>>>>
>>>>>>> the option auth_plugin is deprecated (from nova.conf):
>>>>>>>
>>>>>>> ---cut here---
>>>>>>> # Authentication type to load (unknown value)
>>>>>>> # Deprecated group/name - [DEFAULT]/auth_plugin
>>>>>>> auth_type = password
>>>>>>> ---cut here---
>>>>>>>
>>>>>>> But as far as I can tell, you should only get a warning, not an
>>>>>>> error,
>>>>>>> I've seen some of these warnings in my logs, but it works (I work
>>>>>>> with
>>>>>>> openSUSE). To get Mitaka working at all I simply tried to set the
>>>>>>> same
>>>>>>> options as in my working Liberty configs, and then I searched for
>>>>>>> deprecation warnings and additional options mentioned in the Mitaka
>>>>>>> guide.
>>>>>>>
>>>>>>> Hope this helps!
>>>>>>>
>>>>>>> Regards,
>>>>>>> Eugen
>>>>>>>
>>>>>>>
>>>>>>> Zitat von Paras pradhan :
>>>>>>>
>>>>>>>
>>>>>>> Can somebody share the nova.conf and neutron.conf from working
>>>>>>> mitaka?
>>>>>>> I
>>>>>>> am
>>>>>>>
>>>>>>> also following the same guide and ran into a problem.
>>>>>>>
>>>>>>>>
>>>>>>>> 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions
>>>>>>>> NoSuchOptError: no such option in group neutron: auth_plugin
>>>>>>>>
>>>>>>>> Not sure what did I do wrong. It was while launching an instance.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> Paras.
>>>>>>>>
>>>>>>>> On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood <
>>>>>>>> nasir.mahm...@gmail.com
>>>>>>>> >
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Martinx,
>>>>>>>>
>>>>>>>>
>>>>>>>> glad to see that you are able 

Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized

[Paras pradhan]

The neutron section was missing from nova.conf and now the instances work
but having issues with metadata server. instances boot but no network
access.
Thanks
Paras.

On Thu, Apr 21, 2016 at 9:58 AM, Martinx - ジェームズ 
wrote:

> My nova.conf is this one:
>
>
> https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_cmpt/templates/mitaka/nova.conf
>
> However, I'm facing connectivity problems when with OpenvSwitch
> deployments, investigating it now...
>
> On 21 April 2016 at 11:04, Paras pradhan  wrote:
>
>> Yes . I did. here is my nova.conf. Can you share yours?
>> http://paste.openstack.org/show/494988/
>>
>> On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block  wrote:
>>
>>> Okay, did you restart the respective services on all nodes after the
>>> changes in your config files? If the same error still occurs then you might
>>> haven't found all occurrences of the option auth_plugin, did you replace it
>>> in all config files? I'm just guessing here...
>>>
>>>
>>>
>>> Zitat von Paras pradhan :
>>>
>>> No I still have that error. Other than that I don't see any other errors.
>>>>
>>>> On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block  wrote:
>>>>
>>>> So I guess the mentioned error should be resolved? Does it work now?
>>>>>
>>>>>
>>>>>
>>>>> Zitat von Paras pradhan :
>>>>>
>>>>> Yes I I have it set up in nova.conf and neutron.conf
>>>>>
>>>>>>
>>>>>> On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block  wrote:
>>>>>>
>>>>>> And did you change it to auth_type instead of auth_plugin? Also you
>>>>>> should
>>>>>>
>>>>>>> make sure that this option is in the correct section of your config
>>>>>>> file,
>>>>>>> for example
>>>>>>>
>>>>>>> [keystone_authtoken]
>>>>>>> ...
>>>>>>> auth_type = password
>>>>>>>
>>>>>>> or
>>>>>>>
>>>>>>> [neutron]
>>>>>>> ...
>>>>>>> auth_type = password
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>> Eugen
>>>>>>>
>>>>>>>
>>>>>>> Zitat von Paras pradhan :
>>>>>>>
>>>>>>> Hi Eugen,
>>>>>>>
>>>>>>>
>>>>>>>> Thanks. Log says its an error. Here is the full log.
>>>>>>>> http://pastebin.com/K1f4pJhB
>>>>>>>>
>>>>>>>> -Paras.
>>>>>>>>
>>>>>>>> On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block  wrote:
>>>>>>>>
>>>>>>>> Hi Paras,
>>>>>>>>
>>>>>>>>
>>>>>>>>> the option auth_plugin is deprecated (from nova.conf):
>>>>>>>>>
>>>>>>>>> ---cut here---
>>>>>>>>> # Authentication type to load (unknown value)
>>>>>>>>> # Deprecated group/name - [DEFAULT]/auth_plugin
>>>>>>>>> auth_type = password
>>>>>>>>> ---cut here---
>>>>>>>>>
>>>>>>>>> But as far as I can tell, you should only get a warning, not an
>>>>>>>>> error,
>>>>>>>>> I've seen some of these warnings in my logs, but it works (I work
>>>>>>>>> with
>>>>>>>>> openSUSE). To get Mitaka working at all I simply tried to set the
>>>>>>>>> same
>>>>>>>>> options as in my working Liberty configs, and then I searched for
>>>>>>>>> deprecation warnings and additional options mentioned in the Mitaka
>>>>>>>>> guide.
>>>>>>>>>
>>>>>>>>> Hope this helps!
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Eugen
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Zitat von Paras pradhan :
>>>>>>>>>
>>>>>>>>>
>>>>>>&

Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized

[Paras pradhan]

Thanks Martinx

On Thu, Apr 21, 2016 at 2:50 PM, Martinx - ジェームズ 
wrote:

> I just manage to make OpenStack Mitaka to work with both Linux Bridges,
> and OpenvSwitch...
>
> Everything is work on both "All in One" and multi-node environments.
>
> Very soon, I'll post instructions about how to use the Ansible automation
> that I am developing to play with this...
>
> Then, you guys will be able to deploy it, on a spare box (or VMs), and
> then, compare with failing deployemnts...
>
> Cheers!
>
> On 21 April 2016 at 16:44, Paras pradhan  wrote:
>
>> The neutron section was missing from nova.conf and now the instances work
>> but having issues with metadata server. instances boot but no network
>> access.
>> Thanks
>> Paras.
>>
>> On Thu, Apr 21, 2016 at 9:58 AM, Martinx - ジェームズ <
>> thiagocmarti...@gmail.com> wrote:
>>
>>> My nova.conf is this one:
>>>
>>>
>>> https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_cmpt/templates/mitaka/nova.conf
>>>
>>> However, I'm facing connectivity problems when with OpenvSwitch
>>> deployments, investigating it now...
>>>
>>> On 21 April 2016 at 11:04, Paras pradhan  wrote:
>>>
>>>> Yes . I did. here is my nova.conf. Can you share yours?
>>>> http://paste.openstack.org/show/494988/
>>>>
>>>> On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block  wrote:
>>>>
>>>>> Okay, did you restart the respective services on all nodes after the
>>>>> changes in your config files? If the same error still occurs then you 
>>>>> might
>>>>> haven't found all occurrences of the option auth_plugin, did you replace 
>>>>> it
>>>>> in all config files? I'm just guessing here...
>>>>>
>>>>>
>>>>>
>>>>> Zitat von Paras pradhan :
>>>>>
>>>>> No I still have that error. Other than that I don't see any other
>>>>>> errors.
>>>>>>
>>>>>> On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block  wrote:
>>>>>>
>>>>>> So I guess the mentioned error should be resolved? Does it work now?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Zitat von Paras pradhan :
>>>>>>>
>>>>>>> Yes I I have it set up in nova.conf and neutron.conf
>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block  wrote:
>>>>>>>>
>>>>>>>> And did you change it to auth_type instead of auth_plugin? Also you
>>>>>>>> should
>>>>>>>>
>>>>>>>>> make sure that this option is in the correct section of your
>>>>>>>>> config file,
>>>>>>>>> for example
>>>>>>>>>
>>>>>>>>> [keystone_authtoken]
>>>>>>>>> ...
>>>>>>>>> auth_type = password
>>>>>>>>>
>>>>>>>>> or
>>>>>>>>>
>>>>>>>>> [neutron]
>>>>>>>>> ...
>>>>>>>>> auth_type = password
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Eugen
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Zitat von Paras pradhan :
>>>>>>>>>
>>>>>>>>> Hi Eugen,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Thanks. Log says its an error. Here is the full log.
>>>>>>>>>> http://pastebin.com/K1f4pJhB
>>>>>>>>>>
>>>>>>>>>> -Paras.
>>>>>>>>>>
>>>>>>>>>> On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block 
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Paras,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> the option auth_plugin is deprecated (from nova.conf):
>>>>>>>>>>>
>>>>>>>>>

Re: [Openstack] Deployment for production

[Paras pradhan]

It is going to be a lot of work to make high availablity work with the
deployment you do with packstack or rdo.  Tripleo provides HA . One good
reason to deploy triplo over rdo / packstack

-Paras.

On Wed, May 3, 2017 at 7:08 PM, Mike Smith  wrote:

> At Overstock.com we use RDO on CentOS for our production clouds.   Works
> great for us.
>
> We do the install straight from the openstack docs but do our own puppet
> modules since we use puppet for everything we do.
>
> Mike
>
> > On May 3, 2017, at 1:01 AM, Satish Patel  wrote:
> >
> > We did POC on RDO and we are happy with product but now question is,
> should we use RDO for production deployment or other open source flavor
> available to deploy on prod. Not sure what is the best method of production
> deployment?
> >
> > Sent from my iPhone
> > ___
> > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> > Post to : openstack@lists.openstack.org
> > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Redhat overcloud node's introspection failing with timeout

[Paras pradhan]

First thing I would check is if the overcloud nodes are booting from pxe or
not.

-Paras.

On Thu, Aug 17, 2017 at 11:07 AM, Shyam Biradar <
shyambiradarsgg...@gmail.com> wrote:

> Hi,
>
> RedHat introspection is failing with timeout error.
>
> I have deployed undercloud and overcloud nodes as VMs on an ESX node and
> using fake_pxe driver for power management.
> I am managing power status of nodes manually.
>
> More details are, during introspection ironic-introspector is not able to
> add MAC address entry to iptables. From documentation it seems that it
> should add.
>
> [stack@redhat-undercloud ~]$ sudo iptables -L ironic-inspector
> Chain ironic-inspector (1 references)
> target prot opt source   destination
> ACCEPT all  --  anywhere anywhere
>
>
> Here are the snap of introspector logs:
> 
> --
>
> Aug 17 12:01:27 redhat-undercloud.triliodata.demo
> ironic-inspector[15329]: 2017-08-17 12:01:27.818 15329 INFO werkzeug [-]
> 11.11.0.1 - - [17/Aug/2017 12:01:27] "GET 
> /v1/introspection/cac58c65-6605-4963-bf75-428295dea0b8
> HTTP/1.1" 200 -
> Aug 17 12:01:31 redhat-undercloud.triliodata.demo
> ironic-inspector[15329]: 2017-08-17 12:01:31.664 15329 DEBUG
> futurist.periodics [-] Submitting periodic function
> 'ironic_inspector.main.periodic_update' _process_scheduled
> /usr/lib/python2.7/site-packages/futurist/periodics.py:614
> Aug 17 12:01:31 redhat-undercloud.triliodata.demo
> ironic-inspector[15329]: 2017-08-17 12:01:31.687 15329 DEBUG
> ironic_inspector.firewall [-] *Not updating iptables - no changes in MAC
> list set([]) update_filters
> /usr/lib/python2.7/site-packages/ironic_inspector/firewall.py:190*
> Aug 17 12:01:37 redhat-undercloud.triliodata.demo
> ironic-inspector[15329]: 2017-08-17 12:01:37.838 15329 INFO werkzeug [-]
> 11.11.0.1 - - [17/Aug/2017 12:01:37] "GET 
> /v1/introspection/cac58c65-6605-4963-bf75-428295dea0b8
> HTTP/1.1" 200
> 
> --
>
> No other error found in logs.
>
> Any suggestions are welcome.
>
>
> Thanks & Regards,
> Shyam Biradar,
> Email: shyambiradarsgg...@gmail.com,
> Contact: +91 8600266938 <+91%2086002%2066938>.
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] compute nodes down

[Paras pradhan]

It might not be the compute nodes. I would check the rabbitmq, neutron and
nova logs on the controllers.


Paras

On Dec 18, 2017 5:30 PM, "Volodymyr Litovka"  wrote:

> Hi Jim,
>
> switch debug to true in nova.conf and check *also* other logs -
> nova-scheduler, nova-placement, nova-conductor.
>
> On 12/19/17 12:54 AM, Jim Okken wrote:
>
> hi list,
>
> hoping someone could shed some light on this issue I just started seeing
> today
>
> all my compute nodes started showing as "Down" in the Horizon ->
> Hypervisors -> Compute Nodes tab
>
>
> root@node-1:~# nova service-list
> +-+--+---+--+---
> --+---++-+
> | Id  | Binary   | Host  | Zone | Status  | State
> | Updated_at | Disabled Reason |
> +-+--+---+--+---
> --+---++-+
> | 325 | nova-compute | node-9.mydom.com  | nova | enabled | down
> | 2017-12-18T21:59:38.00 | -   |
> | 448 | nova-compute | node-14.mydom.com | nova | enabled | up
> | 2017-12-18T22:41:42.00 | -   |
> | 451 | nova-compute | node-17.mydom.com | nova | enabled | up
> | 2017-12-18T22:42:04.00 | -   |
> | 454 | nova-compute | node-11.mydom.com | nova | enabled | up
> | 2017-12-18T22:42:02.00 | -   |
> | 457 | nova-compute | node-12.mydom.com | nova | enabled | up
> | 2017-12-18T22:42:12.00 | -   |
> | 472 | nova-compute | node-16.mydom.com | nova | enabled | down
> | 2017-12-18T00:16:01.00 | -   |
> | 475 | nova-compute | node-10.mydom.com | nova | enabled | down
> | 2017-12-18T00:26:09.00 | -   |
> | 478 | nova-compute | node-13.mydom.com | nova | enabled | down
> | 2017-12-17T23:54:06.00 | -   |
> | 481 | nova-compute | node-15.mydom.com | nova | enabled | up
> | 2017-12-18T22:41:34.00 | -   |
> | 484 | nova-compute | node-8.mydom.com  | nova | enabled | down
> | 2017-12-17T23:55:50.00 | -   |
>
>
> if I stop and the start nova-compute on the down nodes the stop will take
> several minutes and then the start will be quick and fine. but after about
> 2 hours the nova-compute service will show down again.
>
> i am not seeing any ERRORS in nova logs.
>
> I get this for the status of a node that is showing as "UP"
>
>
>
> root@node-14:~# systemctl status nova-compute.service
> â nova-compute.service - OpenStack Compute
>Loaded: loaded (/lib/systemd/system/nova-compute.service; enabled;
> vendor preset: enabled)
>Active: active (running) since Mon 2017-12-18 21:57:10 UTC; 35min ago
>  Docs: man:nova-compute(1)
>   Process: 32193 ExecStartPre=/bin/chown nova:adm /var/log/nova
> (code=exited, status=0/SUCCESS)
>   Process: 32190 ExecStartPre=/bin/chown nova:nova /var/lock/nova
> /var/lib/nova (code=exited, status=0/SUCCESS)
>   Process: 32187 ExecStartPre=/bin/mkdir -p /var/lock/nova /var/log/nova
> /var/lib/nova (code=exited, status=0/SUCCESS)
>  Main PID: 32196 (nova-compute)
>CGroup: /system.slice/nova-compute.service
>ââ32196 /usr/bin/python /usr/bin/nova-compute
> --config-file=/etc/nova/nova-compute.conf --config-file=/etc/nova/nova.conf
> --log-file=/var/log/nova/nova-compute.log
>
> Dec 18 22:31:47 node-14.mydom.com nova-compute[32196]: 2017-12-18
> 22:31:47.570 32196 DEBUG oslo_messaging._drivers.amqpdriver
> [req-f30b2331-2097-4981-89c8-acea4a81f7f2 - - - - -] CALL msg_id:
> 2877b9707da144f3a91e7b80e2705fb3 exchange 'nova' topic 'conductor' _send
> /usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:448
> Dec 18 22:31:47 node-14.mydom.com nova-compute[32196]: 2017-12-18
> 22:31:47.604 32196 DEBUG oslo_messaging._drivers.amqpdriver [-] received
> reply msg_id: 2877b9707da144f3a91e7b80e2705fb3 __call__
> /usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:296
> Dec 18 22:31:47 node-14.mydom.com nova-compute[32196]: 2017-12-18
> 22:31:47.605 32196 INFO nova.compute.resource_tracker
> [req-f30b2331-2097-4981-89c8-acea4a81f7f2 - - - - -] Total usable vcpus:
> 40, total allocated vcpus: 0
> Dec 18 22:31:47 node-14.mydom.com nova-compute[32196]: 2017-12-18
> 22:31:47.606 32196 INFO nova.compute.resource_tracker
> [req-f30b2331-2097-4981-89c8-acea4a81f7f2 - - - - -] Final resource view:
> name=node-14.mydom.com phys_ram=128812MB used_ram=512MB phys_disk=6691GB
> used_disk=0GB total_vcpus=40 used_vcpus=0 pci_stats=[]
> Dec 18 22:31:47 node-14.mydom.com nova-compute[32196]: 2017-12-18
> 22:31:47.610 32196 DEBUG oslo_messaging._drivers.amqpdriver
> [req-f30b2331-2097-4981-89c8-acea4a81f7f2 - - - - -] CALL msg_id:
> ad32abe833f4440d86c15b911aa35c43 exchange 'nova' topic 'conductor' _send
> /usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:448
> Dec 

Re: [Openstack] Instances lost connectivity with metadata service.

[Paras pradhan]

If this is project specifc usually I run the router-update and fixes the
problem.

/usr/bin/neutron router-update --admin-state-up False $routerid
/usr/bin/neutron router-update --admin-state-up True $routerid

On Mon, Feb 26, 2018 at 5:53 AM, Jorge Luiz Correa 
wrote:

> I would like some help to identify (and correct) a problem with instances
> metadata during booting. My environment is a Mitaka instalation, under
> Ubuntu 16.04 LTS, with 1 controller, 1 network node and 5 compute nodes.
> I'm using classic OVS as network setup.
>
> The problem ocurs after some period of time in some projects (not all
> projects at same time). When booting a Ubuntu Cloud Image with cloud-init,
> instances lost conection with API metadata and doesn't get their
> information like key-pairs and cloud-init scripts.
>
> [  118.924311] cloud-init[932]: 2018-02-23 18:27:05,003 -
> url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-
> 04-04/meta-data/instance-id' failed [101/120s]: request error
> [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries
> exceeded with url: /2009-04-04/meta-data/instance-id (Caused by
> ConnectTimeoutError( object at 0x7faabcd6fa58>, 'Connection to 169.254.169.254 timed out.
> (connect timeout=50.0)'))]
> [  136.959361] cloud-init[932]: 2018-02-23 18:27:23,038 -
> url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-
> 04-04/meta-data/instance-id' failed [119/120s]: request error
> [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries
> exceeded with url: /2009-04-04/meta-data/instance-id (Caused by
> ConnectTimeoutError( object at 0x7faabcd7f240>, 'Connection to 169.254.169.254 timed out.
> (connect timeout=17.0)'))]
> [  137.967469] cloud-init[932]: 2018-02-23 18:27:24,040 -
> DataSourceEc2.py[CRITICAL]: Giving up on md from ['
> http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 120
> seconds
> [  137.972226] cloud-init[932]: 2018-02-23 18:27:24,048 -
> url_helper.py[WARNING]: Calling 'http://192.168.0.7/latest/
> meta-data/instance-id' failed [0/120s]: request error
> [HTTPConnectionPool(host='192.168.0.7', port=80): Max retries exceeded
> with url: /latest/meta-data/instance-id (Caused by
> NewConnectionError(' object at 0x7faabcd7fc18>: Failed to establish a new connection: [Errno
> 111] Connection refused',))]
> [  138.974223] cloud-init[932]: 2018-02-23 18:27:25,053 -
> url_helper.py[WARNING]: Calling 'http://192.168.0.7/latest/
> meta-data/instance-id' failed [1/120s]: request error
> [HTTPConnectionPool(host='192.168.0.7', port=80): Max retries exceeded
> with url: /latest/meta-data/instance-id (Caused by
> NewConnectionError(' object at 0x7faabcd7fa58>: Failed to establish a new connection: [Errno
> 111] Connection refused',))]
>
> After give up 169.254.169.254 it tries 192.168.0.7 that is the dhcp
> address for the project.
>
> I've checked that neutron-l3-agent is running, without errors. On compute
> node where VM is running, agents and vswitch is running. I could check the
> namespace of a problematic project and saw an iptables rules redirecting
> traffic from 169.254.169.254:80 to 0.0.0.0:9697, and there is a process
> neutron-ns-medata_proxy_ID  that opens that port. So, it look like the
> metadata-proxy is running fine. But, as we can see in logs there is a
> timeout.
>
> If I restart all services on network node sometimes solves the problem. In
> some cases I have to restart services on controller node (nova-api). So,
> all work fine for some time and start to have problems again.
>
> Where can I investigate to try finding the cause of the problem?
>
> I appreciate any help. Thank you!
>
> - JLC
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Multiple floating IPs one instance

[Paras pradhan]

Look for  nova add-fixed-ip and nova add-floating-ip

* add a private fixed ip for an instance:  nova add-fixed-ip instance_id
neutron_network_id
* On instance : ip address add private_fixed_ip_address/24 dev eth0
* add fip: nova add-floating-ip --fixed-address private_fixed_ip_address
instance_id floating_ip_address

Thanks
Paras.

On Fri, Apr 27, 2018 at 1:47 PM, Torin Woltjer 
wrote:

> Is it possible to run an instance with more than one floating IPs? It is
> not immediately evident how to do this, or whether it is even possible. I
> have an instance that I would like to have address on two separate
> networks, and would like to use floating IPs so that I can have that are
> capable of living longer than the instance itself.
>
> *Torin Woltjer*
>
> *Grand Dial Communications - A ZK Tech Inc. Company*
>
> *616.776.1066 ext. 2006*
> * www.granddial.com *
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack