** Changed in: neutron
Importance: Undecided => Low
** Changed in: neutron
Milestone: None => pike-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656010
Title:
Incorrect notification to no
This bug is > 180 days without activity. We are unsetting assignee and
milestone and setting status to Incomplete in order to allow its expiry
in 60 days.
If the bug is still valid, then update the bug status.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
This bug is > 180 days without activity. We are unsetting assignee and
milestone and setting status to Incomplete in order to allow its expiry
in 60 days.
If the bug is still valid, then update the bug status.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
This bug is > 180 days without activity. We are unsetting assignee and
milestone and setting status to Incomplete in order to allow its expiry
in 60 days.
If the bug is still valid, then update the bug status.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Changed in: neutron
Milestone: ocata-1 => newton-rc2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1622002
Title:
dhcp_release6 can be called when it is not present
To manage notifications a
** Tags added: newton-rc-potential
** Changed in: neutron
Milestone: newton-rc1 => ocata-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1622002
Title:
dhcp_release6 can be called when it is no
Ryan should give a look at this, please bear in mind that we are in the
process of switching to the openstack client and as such we may favor
fixing issues in the OSC plugin rather than native neutronclient, which
I expect to be signaled for deprecation as soon as Ocata opens up.
** Also affects:
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen th
This bug is > 172 days without activity. We are unsetting assignee and
milestone and setting status to Incomplete in order to allow its expiry
in 60 days.
If the bug is still valid, then update the bug status.
** Changed in: neutron
Status: New => Incomplete
--
You received this bug noti
This bug is > 172 days without activity. We are unsetting assignee and
milestone and setting status to Incomplete in order to allow its expiry
in 60 days.
If the bug is still valid, then update the bug status.
** Changed in: neutron
Status: Confirmed => Incomplete
--
You received this bu
This bug is > 172 days without activity. We are unsetting assignee and
milestone and setting status to Incomplete in order to allow its expiry
in 60 days.
If the bug is still valid, then update the bug status.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
This bug is > 172 days without activity. We are unsetting assignee and
milestone and setting status to Incomplete in order to allow its expiry
in 60 days.
If the bug is still valid, then update the bug status.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I am not biased one way or the other and I can see both sides of the
arguments. Based on the lack of consensus and in the absence of someone
volunteering to resolve/define the course of action, I can't see how
this can be targeted/approved.
--
You received this bug notification because you are a
** Changed in: neutron
Milestone: mitaka-1 => None
** Tags removed: rfe-approved
** Changed in: neutron
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460177
** Changed in: neutron
Milestone: None => mitaka-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460177
Title:
Support metadata service with IPv6-only tenant network
To manage notifications ab
** Changed in: neutron
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460177
Title:
Support metadata service with IPv6-only tenant network
To manage notificatio
** Tags removed: rfe
** Tags added: rfe-approved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460177
Title:
Support metadata service with IPv6-only tenant network
To manage notifications about th
** Changed in: neutron
Milestone: None => mitaka-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501772
Title:
Metadata proxy process errors with binary user_data
To manage notifications about
** Changed in: neutron
Importance: Undecided => Low
** Changed in: neutron
Milestone: None => mitaka-1
** Tags added: liberty-rc-potential unittest
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
It sounds to me then that (and please bear with me if I am completely
off here) file [1] would need to include more just than simply the
python code? Or have *-aas services depend on neutron-common?
Having said that, I think we'd need to have a more comprehensive
discussion also on how the decomp
Perhaps there are some preliminary steps that need to be executed ahead
of the testsuite in the package build process? As far as I can tell I
see nothing that could be missing from a source codebase standpoint.
** Changed in: neutron
Status: New => Incomplete
--
You received this bug not
** Changed in: neutron
Milestone: None => kilo-1
** Changed in: neutron
Importance: Undecided => Medium
** Tags added: juno-backport-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/138
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1369386
Title:
ipset_enabled = True default is not upgrade friendly
To ma
anyone out there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273877
Title:
neutron-plugin-nicira should be renamed to neutron-plugin-vmware
To manage notifications about this bug go to:
https:/
I am happy to carry out the work if pointed in the right direction.
Thanks,
Armando
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273877
Title:
neutron-plugin-nicira should be renamed to neutron-p
Public bug reported:
This is not a bug per se, but more like a feature request.
As per:
https://blueprints.launchpad.net/neutron/+spec/nicira-plugin-renaming
During the Icehouse timeframe the Nicira NVP plugin is being renamed to
VMware NSX plugin.
Canonical's packages for Neutron should refle
** Changed in: glance
Status: New => Confirmed
** Changed in: glance
Assignee: (unassigned) => Armando Migliaccio (armando-migliaccio)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
I think I found a problem with the current keystone debian packaging
rules (latest revision: http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/quantal/keystone/quantal/revision/34).
When I try to install keystone in my system I get the following
stacktrace:
Traceback (mos
Hi Chuck, that'll do ;)
Thanks, verified successfully.
** Tags removed: verification-failed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000403
Title:
[SRU] mult
I followed instructions on:
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification
and I get the following package:
dpkg -l nova-scheduler | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-requir
30 matches
Mail list logo
