NetScaler instance is not detecting the interfaces in Mirantis Openstack 6.0

Bug #1470163 reported by Venkateswara Rao Dokku
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Venkateswara Rao Dokku

Bug Description

We are trying to bring up Netscaler instance (FreeBSD based) on top of Mirantis Openstack fuel 6.0. We are booting it as ide disk & also we have assigned an interface.

The NetScaler booted up fine, but it couldn’t able to see the network interface that was assigned, even though we could see the interface details in XML file.
The following can be seen in the XML of the instance

<interface type='bridge'>
      <mac address='fa:16:3e:6a:98:c6'/>
      <source bridge='qbr247195b8-bf'/>
      <target dev='tap247195b8-bf'/>
      <model type='virtio'/>
      <driver name='qemu'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>

I could see the tap interface ('tap247195b8-bf') getting create in the host, but not getting detected in the NetScaler.

We could see the interfaces attached in case of Ubuntu also. Only FreeBSD based VM’s we are facing this issue.

Is there a known issue with the FreeBSD based VM’s?

Environment:
Mos: 6.0
Compute Node: Ubuntu Precise 12.04
Qemu : 2.0.0+dfsg-2ubuntu1.9

Changed in fuel:
milestone: none → 6.0.1
importance: Undecided → High
tags: added: customer-found
Changed in fuel:
assignee: nobody → MOS Linux (mos-linux)
Revision history for this message
Aleksander Mogylchenko (amogylchenko) wrote :

We had issues with Netscaler images before:
https://bugs.launchpad.net/fuel/+bug/1435501

Could you recheck logs to see if you face the same problem?

Changed in fuel:
status: New → Incomplete
Revision history for this message
Venkateswara Rao Dokku (dvrao-584) wrote : Re: [Bug 1470163] Re: NetScaler instance is not detecting the interfaces in Mirantis Openstack 6.0

After upgrading the sea-bios package, we hit this issue.

On Wed, Jul 1, 2015 at 2:00 PM, Aleksander Mogylchenko <
<email address hidden>> wrote:

> We had issues with Netscaler images before:
> https://bugs.launchpad.net/fuel/+bug/1435501
>
> Could you recheck logs to see if you face the same problem?
>
> ** Changed in: fuel
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1470163
>
> Title:
> NetScaler instance is not detecting the interfaces in Mirantis
> Openstack 6.0
>
> Status in Fuel: OpenStack installer that works:
> Incomplete
>
> Bug description:
> We are trying to bring up Netscaler instance (FreeBSD based) on top of
> Mirantis Openstack fuel 6.0. We are booting it as ide disk & also we have
> assigned an interface.
>
> The NetScaler booted up fine, but it couldn’t able to see the network
> interface that was assigned, even though we could see the interface details
> in XML file.
> The following can be seen in the XML of the instance
>
> <interface type='bridge'>
> <mac address='fa:16:3e:6a:98:c6'/>
> <source bridge='qbr247195b8-bf'/>
> <target dev='tap247195b8-bf'/>
> <model type='virtio'/>
> <driver name='qemu'/>
> <alias name='net0'/>
> <address type='pci' domain='0x0000' bus='0x00' slot='0x03'
> function='0x0'/>
> </interface>
>
> I could see the tap interface ('tap247195b8-bf') getting create in the
> host, but not getting detected in the NetScaler.
>
> We could see the interfaces attached in case of Ubuntu also. Only
> FreeBSD based VM’s we are facing this issue.
>
> Is there a known issue with the FreeBSD based VM’s?
>
> Environment:
> Mos: 6.0
> Compute Node: Ubuntu Precise 12.04
> Qemu : 2.0.0+dfsg-2ubuntu1.9
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/fuel/+bug/1470163/+subscriptions
>

--
Thanks & Regards,
Venkateswara Rao Dokku.

Revision history for this message
Aleksander Mogylchenko (amogylchenko) wrote :

Interesting. Can you share Netscaler image?

Revision history for this message
Venkateswara Rao Dokku (dvrao-584) wrote :

The NetScaler image can be found at
https://citrix.sharefile.com/d/s397e9fccace48009

On Wed, Jul 1, 2015 at 2:22 PM, Aleksander Mogylchenko <
<email address hidden>> wrote:

