Public bug reported:
Using pacemaker version: 1.1.10+git20130802-1ubuntu2.3
On ubuntu: Ubuntu 14.04.4 LTS
Corosync upgrade to 2.3.3-1ubuntu2 leaves pacemaker in a stopped state.
Specifically from version 2.3.3-1ubuntu1
I have attached logs from such upgrade.
** Affects: pacemaker (Ubuntu)
** Changed in: python-openstackclient (Ubuntu)
Assignee: (unassigned) => AMIT KUMAR (maurya0092)
** Changed in: python-ceilometerclient (Ubuntu)
Assignee: (unassigned) => AMIT KUMAR (maurya0092)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Public bug reported:
I received the following message when upgrading cloud-init in Ubuntu Xenial:
/var/lib/dpkg/info/cloud-init.postinst: 206:
/var/lib/dpkg/info/cloud-init.postinst: -f: not found
I looked at the script, and there appear to be missing brackets around the
test. Specifically, lin
*** This bug is a duplicate of bug 1500581 ***
https://bugs.launchpad.net/bugs/1500581
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1500581, so it is being marked as such. Please look
I mean vm hang when memory >= 1100G (1024G when enable ide cdrom)
instead of 1.5G.
If disable hpet, the vm will hang at
acpi_ex_system_memory_space_handler when memory >= 1100G
If disable kvm, vm is good when memory <= 1020G, but also hang when
memory >= 1024G.
There is no critical information
Hi,
this should be fixed in libvirt 1.3.1-1ubuntu8. I'm not sure why it
didn't get auto-closed.
Please report if this is stlil broken for you.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server
** No longer affects: heat
--
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/1515768
Title:
Instance creation fails with libvirtError: Unable to create tap
device: Device or resource bu
Ok, so two things I've found are that
1. tcg emulated vms can't be migrated (this doesn't apply to you)
2. pc-1.0-qemu-kvm as the source machine type doesn't actually work. What
works for me is when i set the machine type to pc-1.0, then set
allow_incoming_qemukvm=1 in /etc/libvirt/qemu.conf on
Adam has built the initial version desired for upload:
https://launchpad.net/~adam-stokes/+archive/ubuntu/juju-pkg
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1545913
Title:
[F
This bug was fixed in the package dh-golang - 1.12ubuntu1
---
dh-golang (1.12ubuntu1) xenial; urgency=medium
* Follow /usr/bin/go symlink when computing Built-Using. (LP:
#1564124)
-- Michael Hudson-Doyle Thu, 31 Mar
2016 11:42:07 +1300
** Changed in: dh-golang (Ubuntu)
** Description changed:
+ FFe justification:
+
+ The largest changes are in 1.5.7-1 -> 1.5.7-2, which allows for end
+ users to use unbound without configuring /etc/default/unbound in the
+ general case. Additionally, some chroot cruft in debian as been cleaned
+ up.
+
+ Removing the default fil
** Summary changed:
- Please merge unbound 1.58-1 from Debian unstable
+ [FFe] Please merge unbound 1.58-1 from Debian unstable
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to unbound in Ubuntu.
https://bugs.launchpad.net/bugs/1556308
** Branch linked: lp:~smoser/cloud-init/trunk.1562918
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1562918
Title:
cloud-init does not create defined users
To manage notificati
Leander,
I'd appreciate you giving the linked branch a test if you're up for it.
I dont have time at the moment and probably wont until next week.
You can either build a deb with:
./packages/bddeb
or just apply the diff (copy in the new cloudinit/distros/__init__.py
Thanks.
--
You received
Public bug reported:
juju list-credentials --show-secrets does not display password data,
unless used with --format yaml.
The following commands all fail to show additonal information using
--show-secrets
juju list-credentials --show-secrets
juju list-credentials --format json --show-secrets
juj
Public bug reported:
If credentials.yaml contains invalid syntax, the error is
ERROR credentials.blarhg.google.credentials: expected string, got map
which does not accurately convey 'blarhg' is not valid syntax.
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
--
Public bug reported:
It would be nice to include a tag of the environment name from my
credentials file.
aws:
default-credential: balloons
balloons:
auth-type: access-key
access-key: XXXxxx
secret-key: xxx
Given those credentials, I expect
Leander,
Thanks for the bug report. Sorry for the regression.
I suspect that you can work around the issue by just putting your user into a
group. Ie, you add 2 groups, but your user is not in either one of them.
We'll get this fixed.
--
You received this bug notification because you are a
Just to be sure before I mark this as affecting upstream, could you
try adding more memory, maybe -m 1024?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc
Public bug reported:
When a cloud is not found in your credentials file, the credentials are
not listed. In addition, the credentials error given is confusing, and
non-consistent.
nskaggs@pixel:~$ juju list-credentials
ERROR removing secrets from credentials for cloud maas18: cloud maas18 not fou
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/b
Same issue. Stopped on the exact same spot.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To manage notification
Public bug reported:
This is probably because it's just checking the owner of /usr/bin/go --
instead, it should follow links and report the owner of the ultimate
binary.
** Affects: dh-golang (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
zarej, refer to Bug 1512344 - this is a known problem but it's not
something that's able to be fixed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1522890
Title:
package nginx-core
This is not a bug in `nginx`. You have to shut off any other web server
running on port 80 in order to install NGINX and get it to run
automatically during setup. You run into the same issues installing
Apache when there's another thing running on Port 80.
Marking Invalid.
** Changed in: nginx
I used this package to build docker 1.10 in my ppa:
https://launchpad.net/~mwhudson/+archive/ubuntu/scratch/+packages, which
seems like an adequate test to me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of
I was unable to install nginx package if port 80 was opened. I need to
free port 80 in order to install nginx.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1522890
Title:
package ng
hi all
I'm trying upgrading from maas 1.8.2 to the latest 1.9.1 version via apg-get
update / upgrade commands and the mass update hangs exactly at:
* Stopping web server apache2
This bug was fixed in the package tgt - 1:1.0.63-1ubuntu1
---
tgt (1:1.0.63-1ubuntu1) xenial; urgency=medium
* Merge from Debian (LP: #1555700). Remaining changes:
- Drop glusterfs support, package not in main.
- debian/control
- debian/rules
- debian/tests/{ad
xnox, there is this bug: https://bugs.launchpad.net/juju-
core/+bug/1547665
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1545913
Title:
[FFe] juju-core 2.0
To manage notificati
No, there is no KVM local provider in Juju 2.0. Product management has
made the determination that the lxd tool provides the needed
functionality for both the lxc and kvm use cases. lxd in Juju 2.0 will
be the answer.
--
You received this bug notification because you are a member of Ubuntu
Server
Looks like the issue can be worked around by calling Supernet() with
prefixlen_diff=0 at the end of the computation. I have the impression
that blanking the host part and shifting the network mask are done in
the wrong order, but I haven't seen the code.
New program:
from sys import argv
import i
Override component to main
lua-lpeg 0.12.2-1 in xenial amd64: universe/interpreters/optional/100% -> main
lua-lpeg 0.12.2-1 in xenial arm64: universe/interpreters/optional/100% -> main
lua-lpeg 0.12.2-1 in xenial armhf: universe/interpreters/optional/100% -> main
lua-lpeg 0.12.2-1 in xenial i386: u
squid3-3.5.12-1ubuntu3 uploaded already by stgraber handled using the
dpkg-maintscript-helper to clean up the old /etc/init.d/squid3 file.
This debdiff handles the second task of removing the check on how to
restart squid and just calls invoke-rc.d squid restart unconditionally.
I've tested this
Public bug reported:
When using the IPv4Network.Supernet() call, the resulting address is
calculated incorrectly. Instead of presenting the all-zeros address in
the host part, the first bit of the host part is kept as it was, causing
an incorrect address to be displayed. This only appears to be a
Could you try this using upstream qemu?
git clone http://git.qemu.org/git/qemu.git
cd qemu
sudo apt-get -y build-dep qemu
./configure --target-list=ppc64-softmmu
make
cd ppc64-softmmu
./qemu-system-ppc64 [...]
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Changed in: lua-lpeg (Ubuntu)
Status: New => Fix Committed
** Changed in: lua-lpeg (Ubuntu)
Assignee: Ubuntu Server Team (ubuntu-server) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
htt
The attachment "Xenial Patch" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you a
** Summary changed:
- [FFE] Sync ethtool 1:4.5-1 (main) from Debian testing (main)
+ [FFe] Sync ethtool 1:4.5-1 (main) from Debian testing (main)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ethtool in Ubuntu.
https://bugs.launchpad
** Patch added: "Xenial Patch"
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+attachment/4617458/+files/fix-lp-1563089-xenial.debdiff
** Changed in: corosync (Ubuntu Wily)
Status: New => In Progress
** Changed in: corosync (Ubuntu Wily)
Importance: Undecided => Hig
Ubuntu Server Team now subscribed.
** Changed in: lua-lpeg (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1546957
Title:
[MIR] lua-lpeg, need
(Closed per discussion in the rh bug)
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/584862
Title:
libvirt lau
** Also affects: corosync (Ubuntu Wily)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1563089
Title:
Memory Leak when new cluster confi
** Changed in: corosync (Ubuntu)
Status: New => In Progress
** Changed in: corosync (Ubuntu Trusty)
Status: New => In Progress
** Changed in: corosync (Ubuntu)
Importance: Undecided => High
** Changed in: corosync (Ubuntu Trusty)
Importance: Undecided => High
** Changed in:
** Description changed:
[Environment]
Trusty 14.04.3
Packages:
ii corosync 2.3.3-1ubuntu1
amd64Standards-based cluster framework (daemon and modules)
ii libcorosync-common4 2.3.3-1ubuntu1
Debian testing now has the maintenance release 3.5.15.
Changes to squid-3.5.15 (23 Feb 2016):
- Bug 3870: assertion failed: String.cc: 'len_ + len <65536' in
ESI::CustomParser
- Fix multiple assertion on String overflows
- Fix unit test errors on MacOS
- Better ha
** Summary changed:
- [FFe Needed] Update nginx to 1.9.13.
+ [FreezeException Needed] Update nginx to 1.9.13.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393
Title:
[FreezeExc
Hi,
looking at the information in the Description, it looks like you still
have /dev/nbd0 attached to the file you're using in qemu. Just to be
sure, does this still happen when you disconnect that first?
--
You received this bug notification because you are a member of Ubuntu
Server Team, whic
Yes. I only mounted (a different file) to troubleshoot what was going
on. The issue was happening before and after mounting. I have since
unmounted it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchp
You have been subscribed to a public bug by Jon Grimm (jgrimm):
qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image
as part of the certification process. This on an IBM ppc64le in PowerVM
mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no
error output.
ubunt
** Description changed:
qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image
as part of the certification process. This on an IBM ppc64le in PowerVM
mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no
error output.
- ubuntu@alpine01:~$ qemu-system-pp
Public bug reported:
I have installed samba, winbind, libpam-winbind, libnss-winbind,
kerberos, etc. so that I am able to in principle connect to a Windows
Server 2008 R2 active directory controller for AD based logins from
Ubuntu. I am able to use wbinfo -i, wbinfo -u, wbinfo -g to get the list
o
Well this is unnerving. After re-installing the current versions of
qemu-kvm on the source host, it continues to work.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1536331
Title:
Pr
Ok, so reverting the qemu-kvm on the precise source host to 1.0+noroms-
0ubuntu14.18 seems to fix it. (And then using pc-1.0 machine type and
setting allow_incoming_qemukvm = 1 on the destination)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subs
** Summary changed:
- Sync ethtool 1:4.5-1 (main) from Debian testing (main)
+ [FFE] Sync ethtool 1:4.5-1 (main) from Debian testing (main)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ethtool in Ubuntu.
https://bugs.launchpad.net/b
** Changed in: maas (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: maas (Ubuntu)
Status: New => Triaged
** Also affects: maas
Importance: Undecided
Status: New
** No longer affects: maas (Ubuntu)
** Changed in: maas
Importance: Undecided => Wishlist
** Changed
Hello Mathieu, or anyone else affected,
Accepted nova into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nova/2:12.0.2-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
This is the nginx-core installation and apt logs.
** Attachment added: "nginx-core apt logs"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617282/+files/install_logs_nginx-core.txt
--
You received this bug notification because you are a member of Ubuntu
Server Tea
Hello James, or anyone else affected,
Accepted nova into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nova/2:12.0.2-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Upgrading from the 1.9.12 packages to the 1.9.13 packages works without
any issues. There are no failures to update.
Adding install/history logs shortly for each version, and a screenshot
done through nginx-core to show that the defaults work and the
application runs. It also includes a picture
Runtime screenshot - shows the 'default' landing page of nginx-core,
done via VM, and the IP data for the VM, the pidof output to show nginx
is running, and the default landing page via web browser to that VM's IP
address.
** Attachment added: "Screenshot - Xenial VM IP, Xenial pidof output showin
DebDiff between 1.9.12-0ubuntu1 and 1.9.13-0ubuntu1.
** Patch added: "Debdiff, nginx 1.9.12-0ubuntu1 to 1.9.13-0ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617290/+files/nginx_xenial_1.9.12_1.9.13.debdiff
--
You received this bug notification because yo
This needs to be examined for freeze exception. We are past
FinalBetaFreeze, so this needs review before I even upload it to the
repositories.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/
This is the nginx-extras installation and apt logs.
** Attachment added: "nginx-extras apt logs"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617286/+files/install_logs_nginx-extras.txt
--
You received this bug notification because you are a member of Ubuntu
Serv
This is the nginx-light installation and apt logs.
** Attachment added: "nginx-light apt logs"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617283/+files/install_logs_nginx-light.txt
--
You received this bug notification because you are a member of Ubuntu
Server
Public bug reported:
In the near future, we'd expect to have a number of new ARM64 platforms
( Cavium, APM, Qualcomm, Broadcom etc) supported in Ubuntu 16.04 LTS.
Some of these use UEFI + DTB as the default boot mechanism, whereas
others are expected to use UEFI +ACPI as thedefault boot mode.
This is the nginx-full installation and apt logs.
** Attachment added: "nginx-full apt logs"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617284/+files/install_logs_nginx-full.txt
--
You received this bug notification because you are a member of Ubuntu
Server Tea
Blueprint changed by Thomas Ward:
Work items changed:
Work items for ubuntu-15.11:
[serge-hallyn] etckeeper: DONE
[paelzer] NIS merge: DONE
Work items for ubuntu-15.12:
[raharper] : tgt merge (bug 1524982): DONE
[racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
[kic
local-kvm provider is not available in the beta, and is a regression
compared with juju-core 1.25. Is there going to be a local kvm provider?
(or e.g. libvirt provider on par with lxd provider)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscrib
The attachment "x86/mm: Make MM locks recursive." seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned
Public bug reported:
Systemd uses /etc/machine-id file to uniquely identify the machine and
to provide machine ID to D-Bus. This file is generated with `systemd-
machine-id-setup` command that should be run on system installation (or
at least when a system is provisioned). However, cloud-init does
*** This bug is a duplicate of bug 1398001 ***
https://bugs.launchpad.net/bugs/1398001
** This bug has been marked a duplicate of bug 1398001
package clamav 0.98.5+dfsg-0ubuntu0.14.10.1 failed to install/upgrade:
beroendeproblem - lämnar okonfigurerad
--
You received this bug notificatio
Hi rolfc,
thank you for reporting that bug.
It appears on your system some conffiles were deleted.
modified.conffile..etc.apparmor.d.usr.sbin.clamd: [deleted]
modified.conffile..etc.init.d.clamav.daemon: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.clamav.daemon: [deleted]
modi
On Wed, Mar 30, 2016 at 04:41:12AM -, Ryan Harper wrote:
> As far as I can see, the entire versioned code block here is wrong, and
> > you should *only* be restarting squid.
> The block (without my addition) is from debian itself.
Yes, and I believe it's wrong there also (unless their previou
** Also affects: heat (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: heat (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
debian/patches/xsa97-hap-4.1-prereq.patch is the combination of
* commit 301493fb027648db6808b66d1ccf849f524b8422
x86/mm: dedup the various copies of the shadow lock functions
* commit eca988de7381e5efe58792dc166611e4523d33b3
x86/mm: merge the shadow, hap and log-dirty locks into a single p
Hi Jeff,
Thanks for you report - I've seen several such reports popping up around the
same time.
Almost all others had success with purging and reinstalling the clamav packages.
I'd ask you to do the same.
I set the bug to incomplete to ease scanning open bugs, please feel free
to reopen if the
Hi Ken,
this bug report is being closed due to your last comment regarding this being
fixed with an update. For future reference you can manage the status of your
own bugs by clicking on the current status in the yellow line and then choosing
a new status in the revealed drop down box. You can l
It seems that some or all of the package was removed manually.
Therefore the upgrade is failing
>From your logs:
chown: invalid user: ‘clamav:adm’
...
modified.conffile..etc.apparmor.d.usr.sbin.clamd: [deleted]
modified.conffile..etc.init.d.clamav.daemon: [deleted]
modified.conffile..etc.logcheck.
Hello Pavel, or anyone else affected,
Accepted qemu into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-
2ubuntu1.23 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
@taco-screen-team
I'd suggest for @cyphermox (formerly @mathieu-tl) to look at this one.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1561103
Title:
Multipath ass
** Changed in: cloud-images
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1563487
Title:
do not delete /etc/networ
** Changed in: multipath-tools (Ubuntu)
Status: New => Triaged
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.laun
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Confirmed
** Changed in: livecd-rootfs (Ubuntu)
Importance: Undecided => High
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Ol
In Ubuntu 14.04.4 running on the same hardware, the fix was to update
qemu-system-ppc from cloud-archive:kilo. This repository is only
supported on trusty and contains an earlier version of qemu-system-ppc
than what is available on xenial.
** Description changed:
qemu-system-ppc64 running on U
Public bug reported:
qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image
as part of the certification process. This on an IBM ppc64le in PowerVM
mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no
error output.
ubuntu@alpine01:~$ qemu-system-ppc64 -m 256 -dis
** Changed in: tgt (Ubuntu)
Importance: Undecided => Medium
** Changed in: tgt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1555700
Title:
P
Public bug reported:
update bug
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-simplegeneric 0.8.1-1
ProcVersionSignature: Ubuntu 3.16.0-67.87~14.04.1-generic 3.16.7-ckt24
Uname: Linux 3.16.0-67-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Archit
** Changed in: iproute2 (Ubuntu)
Assignee: (unassigned) => Kick In (kick-d)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1522371
Title:
iproute2: seg fault with 'ip link type gr
I have been working on parallel on this one & opened a bug in debian :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819546
listen_ipv6 was reverted from YES to NO following Debian Bug: #803999 to
allign with the manpage statement.
Either we revert it back & adapt the manpage or we force it in
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1563296
The short term fix is to disable cloud-init's networking code by
writing a file /etc/cloud/cloud.cfg.d/99-snappy-disable-network-config.cfg
with:
| network:
|config: "disabled"
The file is yaml text.
This unfortunately, will
Hi. Can you still reproduce this?
I'm not aware of any problems like this with cliff init and maas.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1532072
Title:
cloud-init fails with UnicodeDecodeError
To m
This bug was fixed in the package corosync - 2.3.3-1ubuntu2
---
corosync (2.3.3-1ubuntu2) trusty; urgency=medium
* Patches to solve logsys file leaks (LP: #1530837)
+ /d/p/Fix-compiler-warning-introduced-by-previous-patch.patch
+ /d/p/Handle-SIGSEGV-and-SIGABRT-signals.patch
The verification of the Stable Release Update for corosync 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
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bug
Hmm.
You can disable cloud-init writing network config by putting config in
/etc/cloud/cloud.cfg.d/ that says
network:
config: disabled
However, that will entirely disable cloud init writing networking
information that the data source provided it with.
Currently that is openstack config dr
Patch attached upstream
https://bugzilla.mindrot.org/show_bug.cgi?id=2559 see
https://bugzilla.mindrot.org/attachment.cgi?id=2801
As far as I understand there is no further actions for s390x port.
@OP this is a minor problem, and best addressed upstream, see upstream
bug report linked.
** Bug wa
Sorry, I mean OpenSSH in general of course, not just the client.
And yes, the other end ought to be able to cope with stronger primes.
But that's not what this bug is about: it specifically says "The alleged
problem is the reference to /etc/ssh/primes instead of /etc/ssh/moduli".
--
You received
Sigh. No. It's a perfectly obvious bug in the OpenSSH client, it's
just mostly cosmetic (i.e. it's checking two files but then only warning
about one). Please read the original bug description carefully before
closing this or arguing further about whether it's valid.
** Changed in: openssh (Ubu
1 - 100 of 114 matches
Mail list logo
