On 28 May 2014 11:56, Jeremy Stanley <email address hidden> wrote:
> *** This bug is a duplicate of bug 1309195 ***
> https://bugs.launchpad.net/bugs/1309195
>
> There is no real benefit to switching this particular bug to private at
> this point, since it has already been public for several days and copies
> of it are now on mailing list archives and in other places indexed by
> Web search engines. Aaron was merely trying to point out that you have
> the option of keeping future bugs of this nature private to allow the
> developers some time to work on resolving them prior to publication.
>
> ** Information type changed from Private Security to Public Security
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1322945
>
> Title:
> Attaching a IPv6 private subnet to a L3 Router, breaks it and its IPv4
> Floating IPs
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/neutron/+bug/1322945/+subscriptions
>
Okay Jeremy, got it... Sorry for that... :-)
On 28 May 2014 11:56, Jeremy Stanley <email address hidden> wrote:
> *** This bug is a duplicate of bug 1309195 *** /bugs.launchpad .net/bugs/ 1309195 /bugs.launchpad .net/bugs/ 1322945 /bugs.launchpad .net/neutron/ +bug/1322945/ +subscriptions
> https:/
>
> There is no real benefit to switching this particular bug to private at
> this point, since it has already been public for several days and copies
> of it are now on mailing list archives and in other places indexed by
> Web search engines. Aaron was merely trying to point out that you have
> the option of keeping future bugs of this nature private to allow the
> developers some time to work on resolving them prior to publication.
>
> ** Information type changed from Private Security to Public Security
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Attaching a IPv6 private subnet to a L3 Router, breaks it and its IPv4
> Floating IPs
>
> To manage notifications about this bug go to:
> https:/
>