** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ A cloud-config that contains packages to install (see below) or
+ 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a
+ result of contention with the apt-daily.service that updates that information.
+
+ Cloud
** Attachment added: "yakkety results"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1693361/+attachment/4905923/+files/1693361-yakkety.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
http
$ for rel in xenial yakkety zesty; do lxc-proposed-snapshot --proposed
$rel proposed-$rel --publish || break; done
$ for rel in xenial yakkety zesty; do lxc launch proposed-$rel "--
config=user.user-data=$(cat config.yaml)" test-$rel || break; done
$ sleep 2m
$ for rel in xenial yakkety zesty; d
** Attachment added: "zesty results"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1693361/+attachment/4905924/+files/1693361-zesty.tar.gz
** Tags removed: verification-needed verification-needed-xenial
verification-needed-yakkety verification-needed-zesty
** Tags added: verificat
** Description changed:
After update [1] of cloud-init in Ubuntu (which landed in xenial-updates
on 2017-06-27), it is causing NTP reload failures.
https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
0ubuntu1~16.04.1
In MAAS scenarios, this is causing the machine t
If you are affected by this bug, then you have the following options:
a.) upgrade to maas 2.2
MAAS 2.2 sends 'apparmor=0' to the installation/commissionging kernel command
line. 2.2 is in -proposed for 16.04, 16.10, 17.04 repositories and
is already available in artful.
Alternatively you can
** Attachment added: "foo.log: /var/log/sysylog and dumpe2fs on system chris
saw this on."
https://bugs.launchpad.net/maas/+bug/1643838/+attachment/4871572/+files/foo.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ur
I've talked about this with Robie Basak before.
For cloud-images building, it seems like it makes sense to clear out apt cache
for updates and security. In the best case scenario, those files are up to
date and apt wont re-download. That lasts only until the next SRU or security
update, so it
Public bug reported:
dash in 14.04 has an odd bug in /bin/sh.
$ var="[abc"
$ echo "${var#[}"
[abc
That *should* output just 'abc' (and does everywhere other than
14.04).
It is fairly easily workaroundable by quoting the '[':
$ var="[abc"
echo ${var#"["}
To demonstrate:
$ lxc
it generally seems to work for just about everything other than '['
# /bin/sh -c 'for i in "$@"; do var="${i}abc";
[ "${var#$i}" = "$var" ] && echo "$i: broken" || echo "$i: ok"; done' \
a b c '[' ']' d e f 1 2 3 '#' - _ = +
b: ok
c: ok
[: broken
]: ok
d: ok
e: ok
f: ok
1: ok
2: ok
3: ok
#:
Public bug reported:
I noticed quite a long time to login to some of my systems via ssh (or scp).
Investigating lead me to find out that the '50-motd-news' file
(/etc/update-motd.d/50-motd-news) was the primary cost.
In line 108 [1] it does something like:
curl --connect-timeout "5" --max-time "
** Merge proposal linked:
https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379177
** Changed in: cloud-utils
Status: New => Fix Committed
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-utils (Ubuntu)
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: New => Confirmed
--
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/1834875
Title:
cloud-init growpart race with u
The fix is in cloud-utils upstream now.
Still to do:
a.) review/merge cloud-initramfs-tools pull request
https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379177
b.) upload cloud-initramfs-tools to focal
c.) upload cloud-utils to focal
d.) any SRU
the order of 'b' a
a.) I gave the wrong link. ugh. It should have been:
https://code.launchpad.net/~smoser/cloud-initramfs-tools/+git/cloud-initramfs-tools/+merge/379774
b.) the fixed link to 'a' probably makes more sense now. But basically
you need a newer cloud-initramfs-tools to adjust for the fact that
growp
this seemed to "just work" for me.
http://paste.ubuntu.com/p/93dWDPZfZT/
--
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/1834875
Title:
cloud-init growpart race with udev
I bumped into this yesterday on bionic.
The commit 1e04bb71da3ed829 [1] reports to fix it.
[1]
https://github.com/lxc/lxc/commit/1e04bb71da3ed829761ae8c729c3d021a6a709df
Hopefully there will be a 3.0.x update to bionic at some point.
** Also affects: lxc (Ubuntu Focal)
Importance: Medium
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
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
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
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
** Also affects: schroot (Ubuntu)
Importance: Undecided
Status: New
** Changed in: schroot (Ubuntu)
Importance: Undecided => High
** Changed in: schroot (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
$ echo "now: $(TZ=GMT date)"; wget -S -q
http://azure.archive.ubuntu.com/ubuntu/dists/vivid/Release -O /dev/null
now: Fri Apr 3 14:37:31 GMT 2015
HTTP/1.1 200 OK
Date: Fri, 03 Apr 2015 14:37:31 GMT
Server: Apache/2.2.22 (Ubuntu)
Last-Modified: Fri, 03 Apr 2015 14:28:00 GMT
ETag: "34f32-
** Also affects: vim (Ubuntu)
Importance: Undecided
Status: New
** Changed in: vim (Ubuntu Vivid)
Status: New => Confirmed
** Changed in: vim (Ubuntu Vivid)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
I ran this on a fresh cloud instance.
$ cat /etc/cloud/build.info
build_name: server
serial: 20150403.2
$ py2pkgs=$(dpkg -l | grep python | grep -v python3 | awk '{print $2}')
$ for p in $py2pkgs; do
out=$(sudo apt-get remove --dry-run $p 2>&1); pkgs=$(echo "$out" | awk '$1 ==
"Remv" && $2 !=
*** 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
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
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
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
host $ rel=vivid serial=20150422
host $
url=http://cloud-images.ubuntu.com/releases/$rel/release-$serial/ubuntu-14.04-server-cloudimg-amd64-disk1.img
host $ img_dist="$rel-$serial-amd64.img.dist"
host $ img=${img_dist%.dist}
## host
host $ pkgs="qemu-utils qemu-system-x86 cloud-image-utils"
host
## host system is vivid, trusty would also do
host $ rel=trusty ; serial=20150417
host $
url=http://cloud-images.ubuntu.com/releases/$rel/release-$serial/ubuntu-14.04-server-cloudimg-amd64-disk1.img
host $ img_dist="$rel-$serial-amd64.img.dist"
host $ img=${img_dist%.dist}
host $ pkgs="qemu-util
landscape-client removed from wily cloud-image seed.
** Changed in: landscape-client (Ubuntu)
Status: Confirmed => Fix Committed
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubu
took an initial stab at vim, and then was pointed at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729924
which is debian bug to get python3 support.
just linking here.
** Bug watch added: Debian Bug tracker #729924
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729924
--
You received
With some other work that I was doing, I found bug 1272414
it seems that getifaddrs() is somewhat slow when lots of interfaces are used.
so this could have a bit of a performance impact in some places. that said,
dhclient is not likely a heavy use path.
--
You received this bug notification b
For anyone else hit by this, the fix still requires you to turn it on.
echo "Set probe_interfaces false" | sudo tee -a /etc/sudo.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.n
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
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:
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
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
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
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
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
** 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
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
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:
** 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
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
** 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
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
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) =
** 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
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
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
-- 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
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
point of reference:
$ sudo apt-get remove python
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
landscape-client landscape-common python python-apt python-characteristic
python-chardet python-configobj pyth
** Changed in: cloud-utils (Ubuntu Vivid)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1427275
Title:
clean cloud images of python2
Public bug reported:
given 3 nics eth0, eth1, eth2
dhclient -1 -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
while that in its early phases, if eth1 is renamed a race condition can
cause dhclient to exit failure.
example, while running attached 'nic-go-crazy' on othe
** Attachment added: "nic-go-crazy: randomly rename nics for dhclient noise"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380696/+files/nic-go-crazy
** Changed in: isc-dhcp (Ubuntu)
Status: New => Confirmed
** Changed in: isc-dhcp (Ubuntu)
Importance:
** Description changed:
given 3 nics eth0, eth1, eth2
dhclient -1 -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
while that in its early phases, if eth1 is renamed a race condition can
cause dhclient to exit failure.
+
+ This can happen in real life when
** Patch added: "patch for trusty"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380752/+files/lp-1446767-trusty.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https
** Patch added: "fix applied to vivid"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380759/+files/lp-1446767-vivid.diff
** Attachment removed: "nic-go-crazy: randomly rename nics for dhclient noise"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/144
** Attachment added: "ifup-loop: loop over ifdown / ifup for a nic to cause
dhclient failure"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380761/+files/ifup-loop
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
** Attachment added: "nic-go-crazy: randomly rename nics for dhclient noise"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380760/+files/nic-go-crazy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
I've also put these attached recreate programs and the original kvm boot
recreate at lp:~smoser/+junk/lp128/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1446767
Titl
The solution here was pulled from
https://bugzilla.redhat.com/show_bug.cgi?id=449946
The patch really just makes linux use getifaddrs rather than reading
/proc/net/dev for information.
The change has been in place in fedora for ~ 3 years, so that should
stand as some testimony.
** Bug watch ad
** Description changed:
+ === Begin SRU Information ===
+ [Impact]
+ Systems that use dhcp for network config combined with network device
re-naming can hit a race condition in dhclient which causes dhcp to fail. Any
network device renaming could cause this, but the most likely scenario is boo
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
I subscribed ubuntu-server to bug mail.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to liburcu in Ubuntu.
https://bugs.launchpad.net/bugs/1644757
Title:
[MIR] liburcu
Status in liburcu package in Ubuntu:
New
Bug descri
I can verify that in a lxc container of zesty i installed ppa above (yakkety)
and dist-upgraded.
rebooted and no dev-sda2 job.
--
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
tu Xenial)
Status: New => In Progress
** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
Assignee: (unassigned) => Scott Moser (smoser)
** No longer affects: initramfs-tools (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Hi,
I've reviewed the changes that Mathieu has suggested at
https://launchpadlibrarian.net/295312215/isc-dhcp_4.3.3-5ubuntu15.2~mtrudel4_4.3.3-5ubuntu15.2~mtrudel5.diff.gz
.
I'm fine to let what he has go in there. I suggest, however, that we
drop the exposing of dhclient variables to the /run/
** Description changed:
- Drop: Maintain compatibility with pre- /run configurations -- this was
- for compatibility with oneiric which is now long gone.
+ === Begin SRU Template ===
+ [Impact]
+ overlayfs writes some log information to the tmpfs that was intended
+ to be then viewable after the
I've verified this using the steps described in the SRU template
$ dpkg-query --show overlayroot
overlayroot 0.27ubuntu1.3
** Description changed:
=== Begin SRU Template ===
- [Impact]
+ [Impact]
overlayfs writes some log information to the tmpfs that was intended
to be then viewable
I've verified that networking.service does not take down 'lo' interface
with the proposed version in yakkety (0.8.13ubuntu3).
Below, first I show the problem in 0.8.13ubuntu2 and then install
the proposed version and show it fixed.
$ lxc launch ubuntu-daily:yakkety y1
$ sleep 10
$ lxc exec y1 /
** Changed in: ifupdown (Ubuntu Xenial)
Status: Confirmed => In Progress
--
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/1629972
Title:
networking stop incorrectly
I've adjusted the description, including SRU template of this bug to
better fit what we found out and the solution that was applied.
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ The systemd networking.service unit will bring down the loopback device (lo)
+ when it is stopped.
Public bug reported:
When testing bug 1639930 I found that booting a system with:
ip6=dhcp
will enable ip=dhcp. ip= does not enable ip6=dhcp, so this is odd behavior.
Thus, if you had an ip6 only network, in order to do this you have to do:
ip6=dhcp ip=off
This is really just a matter of a v
I've removed the verification-needed tag that seemed to have been blocking this
into precise-updates.
My comment in 13 stands, as I verified on precise at that time, and added the
verification-done-precise tag.
** Tags removed: verification-needed
** Tags added: verification-done
--
You recei
Robie,
wrt git noise on precise, I'm not fussed either way. I can re-upload if you'd
like.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1633479
Title:
dhclient does n
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1629797
Title:
resol
This is fixed in cloud-init 0.7.9.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1629797
Title:
resolve service in nsswitch.conf adds 25 seconds to failed lookups
before s
** Also affects: cloud-init
Importance: Undecided
Status: New
--
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/1636912
Title:
systemd-networkd runs too late for cl
aniel-thewatkins) => Scott Moser (smoser)
--
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/1629797
Title:
resolve service in nsswitch.conf adds 25 seconds to failed looku
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1629797
Title:
resolve service in nsswitch.conf a
Public bug reported:
/sbin/dhclient-script does not seem to pay any attention to the prefixlen that
is provided.
The result is that:
$ dhclient -6 -1 -v eth0
results in network configuration like this:
2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 52:54:00:12:34:56 brd ff:ff:ff:f
I put a branch at https://code.launchpad.net/~smoser/ubuntu/+source
/initramfs-tools/+git/initramfs-tools/+ref/lp-1631010 with a fix for
this.
other improvements too:
improvements to dhclient handing of ip= command lines.
Improvemnts here are:
a.) do not leave /run/net-* around i
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git
/initramfs-tools/+ref/lp-1631010
there i added 'ip6=only' and 'ip6=only-S' (we can change the syntax),
but '-S' means to pass '-S' to 'dhclient -6'.
--
You received this bug notification because you are a member of Ubuntu
Tou
lscotte, did you open a bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1628306
Title:
network booting fails for iscsi root if no ip is set
Status in initramf
(found bug 1631474)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1628306
Title:
network booting fails for iscsi root if no ip is set
Status in initramfs-tools p
** Changed in: ifupdown (Ubuntu)
Status: New => Confirmed
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => High
** Changed in: ifupdown (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: ifupdown (Ubuntu Xenial)
Importance: Undecided => High
--
You received th
I have a branch of ifupdown at
https://code.launchpad.net/~smoser/ubuntu/+source/ifupdown/+git/ifupdown/+ref/lp-1629972
and just uploaded to https://launchpad.net/~smoser/+archive/ubuntu/ppa
It seems to work for me.
Please test.
--
You received this bug notification because you are a member of
I've subscribed pitti, in an effort to a.) have him review my changes
b.) ask if there is any other way to do this. i've verified in ifupdown
source that 'ifdown -a' will ultimately get '/bin/ip link set dev eth0
down' called.
--
You received this bug notification because you are a member of Ubu
Hi,
I think the right way to fix this regression would have been to revert the
change.
The change made in bug 1628306 made fairly wide spread changes. It caused this
regression as seen, but also added behavioral changes.
Previously, 'ip=dhcp' would do a ipv4 dhcp request (via ipconfig).
The cha
** Description changed:
[Impact]
Remote-root installs (eg. / over iscsi and similar) where the configuration
is simple, and no extra parameters are included on the kernel command-line (as
opposed to MaaS specifying everything).
[Test case]
1) do an installation with /boot on a local d
285:69dd:7210:c0a5: icmp_seq=3 ttl=64
time=0.069 ms
...
$ lxc exec y1 -- ip link set down dev lo
immediately ping6 starts dropping packets in window1.
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: ifupdown (Ubuntu Xenial)
Assi
" - Alpha amd64 (20150722.1)
SourcePackage: isc-dhcp
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: isc-dhcp (Ubuntu)
Importance: Medium
Assignee: Scott Moser (smoser)
Status: Fix Committed
** Tags: amd64 apport-bug yakkety
** Changed in: isc-dhcp (U
** Changed in: isc-dhcp (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1633479
Title:
dhclient does not wait for ipv6 d
** Description changed:
dhclient -6 does not wait for an interface go through duplicate address
detection.
As a result the following will almost always fail:
- $ dev=eth0
- $ ip link set down dev $dev
- $ dhclient -6 -1 -v eth0
- Internet Systems Consortium DHCP Client 4.3.3
- Copyrig
301 - 400 of 562 matches
Mail list logo
