I run update manager and get this error message
** Package changed: ubuntu = amavisd-new (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
https://bugs.launchpad.net/bugs/1010772
Title:
E: changelog
Public bug reported:
Running:
$ sudo lsb_release -rd
Description:Ubuntu 12.04.3 LTS
Release:12.04
$ uname -a
Linux Ubuntu-Desktop 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14
16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
While updating the qemu-kvm package to the latest
** Attachment added: lspci
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1218137/+attachment/3792342/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
** Attachment added: dmesg log
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1218137/+attachment/3792333/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1218137/+attachment/3792343/+files/syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
** Attachment added: lsusb.txt
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1218137/+attachment/3792334/+files/lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Not sure what happened but after another restart it's working fine. Set
status to Invalid as it can no longer be reproduced.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
Binary package hint: samba
Description:Ubuntu 9.04
Release:9.04
samba-common:
Installed: 2:3.3.2-1ubuntu3.2
Candidate: 2:3.3.2-1ubuntu3.2
Version table:
*** 2:3.3.2-1ubuntu3.2 0
500 http://us.archive.ubuntu.com jaunty-updates/main Packages
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32870447/Dependencies.txt
** Attachment added: DpkgTerminalLog.txt
http://launchpadlibrarian.net/32870448/DpkgTerminalLog.txt
--
Samba server upgrade crashed
https://bugs.launchpad.net/bugs/440683
You received this bug
It is a bug when its impossible to set the initial password so it always
tells you that your password is invalid because there is no password set
for the keyring. The issue here is that the code Ubuntu adds for Nova
client initializes the keyring incorectly.
** Changed in: python-novaclient
Public bug reported:
Package updater downloaded and attempted installation. Failed.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: samba 2:3.6.3-2ubuntu2.2
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
--
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/1009015
Title:
package samba 2:3.6.3-2ubuntu2.2 failed to install/upgrade: subprocess
installed post-installation script returned
You can reproduce this problem very quickly on a freshly installed
Ubuntu 12.04 system with Folsom by following the user manual line for
line due to bug #1064749
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
:
http://192.168.200.135:8774/5aa21f92483b441f89b844421b639f9c/servers/3935bacf-63c5-4b19-9375-f067d75d56e6;,
rel: bookmark}], key_name: doug-pikewerks, image: {id:
f1736056-47ba-49f8-b451-6272595045d6, links: [{href:
http://192.168.200.135:8774/5aa21f92483b441f89b844421b639f9c/images/f1736056-47ba
As pointed out to me by ev0ldave in #openstack the way to fix this is to
figure out exactly what the instance ID is.
$ mysql -u root -p
mysql USE nova;
mysql SELECT id, host, hostname FROM instances;
...
mysql UPDATE instances SET deleted=1, deleted_at=2012-10-10 14:56:30,
vm_state=deleted WHERE
** Also affects: python-novaclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-novaclient in Ubuntu.
https://bugs.launchpad.net/bugs/1020238
Title:
nova client keeps
Public bug reported:
Binary package hint: postfix
I was trying to install procmail with postfix on an amd64 server in
Ubuntu 10.04 and I got the following messages:
debconf: DbDriver config: /var/cache/debconf/config.dat is locked by another
process: Resource temporarily unavailable
Selecting
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/786780
Title:
package postfix (not installed) failed to install/upgrade: subprocess
new pre-installation script returned error exit
Is this supposed to be fixed for qemu-kvm? Or am i supposed to install
another package to get spice support? I'm running oneric and using qemu-
kvm from the main repos, but no spice support seems to be available.
--
You received this bug notification because you are a member of Ubuntu
Server
I have been fighting installing a RAID setup with 8.04 + GRUB for about
20 hours. My old setup used a CF card mounted as /boot but I can't get
that to work with some newer hardware and with grub and 8.04. This
worked fine under 6.x and 7.x... So I give up and set up a md RAID 1
partition as ext2
From my perspective, what needs to happen is that the issue of booting from a
degraded root on kernel software raid needs a simple, easy to implement fix
for those who run fixed configuration machines, I.E. servers and the like.
The provided patches seem to accomplish this goal with a boot
for sure.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728666
I am filing this bug report mainly so that I can refer to it on the
testing tracker as an issue, while still setting the test case to pass.
Note that other than the error message itself, I am not aware of any bad
side effect.
doug@v32
Any word on seeing this package published? This ticket hasn't seen an
update in 4 months. I can confirm that Ubuntu 12.04.3 Server out of the
box on amd64 and i386 will not work with DRDB and requires smb's fixed
debs from #17 and #18 (respectively).
--
You received this bug notification because
Public bug reported:
Binary package hint: irqbalance
the 0.56-1ubuntu1 (2) update in natty has disabled irqbalance with no
configure during the update
Not sure what then intention is, seems to not be in keeping with changelog/bug
fixed
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package:
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in ubuntu.
https://bugs.launchpad.net/bugs/705429
Title:
Latest update disables irqbalance with no offer to configure
--
Ubuntu-server-bugs mailing list
here you go -
As the daemon was by default configured before update
0.56-0ubuntu2
#Configuration for the irqbalance daemon
#Should irqbalance be enabled?
ENABLED=1
#Balance the IRQs only once?
ONESHOT=0
After update to 0.56-1ubuntu2 (no configure screen pops up
#Configuration for the
Thanks.
Jamie Strandboge wrote:
Upstream released 2.4.3 to address both the vulnerability and the known
regressions. Reviewing upstream's mailing list shows no regressions so
far with this version. I've sync'd Jaunty with 2.4.2-6, which brings its
patches in line with upstream 2.4.3, so I am
Mathias Gug wrote:
One workaround is to put all of the CA certs in the trusted CA
certificate file.
Yes, that is what we have had to do.
The real fix is to get the gnutls people to support certificate
directories, like OpenSSL. Why the rush to convert to gnutls
when it has so many issues.
Copy of note sent on 1/8/2009:
Attached are the server cert (auth2.it.anl.gov), the intermediate cert
(f0a38a80.0)
and the CA self signed cert (7651b327.0) a debug version of verify.c
and partial output of an ldapsearch using the debug.c
My patch has been #if 0'ed out at line 151.
Lets
Mathias Gug wrote:
@Andy:
Could you describe the X509 certs and CA you're using?
We were using ldap and Verisign, and the root CA was a V2 from 1999
which signed an intermediate cert that signed the server certs.
I submitted to gnutls a few changes to allow for stoping at the
intermediate
** Package changed: glibc (Ubuntu) = libnss-ldap (Ubuntu)
--
nscd leaking memory using libnss-ldap
https://bugs.launchpad.net/bugs/292971
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in ubuntu.
--
Ubuntu-server-bugs
Public bug reported:
Binary package hint: samba
Hi,
I haven't investigated fully yet, but this bug report is fairly similar
to Bug #546896. However, first, the final error message is different
and, second, the platform is 32-bit not 64-bit.
Doug
ProblemType: Package
Architecture: i386
Date
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/42235193/AptOrdering.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42235194/Dependencies.txt
** Attachment added: Dmesg.txt
http://launchpadlibrarian.net/42235195/Dmesg.txt
** Attachment
is the
case that, no matter what I did, installing with apt-get or aptitude
failed with the same error, regardless if I was reinstalling or
installing after a remove or after a purge).
HTH,
Doug
--
package samba-common-bin 2:3.4.0-3ubuntu5.6 failed to install/upgrade:
subprocess installed post
.
HTH,
Doug
--
package samba-common-bin 2:3.4.0-3ubuntu5.6 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 2
https://bugs.launchpad.net/bugs/550022
You received this bug notification because you are a member of Ubuntu
Server Team, which
Hi,
Regarding the workaround I describe in Bug #550022, I should also note
that I had to uninstall package nautilus-share before I could
uninstall samba-common-bin. After the workaround, I of course
reinstalled nautilus-share.
HTH,
Doug
--
samba-common-bin postinst returned error status 2
I don't think we really want mox as a requirement; instead we should be
sorting out how to make sure mox is required only for testing.
** Changed in: horizon (Ubuntu Trusty)
Assignee: (unassigned) = Doug Fish (drfish)
--
You received this bug notification because you are a member of Ubuntu
** Changed in: horizon
Assignee: (unassigned) = Doug Fish (drfish)
** Changed in: horizon (Ubuntu Trusty)
Assignee: Doug Fish (drfish) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https
The update of yesterday fixes issues I was having with vmvga.
qemu-keymaps 2.0~git-20140317.2bda660-0ubuntu1 all
QEMU keyboard maps
qemu-kvm 2.0~git-20140317.2bda660-0ubuntu1 amd64
QEMU Full virtualization on x86 hardware
** Changed in: oslo
Assignee: Doug Hellmann (doug-hellmann) = Morgan Fainberg (mdrnstm)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1301036
Title
My comment may not apply to this, but I'll make it anyhow:
I upgraded my host server from ubuntu 12.04 to 14.04. Afterwards, none
of my desktop VM's worked (I haven't even tried the server VM's yet). I
made a new guest VM using the exact same virst-install command I had
used for the original VM
Public bug reported:
I upgraded my host server from ubuntu 12.04 to 14.04. Afterwards, none
of my desktop VM's worked (I haven't even tried the server VM's yet).
During login the VM's complained about being unable to detect the
graphics card (screenshot will be posted). Proceeding results in a
** Attachment added: screen shot of low graphics message box
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+attachment/4085756/+files/1404-vm-low-graphics.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in
** Attachment added: screen shot of resulting jibberish screen
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+attachment/4085757/+files/1404-vm-jibberish.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in
** Attachment added: a typical .xml file
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+attachment/4085765/+files/desk_tt.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Attachment added: a typical xml file, installed under a 12.04 host.
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308756/+attachment/4085766/+files/desk_ss.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in
All the differences in xml files, one from installing a new guest VM on
a 12.04 server as the host and one installing the same guest again from
the same server upgraded / updated to a 14.04 server host.
** Attachment added: All differences between 12.04 and 14.04 host xml file
are you connecting to a vncserver service running within the guest VM?
Or are you connecting to the qemu VNC head on the server which hosts the
virtual machines?
I connect to the host server IP address port 5900.
Also, on which host and environment are you seeing the 'low graphics
mode' dialog
By the way, if I do the opposite: On an new Ubuntu 14.04 server installation
with a newly installed guest Ubuntu dekstop; Use virsh edit and change the
machine type to pc-1.0, then the quest VM has the same issues upon login.
The information requested above:
doug@s15:~$ dpkg -l | egrep 'qemu
with this command (which will
use the cirrus driver, by default):
sudo virt-install -n desk_tt4 -r 8192 --disk
path=/home/doug/img/desk_tt4.img,bus=virtio,size=50 -c trusty-desktop-
amd64-20140417.iso --machine pc-1.0 --network bridge=br0,model=virtio
--graphics vnc,listen=0.0.0.0 --noautoconsole -v
Serge,
Thanks for the information and the link to even more useful information.
So, specifying vram size doesn't work, that is both good to know and
explains some things.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
It is the configuration file that is incorrect, not the serverguide, so I am
setting this one to invalid for the serverguide.
However, I also checked the trusty and utoptic master files, and they are O.K.
References:
I've opened https://bugs.launchpad.net/horizon/+bug/1381472 to address
the issue Gloria describes in comment 20
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1379761
Title:
Asset
@Coeur: I entered this bug report over 11 months ago, and have simply
ignored the error ever since. I haven't had any problems.
--
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/1257186
*** This bug is a duplicate of bug 1424466 ***
https://bugs.launchpad.net/bugs/1424466
** This bug has been marked a duplicate of bug 1424466
Devel package not installable in 14.04.2 (mesa-lts-utopic
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
This doesn't work -
Depends: libsdl1.2debian (= 1.2.15-8ubuntu1), libasound2-dev, libcaca-dev,
libglu1-mesa-dev | libglu-dev, ect.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libsdl1.2-dev (not installed)
ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic
** Changed in: oslo.messaging
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to oslo.messaging in Ubuntu.
https://bugs.launchpad.net/bugs/1291701
Title:
pluggability for matchmakers in
** Changed in: oslo.messaging
Status: Fix Committed = Fix Released
** Changed in: oslo.messaging
Milestone: None = 1.8.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to oslo.messaging in Ubuntu.
** Changed in: oslo.messaging
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to oslo.messaging in Ubuntu.
https://bugs.launchpad.net/bugs/1432966
Title:
RuntimeError: dictionary changed size
** Changed in: glance
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
https://bugs.launchpad.net/bugs/1419823
Title:
Nullable image description crashes v2 client
To
** Changed in: python-ceilometerclient
Status: Fix Committed = Fix Released
** Changed in: python-ceilometerclient
Milestone: None = 1.3.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-ceilometerclient in Ubuntu.
Chad wrote:
Xavier wrote that this needs to be moved somewhere else.
Does anyone know how to do that?
If someone can explain to me what needs to happen,
I changed the trusty target from 14.04.2 (which is in the past) to
14.04.3 (which is in the future, albeit, not far off)
** Changed in:
** Changed in: oslo.log
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-eventlet in Ubuntu.
https://bugs.launchpad.net/bugs/1459726
Title:
api servers hang with 100% CPU if syslog restarted
To
** Changed in: python-cinderclient
Status: Fix Committed = Fix Released
** Changed in: python-cinderclient
Milestone: None = 1.3.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cinderclient in Ubuntu.
** Changed in: python-cinderclient
Status: Fix Committed = Fix Released
** Changed in: python-cinderclient
Milestone: None = 1.3.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cinderclient in Ubuntu.
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1485694
, just use primitive
commands and not these higher level utilities (that I neither use or
know anything about). For example use:
grep MHz /proc/cpuinfo
to observe CPU frequencies.
The commit that, I think, fixes this issue is:
commit 6c1e45917dec5e7c99ba8125fd8cc50f6e482a21
Author: Doug Smythies
Public bug reported:
Kernel 4.2 includes a significant commit
(87549141d516aee71d511138e27117c41e8aef68), after the patch the files
and directory are present even if the CPU is offline. If the CPU is
offline, writing to those files isn't allowed and so the echo in
94cpufreq fails.
If the failed
** Changed in: python-glanceclient
Status: Fix Committed => Fix Released
** Changed in: python-glanceclient
Milestone: None => 1.1.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to requests in Ubuntu.
No pagination in the current code; I'm sure this is still an issue
https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/nova.py#L734
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
I'm aware of this behavior happening in earlier versions of Horizon - I
do need to double check that it happens on the latest code.
As an ugly workaround this panel can be disabled in a large environment.
** Changed in: horizon
Status: New => Confirmed
** Changed in: horizon
** Changed in: neutron
Status: Fix Committed => Fix Released
--
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/1497309
Title:
l3-agent unable to parse output from ip netns list
** Changed in: nova
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1418590
Title:
Instance is left in ACTIVE state even if rescue fails
** Changed in: nova
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1516652
Title:
'lxd' is an unsupported hypervisor type
To manage
I think, but am not sure, this bug report is the root issue for failure
of the daily server 64 iso installation when "samba server" is selected.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
As of kernel 4.4-rc1 this bug becomes invalid, as the kernel was patched such
that this issue no longer occurs.
I'll wait until kernel 4.4 is finished, check again, then set the status of
this bug report to invalid.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: pm-utils (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1493156
Title:
pm-suspend aborts if highest numbered CPU
This issue was fixed in the openstack/neutron 7.0.2 release.
--
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/1497309
Title:
l3-agent unable to parse output from ip netns list
This issue was fixed in the openstack/python-ironicclient 1.1.0 release.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-ironicclient in Ubuntu.
https://bugs.launchpad.net/bugs/1489059
Title:
"db type could not be determined"
Same for me:
Feb 29 14:45:51 DOUG-64 named[1202]: connection refused resolving
'19.82.133.155.in-addr.arpa/PTR/IN': 37.59.161.64#53
Feb 29 15:35:01 DOUG-64 systemd[1]: Stopping BIND Domain Name Server...
Feb 29 15:35:01 DOUG-64 named[1202]: received control channel command 'stop'
Feb 29 15:35:01
Yes, isc-dhcp - 4.3.3-5ubuntu8 fixes the issue with the dhclient stuff
that caused this:
Feb 26 14:05:21 DOUG-64 kernel: [ 17.518717] audit: type=1400
audit(1456524321.220:10): apparmor="DENIED" operation="open"
profile="/sbin/dhclient" name="/etc/ssl/
This issue was fixed in the openstack/nova 12.0.1 release.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1508230
Title:
regression in cloning raw image type with ceph
To manage
This issue was fixed in the openstack/glance_store 0.11.0 release.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-ironicclient in Ubuntu.
https://bugs.launchpad.net/bugs/1489059
Title:
"db type could not be determined"
Yes, same for me. Setting back to confirmed.
bind9-host 1:9.10.3.dfsg.P2-5, not sure why out package numbers differ.
** Changed in: bind9 (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
>From Stephan comment 14:
"Hm, of course, if one starts dhclient in debug mode (foreground) by
adding a "-d", everything does work."
Yes, that does seem to work, but only for about another day, at least in
my case. Thereafter, my ISP stopped returning my domain name, host name
and some other
1:9.10.3.dfsg.P2-5 has the same issue, but the apparmor issue is fixed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1549788
Title:
bind9 9.10.3.dfsg.P2-4 crash on exit
To manage
This issue was fixed in the openstack/python-glanceclient 2.0.0 release.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-ironicclient in Ubuntu.
https://bugs.launchpad.net/bugs/1489059
Title:
"db type could not be determined"
This issue was fixed in the openstack/nova 13.0.0.0b3 development
milestone.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1369465
Title:
nova resize doesn't resize(extend) rbd disk
This issue was fixed in the openstack/nova 13.0.0.0b3 development
milestone.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1398999
Title:
Block migrate with attached volumes copies
This issue was fixed in the openstack/nova 12.0.2 release.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1369465
Title:
nova resize doesn't resize(extend) rbd disk files when using
Correction 1: Stefan not Stephan, sorry.
Correction 2: Things broke down about another 1/2 day after the lease times
changes to 1 hour. The client didn't seem to release this and resorted to
broadcast type discover stuff. Then it was getting leases for 5 minutes, and
the cycle continued until I
91 matches
Mail list logo
