Most guests generate this on first boot. I haven't looked into how newer
versions of ubuntu handle this though I noticed in 14.04 this file doesn't
exist anymore but I figure it's doing it somewhere else.
Aaron
On Wed, Aug 13, 2014 at 9:03 PM, Jian Wen wrote:
> Ordering of vNICs is not 100% g
Ordering of vNICs is not 100% guaranteed for the cloud images which are not
shipped with
/etc/udev/rules.d/70-persistent-net.rules.
e.g. attaching a port and deattaching another port, then reboot the
instance.
2014-08-12 15:52 GMT+08:00 Aaron Rosen :
> This bug was true in grizzly and older (and
This bug was true in grizzly and older (and was reintroduced in icehouse
for a few days but was fixed before the nova icehouse shipped).
Aaron
On Mon, Aug 11, 2014 at 7:10 AM, CARVER, PAUL wrote:
>Armando M. [mailto:arma...@gmail.com] wrote:
>
>
>
> >>On 9 August 2014 10:16, Jay Pipes wro
Thanks, Paul!
On 08/11/2014 10:10 AM, CARVER, PAUL wrote:
Armando M. [mailto:arma...@gmail.com] wrote:
On 9 August 2014 10:16, Jay Pipes wrote:
Paul, does this friend of a friend have a reproduceable test
script for this?
We would also need to know the OpenStack release where this is
Armando M. [mailto:arma...@gmail.com] wrote:
>>On 9 August 2014 10:16, Jay Pipes wrote:
>>Paul, does this friend of a friend have a reproduceable test
>>script for this?
>We would also need to know the OpenStack release where this issue manifest
>itself. A number of bugs have been raised in the
Hi Paul, as I know, nova can guarante the ordering of vNICS, can you provide
the reproduceable test script for this, I am glad to test it
At 2014-08-10 01:16:16, "Jay Pipes" wrote:
>Paul, does this friend of a friend have a reproduceable test script for
>this?
>
>Thanks!
>-jay
>
>On 08/0
On 9 August 2014 10:16, Jay Pipes wrote:
> Paul, does this friend of a friend have a reproduceable test script for
> this?
>
> Thanks!
> -jay
>
>
We would also need to know the OpenStack release where this issue manifest
itself. A number of bugs have been raised in the past around this type of
is
Paul, does this friend of a friend have a reproduceable test script for
this?
Thanks!
-jay
On 08/08/2014 04:42 PM, Kevin Benton wrote:
If this is true, I think the issue is not on Neutron side but the Nova
side.
Neutron just receives and handles individual port requests. It has no
notion of th
If this is true, I think the issue is not on Neutron side but the Nova
side.
Neutron just receives and handles individual port requests. It has no
notion of the order in which they are attached to the VM.
Can you add the Nova tag to get some visibility to the Nova devs?
On Fri, Aug 8, 2014 at 11
I'm hearing "friend of a friend" that people have looked at the code and
determined that the order of networks on a VM is not guaranteed. Can anyone
confirm whether this is true? If it is true, is there any reason why this is
not considered a bug? I've never seen it happen myself.
To elaborate,
10 matches
Mail list logo
