** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: cloud-initramfs-tools (Ubuntu Bionic)
Status: Confirmed => In
** Changed in: cloud-initramfs-tools (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: cloud-initramfs-tools (Ubuntu Cosmic)
Status: New => Confirmed
** Changed in: cloud-initramfs-tools (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: cloud-initramfs-tools
Hi,
The current state of this bug:
a.) 0.1.0~bzr426-0ubuntu1.3 was uploaded. It contained a fix for
bug 1686437. That change contained a regression (bug 1728982, bug 1719879),
so the bug was marked xenial-verification-failed.
b.) We have subsequently done work to fix that regression
A merge
Just for later reference, similar bug 1792905.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543204
Title:
cloud images should have /lib/modules inside
To manage notifications about this bug go
Hi,
Can you please add a gating check on image publication that /lib/modules
directory exists?
** Changed in: open-iscsi (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: open-iscsi (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: open-iscsi (Ubuntu Bionic)
I put a pull request to upstream open-iscsi to improve its failure path
here : https://github.com/open-iscsi/open-iscsi/pull/127
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792905
Title:
[2.5]
Urgency is critical.
Customer deployments that use modules will be broken. This would include vfat,
zfs... many things.
I believe this is the root cause of Christian's maas deployment with console
log at
http://paste.ubuntu.com/p/BMS4dbW4XD/
** Changed in: cloud-images
Importance: High
just for reference, here is iscsid status when it fails.
the error is 'can not create NETLINK_ISCSI socket'.
I'm confused as to why, but it will start later in boot fine.
$ systemctl status iscsid.service --no-pager --full
● iscsid.service - iSCSI initiator daemon (iscsid)
Loaded: loaded
I want to be clear and state that there will be other fallout from not
having any modules in the ephemeral environment. Just fixing open-iscsi
to not run or not fail doesn't solve the problem.
Also note that if you boot the ephemeral environment without 'ro' on the
command line, then this
See bug 1543204 for more information.
The change that caused this regression was in ubuntu released bionic images.
Between 20180831 and 20180911 the /lib/modules directory disappeared.
That means that 'copymods' cannot copy modules from initramfs into the
root filesystem, and without that,
** Changed in: cloud-init
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787459
Title:
datasource.sys_cfg gets different values in local st
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784713
Title:
cloud-init profile.d files use bash-specific builtin "local"
** Changed in: cloud-init (Ubuntu Bionic)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766401
Title:
full config file wiped after apt-upgrade issued
To
** Changed in: maas (Ubuntu Bionic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1134036
Title:
Failure when using ssh with a locale that is not configured on the
** Changed in: cloud-init (Ubuntu Bionic)
Importance: Undecided => Low
** Changed in: cloud-init (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Alex,
sorry for the slow reply.
Servicing 14.04 could still be done, but doing so would really require
some effort on the person wanting bug fixes in.
I had intended in comment 19 to point at my branch
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Committed
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Seth,
I'm confused by:
"I'm not currently aware of any working kernel version."
Ubuntu 18.04 kernels (4.15) work correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790652
Title:
Oracle
For the lazy
commit 707e7e96602675beb5e09bb994195663da6eb56d ->
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=707e7e96602675beb5e09bb994195663da6eb56d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just successfully used this on my 'bastion'
python3-openstackclient 3.14.0-0ubuntu1
But it seems to fail from my cosmic desktop 3.16.0-0ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
$ openstack volume create --debug --size=1 smvol1
...
Instantiating image api:
create() got an unexpected keyword argument 'source_replica'
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cliff/app.py", line 402, in
run_subcommand
result =
Below is cloud-init log entries around the warning.
Here are the contents of the lease file that dhclient wrote:
# cat /run/dhclient-lease-file
lease {
interface "ens3";
fixed-address 54.36.113.86;
option subnet-mask 255.255.255.255;
option routers 54.36.112.1;
option dhcp-lease-time
Public bug reported:
Part of "make OVH work right" was brought up by Tobias in
https://code.launchpad.net/~tobijk/cloud-init/+git/cloud-init/+merge/354752
After that, though we still see some warnings in the logs that is
attached.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package:
@xnox,
Are you suggesting the /media/root-ro entry in /etc/fstab line for
/media/root-ro should have x-systemd.DefaultDependencies=no ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788188
Title:
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792157
Title:
This is invalid.
It actually all still works because:
udev hook /lib/udev/rules.d/80-ifupdown.rules calls /lib/udev/ifupdown-hotplug
which calls
systemctl --no-block start $(systemd-escape --template ifup@.service
$INTERFACE)
Then the ifup@.service is what actually brings up the device.
Public bug reported:
I haven't verified this, but I believe that ifupdown works through udevadm
hooks.
So udevadm hotplug event -> ifup eth0.
Any subprocesses of a udevadm hook will be restricted by the
systemd-udevd.service
restrictions, which currently are
RestrictAddressFamilies=AF_UNIX
Public bug reported:
Line like this in the log shows the issue:
2018-09-12 10:36:25,462 - openstack.py[DEBUG]: Selected version 'latest' from
[b'2012-08-10', b'2013-04-04', b'2013-10-17', b'2015-10-15', b'2016-06-30',
b'2016-10-06', b'latest']
we're looking for a string in a list of bytes.
Shane,
Could you pleaes fill in a Stable Release Updates template on this bug?
https://wiki.ubuntu.com/StableReleaseUpdates
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781039
Title:
This is reported fixed under bug 1786438 in snapd 2.35.2+18.10 which is
currently in cosmic-proposed.
snapd (2.35.2+18.10) cosmic; urgency=medium
* New upstream release, LP: #1786438
- cmd,overlord/snapstate: go 1.11 format fixes
- ifacestate: fix hang when retrying content providers
Summary: environment-generators inherit environment that /sbin/init
started with, but no other systemd defaults. Therefore, there is no
easy way to append to an environment variable that is not set as snapd
was hoping to do. The only solution currently is to copy the expected
"default path" into
** Attachment added: "Example python generator for debugging."
https://bugs.launchpad.net/cloud-images/+bug/1791691/+attachment/5187696/+files/mytest-env-generator.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://github.com/snapcore/snapd/pull/5808
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791691
Title:
PATH broken in systemd units
To manage notifications about this bug go to:
uploaded. 0.7.5-0ubuntu1.23
Currently in the SRU queue.
Thanks Shane.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781039
Title:
GCE cloudinit and ubuntu keys from metadata to ubuntu
I prepared merge proposals for both xenial and bionic.
Also:
- tested autopkgtest on both xenial and bionic
- uploaded to [my ppa](https://launchpad.net/~smoser/+archive/ubuntu/ppa) for
xenial and bionic
- uploaded bionic to SRU queue
--
You received this bug notification because you are a
** Merge proposal linked:
https://code.launchpad.net/~smoser/ubuntu/+source/open-iscsi/+git/open-iscsi/+merge/354478
** Merge proposal linked:
https://code.launchpad.net/~smoser/ubuntu/+source/open-iscsi/+git/open-iscsi/+merge/354483
--
You received this bug notification because you are
@Mark,
We did not intend to break your use case on 16.04.
Upstream has required strict identification of the platform for some time.
(bug 1669875 was filed ~ 18 months ago).
We do intend to support "explicit" datasource configuration via
setting datasource_list to have 1 entry (or 2 entries if
I uploaded open-iscsi_2.0.874-5ubuntu8 which has the debug code
that we were toying with included. It also includes a fix for
FTBFS bug 1791154.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788188
This was actually fixed in cloud-utils - 0.30-0ubuntu6, but a slew of my
errors meant it didnt leave -proposed until 0ubuntu9.
cloud-utils (0.30-0ubuntu6) cosmic; urgency=medium
* sync to trunk at 333:
- growpart: fix bug when resizing a middle partition with sgdisk.
** Bug watch added: Debian Bug tracker #908160
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908160
** Also affects: open-iscsi (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908160
Importance: Unknown
Status: Unknown
--
You received this bug notification
After some code motion the this was fixed upstream at
https://github.com/open-iscsi/open-iscsi/commit/6d68ef5871c94c6ebbbe6e6b1fe0bc2dce711052
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791154
** Changed in: open-iscsi (Ubuntu)
Status: New => In Progress
** Changed in: open-iscsi (Ubuntu)
Importance: Undecided => Critical
** Changed in: open-iscsi (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are
Public bug reported:
Current build of open-iscsi (2.0.874-5ubuntu7) will fail to build from
source.
Seems to be related to the issue listed here:
https://github.com/hishamhm/htop/issues/663
and fix
https://github.com/hishamhm/htop/commit/c01f40eb3e599f55d408448228d95ecee4b2031f
It ends in:
** Changed in: cloud-utils
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706751
Title:
GPT disk growroot fails in version .027 cloud-utills
To manage
** Changed in: cloud-utils
Status: New => Confirmed
** Changed in: cloud-utils
Importance: Undecided => Medium
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-utils (Ubuntu)
Status: New => Confirmed
** Changed in:
Nominated this for xenial based on bug 1651497.
** Also affects: open-iscsi (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755858
Title:
I've hit that 'retrigger' button 2 more times and have not seen failures.
I just did again. Don't know what to do. :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788188
Title:
transient systemd
If we were to change the behavior of open-iscsi to be socket activated,
then that should happen under bug 1755858.
** Description changed:
I am getting a transient error installing open-iscsi in a xenial lxd
container. Sometimes it works fine, but occasionally, it fails like
this
2016-12-20 12:33:55 INFO install Job for iscsid.service failed because a
configured resource limit was exceeded. See "systemctl status
^ if that is the source of the issue, then this is "working as
designed". If the container had some memory or other constraints and
open-iscsi failed to restart
I cannot seem to re-create this, so I'm not really interested in SRU'ing
a fix that we think might solve the problem without the ability to
verify that.
Here is what I'm doing to attempt to recreate
http://paste.ubuntu.com/p/STVg62nGPb/
I'm through 432 containers 10 at a time right now on my
** Merge proposal linked:
https://code.launchpad.net/~shaner/cloud-init/+git/cloud-init/+merge/353997
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781039
Title:
GCE cloudinit and ubuntu keys
Sorry for late triage... if this is still an issue, please re-open and
run 'cloud-init collect-logs' on the image.
Thanks.
Scott
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Cosmic)
Importance: Medium
Assignee: Pengpeng Sun
*** This bug is a duplicate of bug 1766538 ***
https://bugs.launchpad.net/bugs/1766538
@Pengpeng,
The next time we do a Stable Release Update (SRU) [1], it will include
the fix you've pointed at. Those happen every 1 or 2 months to the
currently supported Ubuntu releases of 16.04 and newer.
@Deepa,
Please file a new bug.
If possible, get
a.) a serial console log of the boot of the system
b.) ssh into the commissioning mode and run 'cloud-init collect-logs'.
thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg, lspci -vvn from a bionic instance of same type
(vmstandard 2.1)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790652/+attachment/5184530/+files/vmstandard-2.1-bionic.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I updated the description to clarify. This issue only occurs on
VMStandard2.1 size. The image I uploaded works for VMStandard1.1 (which
gets a different NIC).
** Summary changed:
- Oracle cosmic image does not find broadcom network device in initramfs
+ Oracle cosmic image does not find
I built and uploaded an image with cosmic-proposed enabled to get the
4.18.0-7-generic kernel.
Note that I'm fairly sure I also got linux-firmware at 1.175 (cosmic-proposed
version). But if that didn't make it into the initramfs (I'm assuming that
some linux-firmware files must make it into
Public bug reported:
I tried to register and boot a cosmic image to verify new changes in it and in
cloud-init.
The image failed to bring up networking in the initramfs, and thus failed to
find iscsi root.
this could be user error.
Here is what I did to publish the image.
- use oci build
** Attachment added: "grep . -r /sys/devices/pci output from initramfs"
https://bugs.launchpad.net/ubuntu/+bug/1790652/+attachment/5184524/+files/grep-r-sys-devices-pci.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Jason,
I'm guessing that you ran some script to collect the logs that you collected
(open-iscsi-errors.tar.gz). There is a lot of good information there, thank
you.
Please add collection of /etc/cloud/build.info to the script that
collects.
--
You received this bug notification because you
I had hoped to reproduce this so that I could be sure that I actually fixed it.
What I did to attempt that was
- download the 20180816 xenial daily build that had
2.0.873+git0.3b4b4500-14ubuntu3.4.
- add to lxc
lxc image import xenial-server-cloudimg-amd64-lxd.tar.xz
@Mark,
We believe the decision to limit cloud-init's "poll"ing of network based
metadata services is the right decision. That means that cloud-init will
only reach out to a metadata service if:
a.) it has positive identification that the metadata service will exist.
b.) it has been
You should be able to specifically set the datasource in
/etc/cloud/cloud.cfg.d/*.cfg
with:
datasource_list: ['OpenStack', 'None']
I know this is not ideal, but in lieu of some mechanism for detecting
that this platform provides an openstack metadata service on
http://169.254.169.254/openstack
There are two paths we could pursue for this:
a.) Utilize reporting mechanism (reporting.handlers.ReportHandler), which
already does this in many senses. MAAS uses this mechanism to accomplish both
"status" events and "pass/fail". This general mechanism is already in place.
To use it for
here is a pastebin of boot with systemd debugging.
http://paste.ubuntu.com/p/vGTRh6WB3B/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788188
Title:
transient systemd ordering cycle in boot with
I pushed a branch up to
https://code.launchpad.net/~smoser/ubuntu/+source/open-iscsi/+git/open-iscsi/+ref/bug/1788188-debug
that Christian and I are trying to get some additional debug information out of
a failure.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
open-iscsi test utilizes overlayroot to boot a cloud-image with root
filesystem on a read-only iscsi server.
The /etc/fstab file in the image looks like this:
LABEL=cloudimg-rootfs /ext4 defaults0 0
#LABEL=UEFI /boot/efi vfatdefaults
** Description changed:
Begin SRU Template
[Impact]
Overlayfs allows a user to mount the root filesystem read-only
and put an overlay over it.
It handles mounting of the root filesystem in the initramfs, and updates
/etc/fstab to account for non-root filesystems and
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766538
Title:
Public bug reported:
# fresh bionic container, as root.
$ apt-get update && apt-get install git-build-recipe bzr-builder
$ bzr branch lp:simplestreams trunk.dist
# 460 is the last functional bzr version
$ bzr branch -r 460 trunk.dist upstream-bzr
$ bzr branch
I did request the pdftk namespace, so now you do not need pdftk-smoser,
but just:
snap install pdftk
Feel free to file issues at
https://github.com/smoser/pdftk/tree/snap/snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When a datasource is instantiated it is passed in Init.cfg as the 'sys_cfg'.
But then when 'distro' property is referenced, it has the side effect
of:
system_config = self._extract_cfg('system')
if self.datasource is not NULL_DATA_SOURCE:
** Merge proposal linked:
https://code.launchpad.net/~shaner/cloud-init/+git/cloud-init/+merge/352572
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781039
Title:
GCE cloudinit and ubuntu keys
autopackage test log for bionic
** Attachment added: "autopkgtest-2.0.874-5ubuntu2.1.log.gz"
https://bugs.launchpad.net/bugs/1785108/+attachment/5174770/+files/autopkgtest-2.0.874-5ubuntu2.1.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You can see lines in each of the attachments like:
[ 315.668747] cloud-init[1584]: Adding mytap0 ^M
[ 316.726647] cloud-init[1584]: Removing mytap0 ^M
That adds the interface and removes it (and udevadm settles), which
would have triggered the bug.
--
You received this bug
autopackage test log for cosmic
** Attachment added: "autopkgtest-2.0.874-5ubuntu7.log.gz"
https://bugs.launchpad.net/bugs/1785108/+attachment/5174769/+files/autopkgtest-2.0.874-5ubuntu7.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
autopackage test log for xenial
** Attachment added: "autopkgtest-2.0.873+git0.3b4b4500-14ubuntu3.5.log.gz"
https://bugs.launchpad.net/bugs/1785108/+attachment/5174768/+files/autopkgtest-2.0.873+git0.3b4b4500-14ubuntu3.5.log.gz
--
You received this bug notification because you are a member
(sorry for attachment noise had wrong bug number while working on a 'lp-
attach-file' https://github.com/CanonicalLtd/uss-
tableflip/blob/master/scripts/lp-attach-file).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
autopackage test log for bionic
** Attachment added: "autopkgtest-2.0.874-5ubuntu2.1.log.gz"
https://bugs.launchpad.net/bugs/1783129/+attachment/5174767/+files/autopkgtest-2.0.874-5ubuntu2.1.log.gz
** Attachment removed: "autopkgtest-2.0.873+git0.3b4b4500-14ubuntu3.5.log.gz"
autopackage test log for cosmic
** Attachment added: "autopkgtest-2.0.874-5ubuntu7.log.gz"
https://bugs.launchpad.net/bugs/1783129/+attachment/5174766/+files/autopkgtest-2.0.874-5ubuntu7.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
autopackage test log for xenial
** Attachment added: "autopkgtest-2.0.873+git0.3b4b4500-14ubuntu3.5.log.gz"
https://bugs.launchpad.net/bugs/1783129/+attachment/5174765/+files/autopkgtest-2.0.873+git0.3b4b4500-14ubuntu3.5.log.gz
--
You received this bug notification because you are a member
autopackage test log for bionic
** Attachment added: "autopkgtest-2.0.874-5ubuntu2.1.log"
https://bugs.launchpad.net/bugs/1783129/+attachment/5174749/+files/autopkgtest-2.0.874-5ubuntu2.1.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
autopackage test log for xenial
** Attachment added: "autopkgtest-2.0.873+git0.3b4b4500-14ubuntu3.5.log"
https://bugs.launchpad.net/bugs/1783129/+attachment/5174748/+files/autopkgtest-2.0.873+git0.3b4b4500-14ubuntu3.5.log
--
You received this bug notification because you are a member of
autopackage test log for cosmic
** Attachment added: "autopkgtest-2.0.874-5ubuntu7.log"
https://bugs.launchpad.net/bugs/1783129/+attachment/5174750/+files/autopkgtest-2.0.874-5ubuntu7.log
** Attachment removed: "autopkgtest-2.0.873+git0.3b4b4500-14ubuntu3.5.log"
Also uploaded to bionic. 2.0.874-5ubuntu2.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785108
Title:
net-interface-handler operates on all adds and removes
To manage notifications about this
I went ahead and uploaded to xenial.
2.0.873+git0.3b4b4500-14ubuntu3.5 is in the queue now.
** Description changed:
=== Begin SRU Template ===
[Impact]
Incorrect handling of udev events by open-iscsi's net-interface-handler
results in nameserver and dns search entries being removed from
I've uploaded a fix to cosmic.
If that passes dep8 tests there I will plan to upload the fix to
xenial-proposed as shown in the MP attached.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785108
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784901
Title:
Backport cloud-init status --wait to Trusty
To manage
** Also affects: cloud-init (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Trusty)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu Trusty)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a
@mwhudson,
your suggested change seems reasonable to me.
I don't love the use of 'eval', but it seems reasonably safe here.
Instead of quoting you could just reject argv[1] input if it
had characters other than [a-zA-z_.-] . Perhaps that makes
this more difficult.
Also, maybe you should try to
Bah. similar to described in
http://cloudinit.readthedocs.io/en/latest/topics/hacking.html
but instead of 'master' you'll propose merge into ubuntu/trusty.
Also, you will need to do the change as a "quilt 3.0" format...
that is to say your change will add a file to debian/patches/
and will
Hi Shane,
Could you put this into a git branch and propose it for merge into
ubuntu/trusty branch of upstream?
Similar to
please feel free to ping me if what i'm asking isn't clear.
Scott.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785683
Title:
dep8 tests fail on non-intel
To m
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Importance: Undecided => Low
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Assignee: (unassigned) => Scott Moser (smoser)
--
You
** Changed in: software-properties (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667725
Title:
[feature request] make full ppa signing public key
** Also affects: open-iscsi (Ubuntu Cosmic)
Importance: Medium
Status: Confirmed
** Also affects: open-iscsi (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: open-iscsi (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: open-iscsi
** Description changed:
=== Begin SRU Template ===
[Impact]
Incorrect handling of udev events by open-iscsi's net-interface-handler
- results in nameserver and dns search entries being removed from
+ results in nameserver and dns search entries being removed from
/etc/resolv.conf and
Public bug reported:
=== Begin SRU Template ===
[Impact]
Incorrect handling of udev events by open-iscsi's net-interface-handler
results in nameserver and dns search entries being removed from
/etc/resolv.conf and thus potentially breaking dns on a system.
This problem is limited to iscsi-root
301 - 400 of 11836 matches
Mail list logo
