Hello Brian,
here is a discussion about realmd problem:
http://comments.gmane.org/gmane.network.samba.internals/76719
and here is the samba-bugzilla with the alleged fixed in 4.1.7
https://bugzilla.samba.org/show_bug.cgi?id=10524
** Bug watch added: Samba Bugzilla #10524
It's not unmounting automatically so it's and issue until the developers
make some possibility to do that...
Any advice how to unmount sftp mount before suspend automatically with
some script? I tried to make script for pm-utils, but it doesn't run as
superuser so it's unable to unmount...
--
** Changed in: samba
Status: In Progress = Fix Released
--
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/1300878
Title:
panic while renaming file
To manage notifications about
I would say that this points more likely to apache itself (or maybe some
plumbing user-space parts). With that setup both containers use the same
kernel and lxc parts. Only the user-space is from the given distro. I
would not think udev is having much impact as that only runs when
devices change
This bug was fixed in the package python-babel - 1.3+dfsg.1-3ubuntu1
---
python-babel (1.3+dfsg.1-3ubuntu1) utopic; urgency=low
* Merge from Debian unstable (lp: #1320612). Remaining changes:
- Don't try to remove files in debian/rules which aren't there anymore.
python-babel
ten patches.. samba should really gain a MRE to allow pushing point-
releases as SRU
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
I've deployed the proposed package for 0.80.1 on a 25 node cluster and
soaked it with IO's for 24 hours - no problems.
I've also deployed a smaller cluster with OpenStack Icehouse and run the
Cinder tempest API test suite against it - again no problems found.
@Henrik - it would be good to get
@Shang - the 0.80.x series will be supported for 5 years; however I
expect most users will want something newer by +2 years, at which point
the Ceph version from 16.04 will be available via the Ubuntu Cloud
Archive - interim stable release will also be made available but only
with 18 months of
** Changed in: net-tools (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-tools in Ubuntu.
https://bugs.launchpad.net/bugs/174858
Title:
'netstat' doesn't check for sockets using SCTP
Next time I run into it I assumed this is because if there is already a
backup and you try to mv to the same exact backup everything comes
tumbling down but I'll check it out again and if it is different file
under a diff bug
--
You received this bug notification because you are a member of
Public bug reported:
I tried to install clamav.
Ubuntu 12.04 classic
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: clamav-daemon 0.98.1+dfsg-4ubuntu1~ubuntu12.04.2
Uname: Linux 3.9.3-030903-generic i686
ApportVersion: 2.0.1-0ubuntu17.6
AptOrdering:
clamav-daemon: Install
** Tags removed: need-duplicate-check
--
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/1321762
Title:
package clamav-daemon 0.98.1+dfsg-4ubuntu1~ubuntu12.04.2 failed to
There definitely is a drop in performance from Ubuntu vs Debian
normally.. see Virtualbox results:
http://openbenchmarking.org/result/1405217-SO-1405214PL68
However, what can explain the drop in Ubuntu Trusty Native vs Ubuntu
Trusty on LXC?
Oh, btw, about the ping yesterday, I think I should
Public bug reported:
1) % lsb_release -rd
Description:Ubuntu Utopic Unicorn (development branch)
Release:14.10
2) % apt-cache policy uvtool-libvirt
uvtool-libvirt:
Installed: 0~bzr92-0ubuntu1
Candidate: 0~bzr92-0ubuntu1
Version table:
*** 0~bzr92-0ubuntu1 0
500
I assume that apache test is running against the local network
interface, so we can rule out the additional network layers you get for
lxc. Not sure here, Stéphane and Serge can probably come up with
details, but all processes running inside the container probably belong
to the same task group (as
Hi Chuck,
assigning this to you since you are working on packaging the new
version. Could you please add the line
/proc/device-tree/** r,
to the file debian/apparmor/libvirt-qemu
?
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Zulnedi (zul)
** Changed in: libvirt (Ubuntu)
Attaching a debdiff for the backport of trusty's open-vm-tools for
precise HWE kernels as open-vm-tools-lts-trusty
v3 changes:
Changed name from *-hwe to *-lts-trusty
v2 changes:
Add mention of supported HWE kernel to the package descriptions
** Patch added: New open-vm-tools-hwe package for
Attaching a debdiff to update open-vm-tools in trusty so that it
replaces open-vm-tools-hwe upon upgrade from precise.
v3 changes:
Rename prior package from *-hwe to *-lts-trusty
v2 changes:
Add missing Conflicts directive for precise HWE packages
** Patch added: open-vm-tools update for
The patches needed to be updated because the package for Precise needed
to have it's version corrected.
Prior patch: 2:9.4.0-1280544-5ubuntu6
Corrected: 2:9.4.0-1280544-5ubuntu6~precise1
At the same time I changed the naming from open-vm-tools-hwe to open-vm-
tools-lts-trusty as suggested by
Can you explain what ssgyboot=break tells the kernel to do?
Could you upload the guest's /var/log/syslog after reboot?
Please show
echo $?
immediately after the qemu-system-ppc command has exited?
** Also affects: qemu
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
I installed the jessie apache2 packages (locally built) on trusty, and
ran the benchmarks using first it and then with a (hand-built) trusty
apache package. The results are at
http://openbenchmarking.org/result/1405218-PL-TRUSTYHOS17 . The
difference there is within SE. It could still be
I'm not sure if PTS actually uses the system installed apache for it's
tests.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1321415
Title:
Big performance difference between debian
1. ssgyboot-break has no effect in the VM kernel; It is only used by
jade-initrd-2.0.bin ;
kernel cmdline:
[0.00] pcpu-alloc: s28800 r8192 d16256 u53248 alloc=13*4096
[0.00] pcpu-alloc: [0] 0
[0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pag
es:
/var/log/syslog attached as syslog.onboot when file system is dirty ;
Since the VM terminated ; the device should have been umounted ;
** Attachment added: syslog.onboot
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1321028/+attachment/4116987/+files/syslog.onboot
--
You received
Having same problem with squid3 3.3.8-1ubuntu6, running Ubuntu 14.04
within a VirtualBox Vm. Any solution yet?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1214379
Title:
I am thinking since the VM hasn't terminated due to defect 1317603 ,
qemu-system-ppc has to be terminated with kill pid which is not kill
-9 ; I could see some inconsistencies with virtio device file not being
sync'ed ; but the VM did unmount it;
--
You received this bug notification because
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1321415
Title:
Big performance difference between debian and ubuntu guest
My results in unprivileged containers on my own host:
http://openbenchmarking.org/result/1405216-PL-HETZNERUN74
http://openbenchmarking.org/result/1405216-PL-HETZNERUN44
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of
Note that while I marked it confirmed, I don't see this as a bug in lxc.
Since we get the same results on bare metal, I would expect it to be the
case in containers as well, barring drastic differences in kernel
configurations.
I do wonder how much of this could be due to toolchain hardening
Quoting Bryan Quigley (gqu...@gmail.com):
I'm not sure if PTS actually uses the system installed apache for it's
tests.
Indeed looking more closely at the install logs suggests it builds its
own. You can find it in the jessie install under
I wonder if we copy all of .phoronix-test-suite from one container to
the other and run it, what the results will look like.
Indeed, that's the best way to confirm this. I'll give that a try.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Copying failed on missing/different libs.. I'm going to try to recreate
the tests using the ab command/locally installed apache.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1321415
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1316396
Title:
When stopping a node from the web UI that was
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1298784
Title:
Vulnerable to user-interface redressing (e.g.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1311151
Title:
MAAS imports Trusty's 'rc' images by default.
To
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1311765
Title:
missing Module 'crochet' prevents installing
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1314409
Title:
parallel juju deployments race on the same maas
To
We've verified all bugs related to this proposal and updated each bug
accordingly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1317601
Title:
[SRU] SRU New upstream bugfix release
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1310082
Title:
d-i with precise+hwe-s stops at Architecture not
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1310076
Title:
lost connectivity to a node when using
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1313556
Title:
API client blocks when deleting a resource
To
You have been subscribed to a public bug:
i have no impi detection or automatic setting of IMPI in ubuntu 14.4
maas. i have the options pull down menu to select IMPI 1.5 or IMPI 2.0
but none of the impi setting work . manual does not work ether. maas
cannot power up servers.
** Affects: maas
** Description changed:
- i have no impi detention or automatic setting of IMPI in ubuntu 14.4
+ i have no impi detection or automatic setting of IMPI in ubuntu 14.4
maas. i have the options pull down menu to select IMPI 1.5 or IMPI 2.0
but none of the impi setting work . manual does not work
Basically it looks like Debian in LXC might be faster looping back to
itself, but once you do the test even from the host machine, they even
out. Also results from Ubuntu apache installed on Debian Jessie.
I'm going to check to see where the other tests were run from.
Summary Results:
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package maas - 1.5.1+bzr2269-0ubuntu0.1
---
maas (1.5.1+bzr2269-0ubuntu0.1) trusty; urgency=medium
* Stable Release Update (LP: #1317601):
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP:
This bug was fixed in the package maas - 1.5.1+bzr2269-0ubuntu0.1
---
maas (1.5.1+bzr2269-0ubuntu0.1) trusty; urgency=medium
* Stable Release Update (LP: #1317601):
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP:
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package maas - 1.5.1+bzr2269-0ubuntu0.1
---
maas (1.5.1+bzr2269-0ubuntu0.1) trusty; urgency=medium
* Stable Release Update (LP: #1317601):
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP:
This bug was fixed in the package maas - 1.5.1+bzr2269-0ubuntu0.1
---
maas (1.5.1+bzr2269-0ubuntu0.1) trusty; urgency=medium
* Stable Release Update (LP: #1317601):
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP:
This bug was fixed in the package maas - 1.5.1+bzr2269-0ubuntu0.1
---
maas (1.5.1+bzr2269-0ubuntu0.1) trusty; urgency=medium
* Stable Release Update (LP: #1317601):
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP:
This bug was fixed in the package maas - 1.5.1+bzr2269-0ubuntu0.1
---
maas (1.5.1+bzr2269-0ubuntu0.1) trusty; urgency=medium
* Stable Release Update (LP: #1317601):
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP:
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package maas - 1.5.1+bzr2269-0ubuntu0.1
---
maas (1.5.1+bzr2269-0ubuntu0.1) trusty; urgency=medium
* Stable Release Update (LP: #1317601):
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP:
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package maas - 1.5.1+bzr2269-0ubuntu0.1
---
maas (1.5.1+bzr2269-0ubuntu0.1) trusty; urgency=medium
* Stable Release Update (LP: #1317601):
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP:
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for maas has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package maas - 1.5.1+bzr2269-0ubuntu0.1
---
maas (1.5.1+bzr2269-0ubuntu0.1) trusty; urgency=medium
* Stable Release Update (LP: #1317601):
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP:
This bug was fixed in the package maas - 1.5.1+bzr2269-0ubuntu0.1
---
maas (1.5.1+bzr2269-0ubuntu0.1) trusty; urgency=medium
* Stable Release Update (LP: #1317601):
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP:
This bug was fixed in the package maas - 1.5.1+bzr2269-0ubuntu0.1
---
maas (1.5.1+bzr2269-0ubuntu0.1) trusty; urgency=medium
* Stable Release Update (LP: #1317601):
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP:
thanks for your response, i dont get any errors. it is like the software
is there, but not doing anything. i will start to perform some tests so
i can try to fingure out, which package it is. but i can say that when
i was running ubuntu 12.04 server, that maas package commissioned
servers and
** Also affects: ipmitool (Ubuntu)
Importance: Undecided
Status: New
** Also affects: openipmi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
i have trace the issue to the package above. i don't have the resources,
to go deeper. but this is what i have come up with.
** Also affects: freeipmi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
The 1.4 release had known problems around IPMI detection which are
mostly fixed in the 1.5 release which is in trusty (14.04). Please
upgrade to trusty, or if you are still on precise you can try out the
MAAS in the cloud tools archive.
** Changed in: maas (Ubuntu)
Status: New = Invalid
Please confirm if 1.5 solves your problem and can you confirm if you are
running on trusty or precise.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1321885
Title:
IMPI detection
Public bug reported:
The following occurred in my attempt to upgrade from Ubuntu 13.10 to
14.04
Errors were encountered while processing:
sa-compile
Error in function:
A fatal error occurred
Please report this as a bug and include the files
/var/log/dist-upgrade/main.log and
72 matches
Mail list logo
