Open Stack

On 10/28/2012 06:00 PM, Daniel Vázquez wrote:

> 2012/10/27 Pádraig Brady <P at draigbrady.com>:
>> On 10/26/2012 06:38 PM, Daniel Vázquez wrote:
>>>
>>>
>>> 2012/10/26 Pádraig Brady <P at draigbrady.com>:
>>>>
>>>> On 10/25/2012 06:30 PM, Pavan Kulkarni wrote:
>>>>>
>>>>>
>>>>> Hi all,
>>>>>
>>>>>      I am facing errors while launching instances on RHEL.
>>>>> The network.log says *cannot run lease-init script
>>>>> /usr/bin/nova-dhcpbridge*
>>>>> I did a liitle search and found out this link
>>>>> <https://lists.launchpad.net/openstack/msg08790.html>, followed the
>>>>> instructions.
>>>>> I have the flag in nova.conf set i.e *dhcpbridge =
>>>>> /usr/bin/nova-dhcpbridge ( This file does exist)*
>>>>>
>>>>> But I still get the same error while launching instances.
>>>>> Any help is highly appreciated .Thanks
>>>>
>>>>
>>>>
>>>> What version of RHEL?
>>>> What version of OpenStack?
>>>> What version of selinux-policy?
>>>>
>>>> The error message (which you seem to have truncated) comes from
>>>> dnsmasq itself, and is mentioned here in relation to SELinux:
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=734346
>>>> You might want to update your SELinux policies.
>>
>>
>>> I'm experiencing same problems on Centos 6.3 (it's RHEL based). All
>>> network system seem to stay ok, Openstack produces private IPs and nat
>>>    public iPs to instances.
>>> But instances don't discover DHCP.
>>>
>>> Here:
>>> Centos 6.3
>>> Essex version
>>> nova-networking flatDCHP
>>> selinux permisive
>>
>> I can't reproduce here.
>> Are you using the EPEL OpenStack packages?
>> On 6.3 based systems please ensure you install the dnsmasq-utils,
>> which installs utils that may be related to this.
>>
>> If using the EPEL packages, I'd advise logging this
>> at http://bugzilla.redhat.com/ against the EPEL version
>> of openstack-nova, so that we don't miss anything.
 >
 > Using epel and dnsmasq-utils, here.

OK please see if there are corresponding messages in /var/log/audit/audit.log
as shown in https://bugzilla.redhat.com/show_bug.cgi?id=734346

If you turn on debugging you should see the `sudo ... dnsmasq`
command being run, and you can try that manually with various
settings to pinpoint your issue.
I know you said you've SELinux=permissive.
Maybe start with SElinux=disabled, and if that works,
you know it's a policy issue on your system.
If it doesn't work then see can you run the script
manually without dnsmasq and build up from there.

thanks,
Pádraig.