> Interesting. Can you share Netscaler image?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1470163
>
> Title:
> NetScaler instance is not detecting the interfaces in Mirantis
> Openstack 6.0
>
> Status in Fuel: OpenStack installer that works:
> Incomplete
>
> Bug description:
> We are trying to bring up Netscaler instance (FreeBSD based) on top of
> Mirantis Openstack fuel 6.0. We are booting it as ide disk & also we have
> assigned an interface.
>
> The NetScaler booted up fine, but it couldn’t able to see the network
> interface that was assigned, even though we could see the interface details
> in XML file.
> The following can be seen in the XML of the instance
>
> <interface type='bridge'>
> <mac address='fa:16:3e:6a:98:c6'/>
> <source bridge='qbr247195b8-bf'/>
> <target dev='tap247195b8-bf'/>
> <model type='virtio'/>
> <driver name='qemu'/>
> <alias name='net0'/>
> <address type='pci' domain='0x0000' bus='0x00' slot='0x03'
> function='0x0'/>
> </interface>
>
> I could see the tap interface ('tap247195b8-bf') getting create in the
> host, but not getting detected in the NetScaler.
>
> We could see the interfaces attached in case of Ubuntu also. Only
> FreeBSD based VM’s we are facing this issue.
>
> Is there a known issue with the FreeBSD based VM’s?
>
> Environment:
> Mos: 6.0
> Compute Node: Ubuntu Precise 12.04
> Qemu : 2.0.0+dfsg-2ubuntu1.9
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/fuel/+bug/1470163/+subscriptions
>

--
Thanks & Regards,
Venkateswara Rao Dokku.

Revision history for this message
Aleksander Mogylchenko (amogylchenko) wrote :

I'm confused, because image is the same as in the bug I mentioned. Are you sure you did recompile seabios after updating it with gcc-4.5?

Revision history for this message
Venkateswara Rao Dokku (dvrao-584) wrote :

I gave the link of the image as it was already on the sharefile.

Yes, I did updated sea-bios & after that only I am seeing this issuw.

On Wed, Jul 1, 2015 at 3:38 PM, Aleksander Mogylchenko <
<email address hidden>> wrote:

> I'm confused, because image is the same as in the bug I mentioned. Are
> you sure you did recompile seabios after updating it with gcc-4.5?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1470163
>
> Title:
> NetScaler instance is not detecting the interfaces in Mirantis
> Openstack 6.0
>
> Status in Fuel: OpenStack installer that works:
> Incomplete
>
> Bug description:
> We are trying to bring up Netscaler instance (FreeBSD based) on top of
> Mirantis Openstack fuel 6.0. We are booting it as ide disk & also we have
> assigned an interface.
>
> The NetScaler booted up fine, but it couldn’t able to see the network
> interface that was assigned, even though we could see the interface details
> in XML file.
> The following can be seen in the XML of the instance
>
> <interface type='bridge'>
> <mac address='fa:16:3e:6a:98:c6'/>
> <source bridge='qbr247195b8-bf'/>
> <target dev='tap247195b8-bf'/>
> <model type='virtio'/>
> <driver name='qemu'/>
> <alias name='net0'/>
> <address type='pci' domain='0x0000' bus='0x00' slot='0x03'
> function='0x0'/>
> </interface>
>
> I could see the tap interface ('tap247195b8-bf') getting create in the
> host, but not getting detected in the NetScaler.
>
> We could see the interfaces attached in case of Ubuntu also. Only
> FreeBSD based VM’s we are facing this issue.
>
> Is there a known issue with the FreeBSD based VM’s?
>
> Environment:
> Mos: 6.0
> Compute Node: Ubuntu Precise 12.04
> Qemu : 2.0.0+dfsg-2ubuntu1.9
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/fuel/+bug/1470163/+subscriptions
>

--
Thanks & Regards,
Venkateswara Rao Dokku.

Changed in fuel:
assignee: MOS Linux (mos-linux) → Venkateswara Rao Dokku (dvrao-584)
Revision history for this message
Aleksander Mogylchenko (amogylchenko) wrote :

>Yes, I did updated sea-bios & after that only I am seeing this issuw.
So you haven't seen this bug before the update? Can you try downgrading a package and use it?

Revision history for this message
Alexander Kislitsky (akislitsky) wrote :

No activity on 'Incomplete' bug since 08.11. Moving to 'Invalid'. If you will find more information, please reopen the bug.

Changed in fuel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.