On Jaunty amd64, still broken for me (gnome-terminal 2.26.0, libvde9
/libvde-common 0.20.0). Following the gnome bug entry[1], it looks like
it's a vde[2] bug instead. This fix isn't yet in Jaunty, but was just
recently updated to Karmic[3]. I installed the karmic versions of
libvte9, libvte-com
Need the presence patch for jaunty amd64.
--
pidgin crashes in libmeanwhile just after connecting
https://bugs.launchpad.net/bugs/261695
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Tested the jaunty amd64 PPA package , fixed my presence issues.
--
pidgin crashes in libmeanwhile just after connecting
https://bugs.launchpad.net/bugs/261695
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
I have a t61p with 64-bit hardy. I can confirm that setting the above
quirks to false fixes my suspend to ram (blank screen on resume).
--
wrong quirks set for Thinkpad T61 with nvidia video
https://bugs.launchpad.net/bugs/225230
You received this bug notification because you are a member of Ubu
* Christian Dohm <1906...@bugs.launchpad.net> [2020-11-29 15:50]:
> Public bug reported:
>
Thank you for filing a bug.
> I've created a 'network-config' file with Terraform's yamldecode() function
> that contains (btw. I've tried with the version being a Number w/o quotes and
> as well as a St
I'm marking the cloud-init task invalid for now.
As mentioned in the other bug[1]; cloud-init is not running too late;
rather scripts not provided to cloud-init are not waiting for cloud-init
to complete its execution. If your scripts are using cloud-init status
--wait before executing or syste
Can you run and attach the output tarball on the target system where you
see this fail:
cloud-init collect-logs
With respect to your use-case; cloud-init does not directly control what
packages do at install time. Some package may require post-install
configuration, or are not typically insta
Please move this back to New after you've attached the cloud-init
collect-logs output tarball.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
* eoli3n <1907...@bugs.launchpad.net> [2020-12-08 11:50]:
> > I can say that the Ubuntu Server installer isn't typically used to install
> > Ubuntu Desktop.
> I use it because i can't find any netboot installer which supports
> autoinstall and EFI installation. I used legacy netboot (60MB) for my
* eoli3n <1907...@bugs.launchpad.net> [2020-12-08 13:30]:
> If i run autoinstall with that user-data file, autoinstall doesn't run
> and subiquity prompt for language setting.
>
> #cloud-config
> runcmd:
> - systemctl daemon-reload
> - systemctl restart gdm3
> autoinstall:
> version: 1
> p
Public bug reported:
1. # lsb_release -rd
Description:Ubuntu 16.04.4 LTS
Release:16.04
2. # apt-cache policy zfsutils-linux
zfsutils-linux:
Installed: 0.6.5.6-0ubuntu19
Candidate: 0.6.5.6-0ubuntu19
Version table:
*** 0.6.5.6-0ubuntu19 500
500 http://archive.ubuntu.com/u
You can also do:
apport-collect 1760776
and
cloud-init collect-logs # this writes a cloud-init.tar.gz to the
current directory
And attach those to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Is this also fixed in bionic yet?
On Tue, Apr 3, 2018 at 9:10 AM, Launchpad Bug Tracker
<1729...@bugs.launchpad.net> wrote:
> This bug was fixed in the package linux - 4.13.0-38.43
>
> ---
> linux (4.13.0-38.43) artful; urgency=medium
>
> * linux: 4.13.0-38.43 -proposed tracker (LP:
On Wed, Apr 4, 2018 at 5:44 AM, Pengpeng Sun <1760...@bugs.launchpad.net> wrote:
> Yes, I saw 'No ds found [mode=search, notfound=disabled]. Disabled
> cloud-init' from /run/cloud-init/ds-identify.log, will attach it.
>
> The Ubuntu Server is the server build I downloaded from below link and
> ins
> this issue doesn't exist in ubuntu-18.04-Server-64.
The server image for 18.04 uses cloud-init during its initial boot as
part of how the new server installer works; The desktop does not use
cloud-init in any way; it is not expected to run desktop images; cloud-
init is a boot-time service for
I'm marking this bug as invalid as the scenario described is not valid.
Installing cloud-init into a desktop image does not mean that cloud-init
service will run; it's a boot time service that requires providing
cloud-init a valid datasource. If you disagree, please reopen and
provide further deta
As per cloud-init networking disabled. Please reopen task if you find
cloud-init is in the picture here.
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
I've just seen that upstream systemd v239 claims to support IPV6MtuBytes
https://lwn.net/Articles/758128/
* networkd's .network files now support a new IPv6MTUBytes= option for
setting the MTU used by IPv6 explicitly as well as a new MTUBytes=
option in the [Route] section to configure the MTU t
The commit:
https://git.launchpad.net/curtin/commit/?id=4bf7750b6010f0483b22ff626eab58d6a85bb072
** Changed in: curtin
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Hello,
I believe this issue is resolved in this commit[1].
There is a new version of curtin for Xenial which contains the fix. Can you
update curtin to the latest?
curtin | 18.1-17-gae48e86f-0ubuntu1~16.04.1 | xenial-updates/universe |
all
--
You received this bug notification because you are
Can you provide the curtin install log?
** Changed in: curtin
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778704
Title:
redeployment of node with bcache fails
T
On Fri, Jun 29, 2018 at 11:20 AM Gábor Mészáros
wrote:
>
> That I can later, not now.
> What I see now though is mds are not clean and resync started:
Yes; the updated curtin does a number of things to prevent this from
happening.
1) we wipe the first and last 1M of the raid device itself
2) we
> I assume curtin only does the wipefs when the bcache devices are
attached, correct?
Yes; curtin probes the disks that are present and activates them as
needed. Bcache is activated by the kernel itself if the metadata header
is present on any block device.
If the disk is not attached to the end
It seems there are some limitations to what systemd will do with
IPv6BytesMTU.
1) if LinkLocalAddressing is not disabled, it will clobber any
IPv6BytesMTU value set.
[Network]
LinkLocalAddressing=ipv6
Address=10.10.10.10/24
IPv6MTUBytes=1470
This results in: /proc/sys/net/ipv6/conf//mtu having a
The 4.15.0-39 kernel FAILs:
+ make-bcache -C /dev/sdb
Can't open dev /dev/sdb: Device or resource busy
+ exit 1
Successful runs: 24
root@ubuntu:~# [ 242.655013] INFO: task kworker/3:103:2610 blocked for more
than 120 seconds.
[ 242.665486] Not tainted 4.15.0-39-generic #43~lp1784665
[ 24
On Mon, Nov 26, 2018 at 11:11 PM Jay Vosburgh
<1671...@bugs.launchpad.net> wrote:
>
> Regarding #2 from comment #19:
>
> As the defined range for the ipv6.mtu is from IPV6_MIN_MTU to the
> device's MTU, and the existing API returns an error if the ipv6.mtu is
> out of range, I think it's reasonable
It took a while, but v4.15-rc6 fails; so we need to move back a bit.
[ 2541.139904] bcache: bcache_device_free() bcache0 stopped
[ 2541.141848] BUG: unable to handle kernel NULL pointer dereference
at 0d38
[ 2541.143813] IP: search_free+0ex01-b6435-e1/5f0x40 [bcache]
[ 2541.145676] PG
I also tested v4.15-rc5, which failed with the same stack trace. Then I
returned to 4.14 mainline, and got this one:
[ 953.659489] BUG: unable to handle kernel NULL pointer dereference at
0d40
[ 953.668707] IP: searc
v4.13 shows the same search_free stack as 4.14, but doesn't appear to be
fatal (it doesn't result in a hung process nor a block device that
cannot be wiped.
I suspect we've got a new upstream issue since 4.20 didn't fix things.
Re-running 4.20 to see if we had a stack trace, we don't NULL pointer
Public bug reported:
dname for disks creates a symlink based on disk properties, like serial
or wwn. In the case that we have disks that are part of a multipath
scenario, then the dname will point to one of many kernel block devices
(sda, sdb, etc) which actually are the same disk.
The dname for
Public bug reported:
When mounting a complex (raid, lvm) curtin should not use the filesystem
UUID in fstab as it may refer to a member of the array rather than the
filesystem itself. LVM snapshots also retain the same filesystem UUID
which may cause confusing results when rebooting, or possibly
Public bug reported:
When rendering a per-subnet route with a metric, the value is ignored
due to clobbering of the looping variable.
Consider this v1 input:
{
"version": 1,
Note, this also affects the eni and sysconfig router as well.
** Summary changed:
- netplan renderer misses metric value in per-subnet routes
+ net renderers miss metric value in per-subnet routes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*renderers*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805871
Title:
net renderers miss metric value in per-subnet routes
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Can you collect the following:
Backing device baseline (it's possible the underlying disks regressed
instead of the bcache layer). the same fio randrw test against the
underlying backing device with bcache disabled
And with bcache enabled on both setups before and after tuning:
1) grep -r . /sys
Public bug reported:
When generating a network-config (v1), any routes should be provided under the
scope of a subnet.
For some renderers (eni) using the top-level routes in the config will
'accidentally' work due to ifupdown implementation, however, routes should
instead be scoped under a netw
On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov
wrote:
> Using systemd 237-3ubuntu10.10
>
> Using:
> [Match]
> Name=ens3
> [Network]
> DHCP=ipv4
> IPv6MTUBytes=1600
> [Link]
> MTUBytes=1800
> [DHCP]
> UseMTU=no
> RouteMetric=100
>
Do you put this in the same .network file or .link file?
--
On Tue, Dec 4, 2018 at 10:30 AM Mathieu Trudel-Lapierre <
mathieu...@gmail.com> wrote:
> I disagree.
>
> We'd be working around a real design issue in systemd, rather that
>
While, I agree that having systemd-udev to apply MTU to devices is
less than ideal; I don't see having systemd or networkd
On Tue, Dec 4, 2018 at 9:31 AM Ryan Harper
wrote:
>
>
> On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov
> wrote:
>
>> Using systemd 237-3ubuntu10.10
>>
>> Using:
>> [Match]
>> Name=ens3
>> [Network]
>> DHCP=ipv4
>> IPv6
On Tue, Dec 4, 2018 at 12:31 PM Mathieu Trudel-Lapierre <
mathieu...@gmail.com> wrote:
> The problem is that DEVTYPE is unreliable at best. Using the MAC of one
> of the member interfaces is fine, but only if you really know what
> you're doing.
>
> I think we're otherwise back to matching by name
Can we confirm which version of curtin you have installed?
** Changed in: curtin (Ubuntu Trusty)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791006
Title:
deplo
The error I see is:
Run install hook of "lxd" snap if present
2018-10-10T20:06:30Z ERROR run hook "install": cannot create lock
directory /run/snapd/lock: Permission denied
$ ls -al /run | grep snapd
srw-rw-rw- 1 root root0 Oct 10 20:06 snapd-snap.socket
srw-rw-rw- 1 root root0 Oct 10
Looking at this bug:
https://bugs.launchpad.net/snappy/+bug/1665808
As we're in the same maas ephemeral environment; though we get a
slightly different error. However the workaround included:
sudo apt-get install -yu apparmor-utils
sudo aa-complain /usr/lib/snapd/snap-confine
does allow lxd sn
I suspect this reloading of profiles from the core snap has something to
do with the failure.
Oct 11 21:46:42 ubuntu systemd[1]: Mounting Mount unit for core, revision
5548...
Oct 11 21:46:42 ubuntu systemd[1]: Mounted Mount unit for core, revision 5548.
Oct 11 21:46:43 ubuntu snapd[745]: backen
Can you attach the guest xml and host kernel/qemu/libvirt packages?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
ke
And /var/log/libvirt/qemu/.log ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
kernel panic
To manage notifications
The backing image:
/var/lib/libvirt/maas-images/e5d185a9-8ccb-4ca6-959a-bd8eff0ee184
What boot image is that? Can I get a copy of that from maas-images? or
how is it created?
On the node with the vm that fails, can you:
virsh start --console
Assuming it's a normal ubuntu image which has norm
I'm unable to recreate with a daily bionic cloud-image on a bionic host
with the same versions.
% sudo apt install uvtool libvirt
% uvt-simplestreams-libvirt -vv sync --source
http://cloud-images.ubuntu.com/daily 'supported=True' arch=amd64 release=bionic
% uvt-kvm create --memory 2048 --cpu 1 --
[0.943808] Unpacking initramfs...
[ 20.690329] Initramfs unpacking failed: junk in compressed archive
[ 20.703673] Freeing initrd memory: 56612K
Looks like the initrd was compromised, possibly a networking hiccup?
Can you confirm the checksums on the source and attempt to download the
URL
Does this fail with other releases? like trusty? I was wondering if
initrd size plays a factor here:
precise/hwe-t: 25M
trusty/hwe-x: 35M
xenial/ga: 39M
xenial/hwe:53M
xenial/edge: 53M
bionic/ga: 55M
cosmic/ga: 57M
That might be faster for you to test than for us to replicate
The virtio configuration in this new kernel build changed, can it get
reverted to what the -kvm kernel currently has?
% grep VIRTIO /boot/config-*kvm
CONFIG_BLK_MQ_VIRTIO=y
CONFIG_HW_RANDOM_VIRTIO=y
CONFIG_NET_9P_VIRTIO=y
# CONFIG_RPMSG_VIRTIO is not set
CONFIG_SCSI_VIRTIO=y
CONFIG_VIRTIO=y
CONFIG
Could you re-apply the KEXEC config changes to the linux-kvm tree build?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799791
Title:
linux-kvm: please support kexec
To manage notifications about t
** Also affects: grub2 (Ubuntu)
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/1800153
Title:
[2.5] Failed to deploy ppc64el
To manage notifications about
Can you attach the curtin logs?
And do you have logs from the last previous successful run?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el
To manage no
** Changed in: curtin
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el
To manage notifications about this bug go to:
http
Can you do a curtin verbose install with GPT and capture the logs from
that? I don't think mbr should matter, but we do use 'parted' for msdos
partition creation and 'sgdisk' for gpt so there could be some issue
going on here.
--
You received this bug notification because you are a member of Ubu
@Andres can you attatch the full config when you run this under beta3
with the MBR config?
>From what I can tell, the prep partition (/dev/sda1) is created fine,
but our wipe clears out the first and last 1M , it's an 8M partition.
This is a curtin bug as you've specified 'wipe: zero' which shoul
On Tue, Oct 30, 2018 at 7:35 PM Lee Trager wrote:
>
> Every time I commission the PPC host we have in our CI I always get a
> GPT partitioning table using MAAS 2.4.2+. Looking through the source
> code it appears GPT is always set when creating a new partitioning
> table[1] and when generating th
On Wed, Oct 31, 2018 at 9:20 AM Scott Moser wrote:
>
> With regard to wiping all prep partitions...
> We do have code that does this in helpers/pt_prep. Ie, the non-storage
> config path does this.
> However, this is kind of a grey line here. If maas wants a partition wiped,
> then MAAS should
** Changed in: curtin
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el when partition table is GPT
To manage notif
This SRU has a regression:
https://bugs.launchpad.net/netplan/+bug/1795343
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793309
Title:
Backport netplan.io 0.40 to bionic
To manage notifications ab
Tested 0.40.1 from -proposed; things look good here.
root@b1:~# ls -al /etc/netplan/
total 9
drwxr-xr-x 2 root root 4 Oct 4 20:29 .
drwxr-xr-x 87 root root 175 Oct 2 06:36 ..
-rw-r--r-- 1 root root 381 Oct 1 14:53 50-cloud-init.yaml
-rw-r--r-- 1 root root 0 Oct 1 15:16 99-empty.yaml
roo
** Changed in: curtin
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796968
Title:
attempt to call string 'run_apt_upgrade' when testing proposed
To manage n
curtin-vmtest-proposed-x-console log
** Attachment added: "curtin-vmtest-proposed-x-console log"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1795712/+attachment/5213131/+files/curtin-vmtest-proposed-x-console.log
--
You received this bug notification because you are a member of Ubu
curtin-vmtest-proposed-b-console log
** Attachment added: "curtin-vmtest-proposed-b-console log"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1795712/+attachment/5213134/+files/curtin-vmtest-proposed-b-console.log
--
You received this bug notification because you are a member of Ubu
curtin-vmtest-proposed-b-artifacts.tar.xz
** Attachment added: "curtin-vmtest-proposed-b-artifacts.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1795712/+attachment/5213135/+files/curtin-vmtest-proposed-b-artifacts.tar.xz
** Description changed:
== Begin SRU Template ==
[
curtin-vmtest-proposed-x-artifacts.tar.xz
** Attachment added: "curtin-vmtest-proposed-x-artifacts.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1795712/+attachment/5213133/+files/curtin-vmtest-proposed-x-artifacts.tar.xz
--
You received this bug notification because you are
maas SRU proposed curtin sru manual testing on bionic artifacts
** Attachment added: "maas SRU proposed curtin sru manual testing on bionic
artifacts"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1795712/+attachment/5213137/+files/maas-SRU-proposed-curtin-sru-manual-bionic.tar.xz
--
4.20-rc3 also fails.
Successful runs: 95
root@ubuntu:~# [ 484.565298] INFO: task kworker/3:206:2091 blocked for more
than 120 seconds.
[ 484.566976] Not tainted 4.20.0-042000rc3-generic #201811182231
[ 484.568069] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
OK, I can recreate.
The specific detail is that the bond macaddress matches one of the
physical interfaces and that the bond itself is down at the time of
the apply command.
# netplan apply --debug
WARK: matches: {'by-driver': {}, 'by-mac': {'00:16:3e:2c:4c:e5':
'eth0', '00:16:3e:c3:41:0a': 'eth
The comments are unclear what the actual sequence of failure is, but as
comment #4 mentions the tool will automatically listen to the default
port on *ALL* interfaces (0.0.0.0).
If you want to manually create one using the existing default port, you
have to delete the 0.0.0.0 entry before adding a
This may now be a cloud-init bug if the support is there since this is
a network-config v1 -> cloud-init renders netplan.
On Fri, Sep 28, 2018 at 9:12 AM Scott Moser wrote:
>
> Hm...
>
> Our tests show that this is not fixed in cosmic or bionic.
>
> https://jenkins.ubuntu.com/server/job/curtin-vm
Actually there needs to be changes to netplan to emit the correct
IPV6BytesMtu setting to networkd; and then cloud-init can emit the
correct netplan yaml for that. This feature is on the netplan roadmap
here:
https://trello.com/c/nIjLIRSG/6-support-ipv6-mtu-bytes-configuration
** Also affects:
Comment #3 correctly diagnoses the issue (bad network-config) which
caused cloud-init to error out. And Comment #11 suggests that this
configuration has been resolved. I'm closing the cloud-init task here.
Please re-open if you believe there is a cloud-init issue that needs
fixing.
** Changed in
I'm closing the cloud-init task; If there is further information about
what cloud-init would need to do here, please reopen.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Matt,
This is expected behavior. MAAS provides network configuration to
cloud-init (via curtin). Cloud-init will rename interfaces that are
part of the provided network configuration to ensure the configuration
will apply. If you need to reconfigure or provide additional
configuration, you have
** Changed in: curtin (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750732
Title:
grub package will change the boot order for MaaS deployed system
To mana
On Thu, Apr 4, 2019 at 9:06 PM Seth Arnold <1817...@bugs.launchpad.net>
wrote:
> Two methods come to mind:
>
> - Writing an apt sources.list that omits the -updates pocket
> - Writing apt pinning rules that omits the -updates pocket.
>
> I would prefer we install all updates, unless the user has e
Hi,
For now, the version from dpkg is the best way. Netplan does have plans
for querying feature-flags/--version.
https://trello.com/c/ls9KUQuV/42-feature-availability-documentation-
introspection-feature-flags
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
@Steve,
In preparing an upload for probert, in addition to the functional
changes, there are some debian directory clean-ups, wondering if those
are acceptable under this FFe? (some of the changes are adding package
deps for the feature, so I'd assume those are).
http://paste.ubuntu.com/p/bZXHkQV
What zfs property are you aware of that takes yes/no or maybe?
** Changed in: curtin (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824172
Title:
Do not fo
On Mon, Apr 15, 2019 at 9:21 AM Pengzhen(Peter) Cao
wrote:
> Hi Ryan,
>
> As you said, "cloudinit/sources/helpers/vmware/imc/config_nic.py" now
> generates v1 network_state dictionary. Should I just add a "DHCPFROMDNS:
> true/false" key as V1 format or should I update the output to v2
> together
printf is a shell built-in which does not exec a new process like echo;
I believe this is a reasonable replacement for use of echo -n
printf "%s" ${1}
Alternatively, if you drop the /bin/echo and use bash's built-in echo;
that also will work as it won't exec a new process.
--
You received this
This is still broken on 17
** Bug watch added: github.com/rhboot/efibootmgr/issues #125
https://github.com/rhboot/efibootmgr/issues/125
** Also affects: efibootmgr via
https://github.com/rhboot/efibootmgr/issues/125
Importance: Unknown
Status: Unknown
--
You received this bug no
After walking through the code in gdb; I realize now that the --remove-
duplicates only operates on the BootOrder variable; not any of the
actual entries.
root@ubuntu:/home/ubuntu# efibootmgr -v --bootorder 0,1,2,2,2
BootNext: 0001
Timeout: 0 seconds
BootOrder: ,0001,0002,0002,0002
Boot* U
https://github.com/CanonicalLtd/probert/pull/78
** Changed in: probert (Ubuntu)
Importance: Undecided => High
** Changed in: probert (Ubuntu)
Status: New => In Progress
** Changed in: curtin
Importance: Wishlist => High
** Changed in: curtin
Status: Triaged => In Progress
-
** Attachment added: "MAAS QA results for curtin-proposed-xenial"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330653/+files/maas-qa-curtin-sru-xenial.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "MAAS QA results for curtin-proposed-bionic"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330654/+files/maas-qa-curtin-sru-bionic.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "Xenial vmtest console log"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330655/+files/curtin-vmtest-proposed-x-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Attachment added: "Xenial vmtest artifacts"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330667/+files/curtin-vmtest-proposed-x-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Attachment added: "Bionic vmtest console log"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330709/+files/curtin-vmtest-proposed-b-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Attachment added: "Bionic vmtest artifacts from repeating tests that timed
out."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330712/+files/curtin-vmtest-proposed-b-artifacts-v2.tar.xz
--
You received this bug notification because you are a member of Ubuntu
B
** Attachment added: "Xenial vmtest artifacts from rerunning tests that timed
out."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330714/+files/curtin-vmtest-proposed-x-artifacts-v2.tar.xz
--
You received this bug notification because you are a member of Ubuntu
B
** Attachment added: "Bionic curtin vmtest artifacts"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330710/+files/curtin-vmtest-proposed-b-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "Eoan vmtest artifacts"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330716/+files/curtin-vmtest-proposed-e-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Attachment added: "Eoan vmtest artifacts from rerunning timedout tests"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330717/+files/curtin-vmtest-proposed-x-artifacts-v2.tar.xz
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports
** Attachment added: "Eoan vmtest console log, including rerun of timed out
tests."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330715/+files/curtin-vmtest-proposed-e-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Attachment added: "Xenial vmtest console log from rerunning tests that timed
out."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330713/+files/curtin-vmtest-proposed-x-console-v2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: "Bionic vmtest artifacts from repeating tests that timed
out."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330711/+files/curtin-vmtest-proposed-b-console-v2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
That sounds like a good fix. It will trip in bionic, but ubuntu images
don't include multipath package by default (which pulls in sg3-utils).
If you install this in bionic, I suspect it will fail just the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
1 - 100 of 1389 matches
Mail list logo
