Bug 1124897 - [Doc] add manual configuration after upgrade to allow launching of new instances
Summary: [Doc] add manual configuration after upgrade to allow launching of new instances
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Upgrade
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: 5.0 (RHEL 6)
Assignee: Don Domingo
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On: 1121619
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-30 15:01 UTC by Dafna Ron
Modified: 2014-08-11 08:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-11 08:14:32 UTC


Attachments (Terms of Use)

Description Dafna Ron 2014-07-30 15:01:23 UTC
Description of problem:

After upgrade I tried creating a new instance and failed with the following error: 

RescheduledException: Build of instance 0eebb3c5-4b2f-4ac6-90b5-e3f707098472 was re-scheduled: Unexpected vif_type=binding_failed

to fix it we need to add some configuration to neutron and nova conf files as published by kashyap: 
https://www.redhat.com/archives/rdo-list/2014-May/msg00079.html

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. after upgrade we fail to launch a new instance 
2. we need to add some additional changes to the following files:
/etc/neutron/plugins/ml2/ml2_conf.ini
/etc/neutron/neutron.conf
/etc/nova/nova.conf

Actual results:

we fail to launch an instance until we add the changes and I did not find the changes in the network configuration guide. 

Expected results:

changes should add the changes to the guide. 

Additional info:

here are the changes for each file: 

vim /etc/neutron/plugins/ml2/ml2_conf.ini

[ml2]
type_drivers = gre
tenant_network_types = gre
mechanism_drivers = openvswitch

[ml2_type_gre]
tunnel_id_ranges = 1:1000

[securitygroup]
firewall_driver =
neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
enable_security_group = True
[ovs]
local_ip = 192.169.142.97
[agent]
tunnel_types = gre
root_helper = sudo /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf

vim /etc/neutron/neutron.conf

linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver
vif_plugging_is_fatal = False
vif_plugging_timeout = 0

vim /etc/nova/nova.conf

[DEFAULT]
agent_down_time = 75
[agent]
report_interval = 5

Comment 1 Andrew Dahms 2014-07-30 21:56:17 UTC
Assigning to Martin Lopes, as the designated author for Neutron and networking issues.

Comment 5 Toni Freger 2014-08-11 05:50:02 UTC
Hi Don, 

These values are correct. 

vif_plugging_is_fatal=true
vif_plugging_timeout=300
 
It means that nova will wait for vif plugging event from neutron for 300 sec and only after it will arrive (that means that neutron successfully created port for the instance) the instance will be launched successfully .

Otherwise if the configuration is set to "false", event won't be expected to arrive, and nova can launch an instance even before neutron creates appropriate port for it, as a result instance could be created but without IP address.

Comment 6 Dafna Ron 2014-08-11 08:14:32 UTC
Hi Don, 
we found the the issue was not these values but a bug in one of the commands in nova configuration which is in the guide. 
I opened a separate bug on that and closing this one


Note You need to log in before you can comment on or make changes to this bug.