Just realized, that ideally 'apt-get update' would respect headers that were
put in place by the source.
$ wget -S -q http://azure.archive.ubuntu.com/ubuntu/dists/vivid/Release -O
/dev/null
HTTP/1.1 200 OK
Date: Tue, 31 Mar 2015 13:32:55 GMT
Server: Apache/2.2.22 (Ubuntu)
Last-Modified: T
I've recreated this in a cloud image.
See the steps to do so here in this attachment.
** Attachment added: "description of how to recreate in cloud image"
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1427264/+attachment/4353785/+files/notes.txt
--
You received this bug notification
Hi,
I dont actually know why 219-4ubuntu7 would fix the problem.
I think it probably just change timing of a very small race window.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad
-- adt --
Note, my adt runs so far have failed each time (and after 30+ minutes)
The last last failure due to guest running out of space, so changed to 20G
(default 4)
# per http://packaging.ubuntu.com/html/auto-pkg-test.html#executing-the-test
sudo addgroup kvm
sudo adduser $(id --use
just copying description from my duplicate bug as i think its probably /
possibly useful
As seen in the failed systemd adt test at [1], installing 'upstart-bin'
and then booting a system with 'init=/sbin/upstart' does not result in a
fully functional system. The problem is that there are many upst
Public bug reported:
As seen in the failed systemd adt test at [1], installing 'upstart-bin'
and then booting a system with 'init=/sbin/upstart' does not result in a
fully functional system. The problem is that there are many upstart
jobs provided by 'upstart' package that are essential to Ubuntu
** Patch added: "proposed fix"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432829/+attachment/4349395/+files/lp-1432829.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launc
I've made this affect systemd as that is where I have the fix for it.
I could fix in open-iscsi as it was in upstart, but I think adding general
infrastructure that considers open-iscsi is more sane than open-iscsi playing
around with tricking ifupdown.
** Package changed: resolvconf (Ubuntu) =
Tomorrow I'll look into adding code in systemd package that would
basically do what the open-iscsi job did previously.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/14328
** Patch added: "suggested fix."
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432821/+attachment/4348329/+files/bug-1432821.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.la
So, thanks to xnox.
/lib/systemd/system/ifup@.service
has 'RuntimeDirectory=network'
So that is what is killing /run/network .
He suggested we should remove this from ifup@.service and ship a file in
/usr/lib/tmpfiles.d that does:
d /run/network 0755 root root -
--
You received this bug noti
** Summary changed:
- something deleting /run/network after during boot
+ something deleting /run/network after initramfs
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1432
possibly related...
likely related, I find that on this system
$ ls /run/network/ifstate
ls: cannot access /run/network/ifstate: No such file or directory
$ ifquery --state --all
Segmentation fault (core dumped)
$ sudo ifquery --state --all
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 52:
Thomas,
Yeah, you're right about 'manual '. Seems unnecessary.
wrt you not reproducing it, I'm seeing the issue
a.) when using systemd as init
b.) when configuring networking from the initramfs
the interface being used is already up, and in this case cant be bounced
when init runs from the roo
** Changed in: ubuntu
Status: New => Confirmed
** Changed in: ubuntu
Importance: Undecided => High
** Package changed: ubuntu => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
h
Public bug reported:
maas images utilize cloud-initramfs-dyn-netconf . The way this works is
basically:
* /etc/network/interfaces in image is a link to
../../run/network/dynamic-interfaces
* kernel command line 'ip=' convince the initramfs to bring up networking
using 'ipconfig'
example: i
I opened bug 1430011 as a request for launchpad to gain the ability to
create /populate by-hash mirrors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/972077
Title:
apt repos
relevant changelog in debian:
* Implement simple by-hash for apt update to improve reliability of
the update. Apt will try to fetch the Packages file via
/by-hash/$hash_type/$hash_value if the repo supports that.
- add APT::Acquire::$(host)::By-Hash=1 knob
- add Acquire-By-Ha
Per mvo, there is apparently by-hash support in debian experimental with some
references seen at
https://github.com/Debian/apt/blob/debian/experimental/apt-pkg/acquire-item.cc#L1222
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Public bug reported:
In many cases (juju, lxc containers .. ) we find ourselves in the
position of not knowing if the apt-cache has been udpated recently. So,
you either risk not doing it, or do it and it takes some time and
generates load.
so long story short, you always run 'apt-get update' wh
this particular system (in azure) has io that rivals that of floppy disks, so
the times are more dramatic.
you're correct in that the information is cached, and that is in general a good
thing, but if I ssh to a system only once a day, then every time i do it, i hit
this penalty.
thats in addit
Public bug reported:
If i launch a new cloud instance, and then ssh to it, my ssh login
blocks, stopping me from doing useful work while '/usr/lib/update-
notifier/apt-check' runs.
By far, the biggest offender of this slow login is
/usr/lib/update-notifier/apt-check.
To demonstrate, a fresh clou
Ted, thanks for your response, and sorry for the spam.
Can you just verify that this specific bit seems correct:
| On that derived image, I see 'resize2fs -P' numbers like:
| trusty: 274500
| utopic: 358400
| vivid: 358400
| The 83900 blocks out of a 358400 seems significant (23% of the f
To rule out kernel involvement, I took the same 'root-image' and ran
this on utopic:
# these downloaded trusty versions
[https://launchpad.net/ubuntu/+source/e2fsprogs]
$ sudo dpkg -i e2fslibs_1.42.9-3ubuntu1_amd64.deb
$ sudo dpkg -i e2fsprogs_1.42.9-3ubuntu1_amd64.deb
$ resize2fs -P /tmp/root-i
Public bug reported:
I have a disk image created as part of lp:maas-images.
This process takes a cloud image (http://cloud-images.ubuntu.com) such as
http://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64.tar.gz
.
Inside that .tar.gz is a .img file. The .img file is operated
*** This bug is a duplicate of bug 1379427 ***
https://bugs.launchpad.net/bugs/1379427
** This bug has been marked a duplicate of bug 1379427
/etc/network/if-up.d/upstart emits static-network-up to early
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I've verified this change fixes the issue with initramfs mounting iscsi targets
. I did this inside of maas.
* basically set up functional maas with some nodes, and daily images of utopic
imported.
from there
### repro
# get some tools
$ apt-get install cloud-image-utils --no-install-recommen
** Description changed:
With trusty, /bin/ping relies on having extended attributes and kernel
capabilities to gain the cap_net_raw+p capability. This allows removing
the suid bit.
However, the tarball cloud images do not preserve the extended
attributes, and thus /bin/ping does not w
Just to demonstrate a particularly odd behavior:
#!/bin/bash
set -e; set -o pipefail
tmpd=$(mktemp -d)
trap "rm -Rf "$tmpd"" EXIT
cd $tmpd; mkdir defaults ex
setfacl --default --modify u::rwx --modify g::r-x --modify other::r-x defaults
setfacl --remove-default ex
xattr_args="--xattrs --xattrs-in
heres output of a run of 'tmp-acl-bavior':
** Attachment added: "example output of running"
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1386237/+attachment/4246269/+files/out
** Description changed:
as discovered in bug 1382632 (http://launchpad.net/bugs/1382632), tar's --acl
has
** Description changed:
With trusty, /bin/ping relies on having extended attributes and kernel
capabilities to gain the cap_net_raw+p capability. This allows removing
the suid bit.
However, the tarball cloud images do not preserve the extended
attributes, and thus /bin/ping does not w
Public bug reported:
as discovered in bug 1382632 (http://launchpad.net/bugs/1382632), tar's --acl
has unexpected behaviors.
The one that caught us there was that extracting a tar file with '--acl' that
was created without '--acl' results in default acl being set on the top level
extracted dire
** Changed in: curtin (Ubuntu Saucy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1313550
Title:
ping does not work as a normal use
I've verified fix-released on utopic. In 2 ways:
a.) set /etc/network/interfaces with:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet6 static
netmask 64
address 2001:db8::1:3
And set a local 'NoCloud' datasource, and then booted
the system to see 'ip -6 addr' shows t
** Also affects: ifupdown (Ubuntu Utopic)
Importance: Medium
Status: Confirmed
** Also affects: ifupdown (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: ifupdown (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: ifupdown (Ubuntu Trusty)
Import
ok. so some updates.
Ben fixed this in the cloud image build process via [1] (commit [2]), and
limited the change to utopic+.
The fix was done by adding a file /etc/sysctl.d/99-cloudimg-ipv6.conf
The problem with this change is described in bug 1352255 and bug
994931. If ipv6 addresses are alr
just for the record changing
sysctl -e net.ipv6.conf.all.use_tempaddr
is what causes the problem. changing 'sysctl -e
net.ipv6.conf.default.use_tempaddr' does not.
changing 0 -> 2 or 2 -> 0 deletes all existing addresses for an interface.
** Changed in: ifupdown (Ubuntu)
Importance: Undeci
i opened bug 1379427 for the incorrect static-networking bug that i
found when investigating.
setting the use_tempaddr setting ends up wiping existing ipv6 addresses.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown i
interestingly enough, modifying the privacy settings via sysctl has some
negative affects if addresses are already up. see diagnosis in bug
1377005 .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bu
Public bug reported:
I came across this when debugging bug 1352255.
as implemented right now (trusty and utopic) the 'static-network-up' event is
emitted when each 'auto' interface has had *an* address configured, as opposed
to *all* addresses configured.
Heres why:
ifupdown calls runparts on
I did a fair amount of debug information including recreation with a
cloud image at lp:~smoser/+junk/lp-1377005 . I'll copy the final comment
here.
ok. so, i now know what happens, and why adding anything before the ipv6
address "fixes" the problem.
boot happens like this:
* system boot
* net-d
The simple fix, then is:
rm /etc/sysctl.d/10-ipv6-privacy.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1352255
Title:
Impossible to configure network interface w
Public bug reported:
When booting the system image, nothing generates ssh host keys.
Normally I think these are created on installation, but for good reason they're
not included in the image.
In cloud imags, cloud-init does this. In other systemd boot scenarios, they're
generated by another ss
Public bug reported:
I'm downloading an image, and booting it in kvm via
lp:~ubuntu-foundations-team/create-ubuntu-core-image .
The result is a image that requires graphics to log into. Ie, I'd much rather
use either '-nographic' or '-curses' flags to kvm.
This is much easier to work with remot
marked this 'triaged' in cloud-init while still not really relevant.
Ben Howard has disabled the privacy extensions in cloud images in 14.10, and
the plan is to just do the same for 14.04.
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Imp
** No longer affects: cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1347020
Title:
trusty host - utopic lxc container cloudimage boot with systemd does
Well, this was opened as a trusty issue, and in my memory it was only on
trusty, but here is an attempt that fails on trusty or utopic host. I
know that when we did this, there was no systemd-sysv package, so my
attempt was more to invoke /lib/systemd/systemd as the init comand.
$ sudo apt-get up
** Changed in: gnupg (Ubuntu)
Status: New => Confirmed
** Changed in: gnupg (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: util-linux (Ubuntu)
Status: New => Confirmed
** Changed in: util-linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification
Chris seems to have correctly identified the issue.
I tried reverting the xserver-xorg-video-intel to previous versions, but it had
no affect.
I rebooted into an older kernel and i can still use compiz/unity.
3.16.0-6-generic : works
3.16.0-7-generic : fails
3.16.0-8-generic: fails
** Summar
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1355196
Title:
unity crashes on login, compiz cpu
** Attachment added: "guest's home dir during failed login (log files in
.cache)"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1355196/+attachment/4176600/+files/guest-home.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "/var/log/Xorg.0.log from guest login"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1355196/+attachment/4176602/+files/guest-Xorg.0.log
** Changed in: unity (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a me
** Attachment added: "/var/log/kern.log messages from guest login"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1355196/+attachment/4176601/+files/guest-kern.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unit
$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset
OpenGL version string: 2.1 Mesa 10.2.5
Not software rendered:yes
Not blacklisted: yes
GLX fbconfig: yes
GL
This reproduces in the guest login also.
** Changed in: unity (Ubuntu)
Status: New => Confirmed
** Changed in: unity (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in
For what its worth, this is an older thinkpad (T400). It has older
intel graphics chipset. I'm attaching xorg.0.log for more information.
** Attachment added: "xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1355196/+attachment/4174472/+files/Xorg.0.log
--
You received th
Public bug reported:
Recent upgrade and reboot/re-login left me with a generally unusable
compiz/unity.
On login, the desktop icons move back and forth several times, I believe this
correlates with ~/.xesssion-errors 'unity main process ended' messages like:
upstart: gnome-keyring main process
Forwarded upstream https://bugs.g10code.com/gnupg/issue1675 .
** Bug watch added: GnuPG Bugs #1675
https://bugs.g10code.com/gnupg/issue1675
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.laun
updated race-verify a bit. no functional change.
** Attachment added: "script that shows the issue"
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1342807/+attachment/4154169/+files/race-verify
** Attachment removed: "script that shows the issue"
https://bugs.launchpad.net/ubuntu/+s
** Attachment added: "script that shows the issue"
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1342807/+attachment/4154140/+files/race-verify
** Description changed:
There is a race condition with gnupg --verify when multiple processes
act at the same time.
strace helps cause t
Public bug reported:
There is a race condition with gnupg --verify when multiple processes
act at the same time.
strace helps cause the race condition (probably by slowing thing down)
gpgv does not seem to have the issue.
The result is you will see transient verify failures with output like below
501 - 562 of 562 matches
Mail list logo
