fuel-dev team mailing list archive

[Alexander Rubtsov <arubtsov@xxxxxxxxxxxx>]

Dmitriy,

If the user tries to deploy Mirantis OpenStack 5.0, he probably faced the
following issue:
http://docs.mirantis.com/fuel/fuel-5.0/release-notes.html#bootstrap-kernel-issues-on-certain-hardware


On Thu, Jun 26, 2014 at 3:15 AM, Dmitriy Novakovskiy <
dnovakovskiy@xxxxxxxxxxxx> wrote:

> Hi guys,
>
> I have a user having issues w/ node going through PXE boot but not showing
> up as unallocated
>
>
>>
>>
>>
>>
>>
>> * I get the following behavior:-          The server PXE-boots into
>> bootstrap, i.e. receives the image and boots up. -          Weird, though,
>> the node does not seem to register in the Fuel Dashboard. It does not
>> become visible in the node list.  It had been visible once earlier on when
>> I had PXE-booted it from another eth i/f but as that seemed to force the
>> Admin network onto the wrong NIC, I had subsequently changed the NIC from
>> which it would boot to avoid this.  Might this be a behavior due to some
>> stale DB entries from the first PXE boot? If so, how can I reset Fuel so
>> the servers are recognized fresh?*
>
>
> Any ideas why this might happen? So far I asked for Fuel diagnostic
> snapshot
>
>  ---
> Regards,
> Dmitriy
>
> --
> 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
>
>


-- 

Alexander Rubtsov
Operations Engineer
Mirantis Service Desk