Open Stack

bingo.. looks like security group was too restrictive.. so basically
seliunx, onboot=no and sec group was causing this behavior.  Thanks again
for your help with this.  Now I have learned how to build glance image :)
Appreciate your quick help with this.

Regards

On Sat, Mar 26, 2016 at 4:10 PM, Remo Mattei <Remo at italy1.com> wrote:

> Can you ping out do you have the right sec rules? Looks like 169 shows up
> so that is a good thing if it takes long to boot usually there is a problem
> with h communications between the host and dhcp can you got to the
> namespace and check and see if you can ping the dhcp server but again make
> sure rules are right.
>
> Inviato da iPhone
>
> Il giorno 26 mar 2016, alle ore 17:01, Jagga Soorma <jagga13 at gmail.com>
> ha scritto:
>
> Ahhh.. got further.. looks like eth0 was set to onboot=no :( rebooting
> with onboot=yes gets me a bit further but the curl is still failing..
> attached is the screenshot from the new bootup..  the bootup process seems
> to be much longer now as well ..
>
> On Sat, Mar 26, 2016 at 3:54 PM, Jagga Soorma <jagga13 at gmail.com> wrote:
>
>> Ahh so looks like selinux was on.  I disabled it by setting
>> SELINUX=disabled in /etc/selinux/config and rebooted the instance.  However
>> when it comes up it has the same issue.  I do see a error right after
>> cloud-init runs saying "Route info failed".  I have attached a screenshot.
>>
>> Also here is the error I get when trying the curl:
>>
>> curl http://169.254.169.254/latest/meta-data/
>> curl: (7) Failed to connect to 169.254.169.254: Network is unreachable
>>
>> Thanks again for your help, its much appreciated!
>>
>> On Sat, Mar 26, 2016 at 3:42 PM, Remo Mattei <remo at italy1.com> wrote:
>>
>>> can you do a curl to
>>>
>>> curl http://169.254.169.254/latest/meta-data/
>>>
>>> this needs to be done from the inside of the Instance
>>>
>>> I would export it from glance in case and test it from there.. Also
>>> check and see if your selinux is on!
>>>
>>> Remo
>>>
>>> On Mar 26, 2016, at 16:34, Jagga Soorma <jagga13 at gmail.com> wrote:
>>>
>>> I am trying to launch a instance from horizon using this new image.  It
>>> was working on the centos 6 server that I built it on.  The server comes up
>>> eventually on horizon but with no networking or keys due to the cloudinit
>>> not working and running into that issue with reaching that 169 address.
>>>
>>> Thanks for your help with this.
>>>
>>> On Sat, Mar 26, 2016 at 3:32 PM, Remo Mattei <remo at italy1.com> wrote:
>>>
>>>> did you try the machine local boot with virsh?
>>>> Does it show up?
>>>>
>>>> I am on a trip now but I could look at it later next week if you still
>>>> have some issues…
>>>>
>>>> Remo
>>>>
>>>>
>>>>
>>>> On Mar 26, 2016, at 16:22, Jagga Soorma <jagga13 at gmail.com> wrote:
>>>>
>>>> Hi Guys,
>>>>
>>>> I am building a new CentOS 6.7 based image for our kilo based openstack
>>>> environment.  I have followed the instructions on
>>>> http://docs.openstack.org/image-guide/centos-image.html.
>>>>
>>>> However when I boot my new image in openstack it does not come all the
>>>> way up and I see the following errors on console:
>>>>
>>>> --
>>>> [CLOUDINIT] url_helper.py[WARNING]: Calling '
>>>> http://169.254.169/254/2009-04-04/meta-data/instance-id' failed
>>>> [75/120s]: unexpected error ['NoneType' object has no attribute
>>>> 'status_code']
>>>> --
>>>>
>>>> Not really sure what I am missing here.  Any help would be appreciated.
>>>>
>>>> Thanks.
>>>> _______________________________________________
>>>> Mailing list:
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>> Post to     : openstack at lists.openstack.org
>>>> Unsubscribe :
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>
>>>>
>>>>
>>>>
>>>>
>>> !DSPAM:1,56f70fbb304453562127646!
>>>
>>>
>>>
>>
> !DSPAM:1,56f714d6311291675315456!
>
> <cloudinit_issue.tiff>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160326/aec61101/attachment.html>