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
** Changed in: neutron
Milestone: None => mitaka-1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1460177
Title:
Support metadata service with IPv6-only tenant network
To
** 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
Server Team, which is subscribed to neutron in Ubuntu.
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
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1460177
Title:
Support metadata service with IPv6-only tenant network
To
** Tags removed: rfe
** Tags added: rfe-approved
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1460177
Title:
Support metadata service with IPv6-only tenant network
To manage
** 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
Server Team, which is subscribed to neutron in Ubuntu.
** Changed in: neutron
Milestone: None => mitaka-1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1501772
Title:
Metadata proxy process errors with binary user_data
To manage
** 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
Server Team, which is subscribed to neutron in Ubuntu.
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1369386
Title:
ipset_enabled = True default is not
anyone out there?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1273877
Title:
neutron-plugin-nicira should be renamed to neutron-plugin-vmware
To manage notifications about this
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
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1273877
Title:
neutron-plugin-nicira should
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
this down to the fact that the keystone-manage db_sync
(defined in keystone.postinst) is done outside the conditional block that
verifies the default value of config_db defined in the keystone.templates.
Hope this help, but if I am completely off track I apologize for the
noise.
Cheers,
Armando
Public bug reported:
no se nada mas! puede haber sido un error MIO! algo hice mal
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: winbind 2:3.6.3-2ubuntu2.3
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
Uname: Linux 3.2.0-31-generic-pae i686
ApportVersion:
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1055896
Title:
package winbind 2:3.6.3-2ubuntu2.3 failed to install/upgrade: el
subproceso instalado el script post-installation
sin duda yo fui el que' metio la pata en algo pero no me doy cuenta
en que (AJO)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1055896
Title:
package winbind 2:3.6.3-2ubuntu2.3
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
|/
Public bug reported:
This package can't install
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: clamav-freshclam 0.97+dfsg-2ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
Architecture: i386
Date: Thu Jul 28 22:33:30 2011
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/817854
Title:
package clamav-freshclam 0.97 dfsg-2ubuntu1.1 failed to
install/upgrade: el subproceso instalado el script
My temporal solution:
wget
http://mirror.pnl.gov/ubuntu//pool/main/o/openssh/openssh-client_5.5p1-4ubuntu5_i386.deb
sudo dpkg -i openssh-client_5.5p1-4ubuntu5_i386.deb
Before:
$ ssh -p 2121 in...@200.57.xx.xx
Read from socket failed: Connection reset by peer
After:
$ ssh -p 2121
@Matthias and Scott
I can understand your frustration, as well -- I was an official
developer for another distro circa 2003-2006. Dealing with emotions,
cares, and the people attached to them, via bug reports, can be
difficult, and is almost always frustrating.
However, the statements made
I stumbled upon this issue last night when trying out Lift / Scala, and
the getting started guide has an example using maven. Installed it,
immediate failure when I tried to run. The program crashes and
described in this and related bugs, because of libraries being out of
sync with maven2.
This
23 matches
Mail list logo
