@Rafael,
the critical path would be to check the output from:
udevadm info --query=all --name=/dev/sd[cd] | grep -i serial
ID_SERIAL does not get set on Disco where we have sg3-utils package
install, which adds the s3g-utils-udev package, and includes the rules
file 55-scsi-sg3_id.rules.
This u
The _real_ concern is:
do you get the _same_ ID_SERIAL value with and without the sg3-utils-
udev package installed?
Can you compare: /dev/disk/by-id/*https://bugs.launchpad.net/bugs/1833618
Title:
failing to deploy Ubuntu Disco
To manage notifications about this bug go to:
https://bugs.launc
@Dan/Chad I suggest we skip-by this bug number on the eoan vlan test
case;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846232
Title:
vmtests: test_ip_output failing in vlan tests on eoan
To man
This looks to be related to networkd:
https://github.com/systemd/systemd/pull/12574/commits
Which is automatically added 4 bytes to base interface MTU, even though
we're explicitly setting mtu to 1500 on base interface and vlan.
** Also affects: systemd (Ubuntu)
Importance: Undecided
This can be reproduced in an LXD Eoan container:
lxc launch ubuntu-daily:eoan e1
lxc exec e1
cat > /etc/netplan/50-cloud-init.yaml << EOF
network:
version: 2
ethernets:
eth0:
dhcp4: false
mtu: 1500
vlans:
eth0.2667:
id: 2667
*** This bug is a duplicate of bug 1840524 ***
https://bugs.launchpad.net/bugs/1840524
2019-10-03 17:52:22,159 curtin:1156 Validation error:
'eui.ace42e00954452d62ee4ac01' is not valid under any of the given
schemas in
{
"id": "disk-nvme0n1",
"path": "/dev/nvme0n1",
"serial": "PC
Actually, this isn't right; For DASD, we need to specify 'vtoc'.
storage:
version: 1
config:
The example config and docs don't mention VTOC; the mention of MBR and
DOS is not correct at all. The curtin dasd code, checks for vtoc; which
currently will fail schema validation; I'll put up a branch to fix docs
and schema for curtin right now.
** Changed in: curtin (Ubuntu)
Importance: Und
commit 08bf6ff7c6dd919bb420f610d2b427ce161d6096
Author: Dimitri John Ledkov
Date: Thu Apr 11 18:29:03 2019 +
Setup kernel-img.conf like base-installer/live-installer did.
LP: #1534162
Should we remove it entirely, or only on target_release E and newer?
Or can we tell whether
What's the bad path if we don't specify the mpath device name?
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
** Changed in: curtin (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@thinktwo nothing missing, the fix is entirely in systemd. Please open
a new bug and put in your steps so we can track down what's going wrong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815254
the UUID is already bound to the device mapper device:
% cat fstab
UUID=50e5271d-665f-4edb-a023-e2f744679751 / ext4 defaults 0 0
UUID=5d9f777b-c102-4d8f-b4f5-56195c4ae21c /home ext4 defaults,nofail 0 0
% cat ls_al_byuuid
total 0
drwxr-xr-x 2 root root 120 Oct 8 14:37 .
drwxr-xr-x 8 root root
Curtin hasn't made any changes here; but I suspect the workload on the
target machine which created the thin lv's has left metadata that curtin
doesn't yet know how to clear. As a workaround for now, you can use the
MAAS disk-erasure to clear the volumes before attempting to deploy.
https://maas.
** 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.launchpad.net/bugs/1840928
Title:
FFE: include changes to enable ssh access sooner during boot
To manage
I'm marking the curtin task invalid; it's likely that the subiquity
task is invalid as well; it appears to be something with the live image
build. If you find out that there's something wrong with curtin itself,
please re-open the curtin task and mark it New.
** Changed in: curtin (Ubuntu)
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
** Changed in: curtin (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847058
Title:
MAAS depl
** Changed in: cloud-init (Ubuntu)
Status: New => 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/1825444
Title:
"make rpm" fails on CentOS after commit 947d3c208
To manage notif
** Changed in: cloud-init (Ubuntu)
Status: New => 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/1824185
Title:
Release a new upstream snapshot to disco
To manage notifications a
This was fixed in commit:
https://git.launchpad.net/cloud-
init/commit/?id=947d3c20891815f164f4c7a8884d1f02ae4a9c5b
** Changed in: cloud-init
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Hi,
Thanks for reporting this.
DataSourceConfigDrive doesn't currently set this value, and likely won't
by default. However, we do want to allow user-config to opt-in to this
behavior.
This is a work-in-progress feature, currently here:
https://code.launchpad.net/~raharper/cloud-init/+git/clou
** Changed in: curtin (Ubuntu)
Importance: Undecided => High
** Changed in: curtin (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805674
Title:
curtin shou
** Changed in: curtin (Ubuntu)
Importance: Undecided => High
** Changed in: curtin (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805673
Title:
dname for m
Reading through the lxd issue log, it appears that a host networking
issue/packaging issue triggered on upgrade; unrelated to cloud-init
inside the containers. If you feel that cloud-init isn't doing
something correct, please re-open this bug with new information.
Thanks.
** Changed in: cloud-in
Xenial GA kernel bcache unregister oops:
http://paste.ubuntu.com/p/BzfHFjzZ8y/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
On Wed, May 8, 2019 at 11:55 PM Trent Lloyd
wrote:
> I have been running into this (curtin 18.1-17-gae48e86f-
> 0ubuntu1~16.04.1)
>
> I think this commit basically agrees with my thoughts but I just wanted
> to share them explicitly in case they are interesting
>
> (1) If you *unregister* the ca
ubuntu@ubuntu:~$ uname -r
4.15.0-56-generic
ubuntu@ubuntu:~$ cat /proc/version
Linux version 4.15.0-56-generic (arighi@kathleen) (gcc version 7.4.0 (Ubuntu
7.4.0-1ubuntu1~18.04.1)) #62~lp1796292 SMP Thu Aug 1 07:45:21 UTC 2019
This failed on the second install while running bcache-super-show /dev
Public bug reported:
Installing into a chroot without /run mounted, grub's os-prober calls
into lvs for details and it waits a very long time. I believe this is
fixed upstream:
https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=3ebce8dbd2d9afc031e0737f8feed796ec7a8df9
1. Eoan
2. lvm2 2.03.
On Thu, Aug 1, 2019 at 10:15 AM Andrea Righi
wrote:
> Thanks Ryan, this is very interesting:
>
> [ 259.411486] bcache: register_bcache() error /dev/vdg: device already
> registered (emitting change event)
> [ 259.537070] bcache: register_bcache() error /dev/vdg: device already
> registered (emitt
Reproducer script
** Attachment added: "curtin-nvme.sh"
https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17962
** Changed in: curtin (Ubuntu)
Status: Fix Committed => 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/1772618
Title:
btrfs-tools is dead, long live btrfs-progs
To manage notifica
I tried the +3 kernel first, and I got 3 installs and then this hang:
[ 549.828710] bcache: run_cache_set() invalidating existing data
[ 549.836485] bcache: register_cache() registered cache device nvme1n1p2
[ 549.937486] bcache: register_bdev() registered backing device vdg
[ 550.018855] bca
Trying the first kernel without the change event sauce also fails:
[ 532.823594] bcache: run_cache_set() invalidating existing data
[ 532.828876] bcache: register_cache() registered cache device nvme0n1p2
[ 532.869716] bcache: register_bdev() registered backing device vda1
[ 532.994355] bcache
On Mon, Aug 5, 2019 at 8:01 AM Andrea Righi
wrote:
> Ryan, I've uploaded a new test kernel with the fix mentioned in the
> comment before:
>
> https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-56.62~lp1796292+4/
>
> I've performed over 100 installations using curtin-nvme.sh
> (install_count = 1
On Mon, Aug 5, 2019 at 1:19 PM Ryan Harper
wrote:
>
>
> On Mon, Aug 5, 2019 at 8:01 AM Andrea Righi
> wrote:
>
>> Ryan, I've uploaded a new test kernel with the fix mentioned in the
>> comment before:
>>
>> https://kernel.ubuntu.com/~arighi/LP-
This looks related:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839529
Title:
Live-server installation fails to install on Samsung
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: Expired => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832381
Title:
Marking this invalid since DASDs can't be used directly without a
partition table.
** Changed in: bcache-tools (Ubuntu)
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/1821
Looks to have a fix committed now.
https://github.com/CanonicalLtd/netplan/commit/ee94ec118a8aabef8d79e78e7b2f028615a28ce8
** Changed in: netplan
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
IIUC
"proper partition setup" for callers of curtin is:
/boot/EFI partition *and* a grub_bios partition.
Something like:
config:
- id: main_disk
type: d
Can you collect:
systemctl list-jobs?
>From the logs, it appears that snapd has not yet seeded, which blocks
cloud-final.service from running, so it's blocking until snapd is ready.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification becau
On Mon, Jun 3, 2019 at 2:05 PM Andrey Grebennikov <
agrebennikov1...@gmail.com> wrote:
> Is there an estimate on getting this package in bionic-updates please?
>
We are starting an SRU of curtin this week. SRU's take at least 7 days
from when they hit -proposed
possibly longer depending on test
Public bug reported:
On Xenial
1. add-apt-repository --enable-source --yes ppa:curtin-dev/daily
2. apt-get install --no-install-recommends -qy curtin
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution
Public bug reported:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these improvements.
The notable ones are:
*
See the changelog entry below for a full list of changes and bug
Not an upstream bug.
** Changed in: curtin
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/1831772
Title:
sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
To manage no
Looks like this issue, I think:
https://github.com/systemd/systemd/issues/12490
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubunt
ntu only
+
+ -- Ryan Harper Wed, 05 Jun 2019 13:46:57 -0500
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
https://git.launchpad.net/curtin/commit/?id=55aa836f04657dac67445e154b2ee5fe78b8db8a
** Changed in: curtin (Ubuntu)
Status: New => 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/18
** Summary changed:
- vmtests: test_ip_output failing in vlan tests on eoan
+ networkd pads interface MTU by 4 bytes for vlan even when told not to
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/184623
At least for Xenial, this still fails, the xfs module either not build-
in, or not copied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi doesn't install fs module needed to a
Public bug reported:
Curtin has been given (or maybe generated for subiquity) a storage
config which includes a serial value with wwn prefixing the actual
serial (eui-X). This results if failure to find the disk since the
wwn prefix is not needed.
---
curtin: Installation started. (19.2)
sta
That looks like a different bug, but still a bug. I've opened a new bug
to track this issue.
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1849322
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Curtin is prefixing 'wwn' for configs which specify a wwn value. The
wwn value does not include the string 'wwn' and udev rules for
persistent disks prefix the wwn with wwn- symlink in
/dev/disk/by-id at all.
** Changed in: subiquity (Ubuntu)
Status: New => Invalid
** Changed in: curtin
** Also affects: subiquity (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/1849325
Title:
18.04 Server Install - Software RAID setup crashes
To ma
Curtin does not rely on device numbers, rather MAAS provides curtin with
a serial or wwn value which curtin finds via udev.
Let's look at the storage configuration sent to the system and the
install logs to see if we can sort out what's going wrong.
https://discourse.maas.io/t/getting-curtin-debu
Thanks for filing the bug. We'll need some more information to see
what's gone wrong.
Would you be able to test the latest version of subiquity to see if it's
still not working?
https://discourse.ubuntu.com/t/how-to-test-the-latest-version-of-
subiquity/12428
Can you switch to tty2 and extract
@stewart
I think you're seeing this bug:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1849322
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841321
Title:
Curtin Fails to Validate Storage
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Importance: Undecided => Wishlist
** Changed in: cloud-init
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Hi Steve, Dmitri,
Do you have more details on the grub process. Curtin already runs grub
on one or more devices as needed. Are there any specific parameters or
settings or will the grub install process detect hybrid configuration?
Are there any restrictions on how the partitions are ordered or
Hi Andy,
Please do file a bug on the NIC issues; they certainly should work and
the modules should be present.
Currently the installer does not create a persistent location. A few
options here are:
1) cat the file to screen and take photos; you won't be the first to
submit a bug report with scr
I cannot verify this is working on bionic with ipv6 static addresses.
root@ubuntu:~# lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
root@ubuntu:~# cat /etc/cloud/build.info
build_name: server
serial: 20191021
root@ubuntu:~# uname -a
Linux ubuntu 4.15.0-66-generic #75-Ubu
The original netplan yaml I was testing was simpler, but also failed so
I tried to see if additional settings would make a difference, but it
did not.
network:
version: 2
ethernets:
interface0:
dhcp4: true
match:
macaddress: '52:54:00:12:34:0
I suspect that subiquity may need to wait until some of the multipath
services have finished starting up before initiating the probe, or
possibly retriggering the probe on udev events.
I don't think there's anything for curtin to do in this bug report so
I'm marking invalid. If it turns out we ne
I did some more testing today. I upgraded systemd and netplan.io to
disco level, rebooted and tested the MTU settings; disco packages fail
as well. I then upgraded to eoan systemd/netplan.io rebooted and the
MTU settings are correct.
--
You received this bug notification because you are a memb
In the Eoan version of systemd, I can see in the logs these messages:
Oct 24 18:52:32.753746 ubuntu systemd-networkd[1167]: Setting
'/proc/sys/net/ipv6/conf/interface1/proxy_ndp' to '0'
Oct 24 18:52:32.753848 ubuntu systemd-networkd[1167]: Setting
'/proc/sys/net/ipv6/conf/interface1/use_tempaddr
On Fri, Oct 25, 2019 at 1:31 PM Dan Streetman
wrote:
> I looked at this for a few minutes, and it seems strange that it works
> at all (at boot) since networkd sets the ipv6 mtu before bringing the
> link up, but the kernel resets the ipv6 mtu to the device mtu on link
> up. I must be missing so
# find /etc/cloud
/etc/cloud
/etc/cloud/cloud.cfg.d
/etc/cloud/cloud.cfg.d/05_logging.cfg
/etc/cloud/cloud.cfg.d/README
/etc/cloud/cloud.cfg.d/90_dpkg.cfg
/etc/cloud/build.info
/etc/cloud/cloud.cfg
/etc/cloud/templates
/etc/cloud/templates/chef_client.rb.tmpl
/etc/cloud/templates/ntp.conf.sles.tmp
** Also affects: curtin
Importance: Undecided
Status: New
** Changed in: curtin
Importance: Undecided => High
** Changed in: curtin
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
@Balint, after further testing, here's where things are:
-
On LXD Containers
-
On Bionic
1) First boot: neither interface mtu, nor ipv6 mtu is applied.
2) Restarting systemd-networkd: neither interface nor ipv6-mtu is applied
3) netplan apply: interface mtu
This looks hypervisor/kernel related.
Some observations:
The cloud-init.log in the collect-logs shows cloud-init running twice.
The first time, run-time is expected, approx 17s of cloud-init time, the
second boot took much longer, but the bulk if the time is in udev
2019-06-20 18:09:18,951 - u
@Dan,
Ill try the ppa and report back.
cloud-init is not doing anything special here, we render the config and call
netplan generate.
If we take cloud-init out of the picture, and just have a file in /etc/netplan
it will still fail due to the udev issue you specify. Shouldn't netplan itself
ha
*** This bug is a duplicate of bug 1849322 ***
https://bugs.launchpad.net/bugs/1849322
** This bug has been marked a duplicate of bug 1849322
Bogus serial string in subiquity install wwn-eui.*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Testing with @ddstreet's systemd ppa, I can confirm that bionic, disco
and eoan correctly set MTU on first boot, no systemd-restart needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671951
Title:
On Mon, Nov 4, 2019 at 9:41 AM Rafael David Tinoco <
rafaeldtin...@kernelpath.com> wrote:
> I believe that happens because sg3-utils-udev started being deployed in
> cloud img from Disco and beyond. By not having the package installed by
>
Disco and newer include the multipath-tools package which
On Thu, Sep 12, 2019 at 5:00 PM Patricia Domingues <
patricia.doming...@canonical.com> wrote:
> Ryan,
> Sorry for delay, we had a BMC issue and it required a manual intervention
> to fix it.
> I've tested Eoan in that machine and it also fails, it doens't show the
> same curtin error as Disco show
Public bug reported:
On Eoan, efibootmgr -v output fails with error "UiAppCound not parse
device path"; this succeeds on Disco and Bionic.
root@ubuntu:/# efivar --name 8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot
--print
GUID: 8be4df61-93ca-11d2-aa0d-00e098032b8c
Name: "Boot"
Attributes:
Curtin hasn't ever run zfs export on the pools; so either something else
did this previously, or it wasn't a requirement.
I can see if adding a zfs export on the pool works around the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
A quick hack shows that if we export after unmount. I'd like to
understand if we we need/should use import -f, however, curtin can now
ensure it exports pools it has created at the end of install.
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844320
Title:
efibootmgr -v UiAppCould not parse device path
To manage notifications about this bug go to:
https://bugs
Thanks! I can confirm this fixes the issue we found:
root@ubuntu:/# apt-cache policy efivar
efivar:
Installed: 37-2ubuntu2
Candidate: 37-2ubuntu2
Version table:
*** 37-2ubuntu2 500
500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
root@u
2019-09-26 21:11:56,148 block-discover:96 probing failed restricted=True
Traceback (most recent call last):
File
"/snap/subiquity/1196/lib/python3.6/site-packages/subiquity/controllers/filesystem.py",
line 93, in _probed
self.model.load_probe_data(storage)
File
"/snap/subiquity/1196/lib/
This needs fixing in curtin.
** Also affects: curtin (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/1845611
Title:
Install fails on ppc64el (unre
** Changed in: curtin (Ubuntu)
Status: New => 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/1845611
Title:
Install fails on ppc64el (unrecognized partition table: 'mac')
To manag
Public bug reported:
1) # lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
2) # apt-cache policy netplan.io
netplan.io:
Installed: 0.36.3
Candidate: 0.40.1~18.04.3
Version table:
0.40.1~18.04.3 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/mai
Public bug reported:
1. Disco
2. probert (0.0.14.2build1)
3. probert --network produces json output
4. probert --network dumps stack trace
root@rharper-d1:~# probert --network
Traceback (most recent call last):
File "/usr/bin/probert", line 62, in
main()
File "/usr/bin/probert", line 5
Building probert from git tip (HEAD =
8b56d73068ec1f293d3db3b0b44966ede9ed1c94) works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811279
Title:
probert --network throws stacktrace
To manag
@Jeff I cannot read the canonical pastebin output, can you use
paste.ubuntu ?
re: -updates; MAAS needs to initiate an SRU for archive users of MAAS.
@nb
I don't know for sure. I was told that MAAS snaps would pull curtin
from git master (or the respective release branches).
--
You received
@Dann Thanks.
Can you provide the log without your changes? Or at least the
efibootmgr dump before curtin starts processing things?
> Notice we have no entry for current/0003. I have not inspected the code to
> determine whether or not this is an issue parsing efibootmgr output or the
> actua
" # curl http://169.254.169.254/openstack/2018-08-27/network_data.json
{"links": [{"id": "tapa035fb68-01", "vif_id":
"a035fb68-010c-42e3-8da7-ea3c36a0d607", "type": "ovs", "mtu": 8942,
"ethernet_mac_address": "fa:16:3e:31:26:f7"}], "networks": [{"id": "network0",
"type": "ipv4_dhcp", "link": "ta
> So I would suggest that whenever OpenStack eludes to dynamic configuration
> being in play cloud-init should not write the MTU value into the on-disk
> configuration but let it be configured by dynamic network configuration
> protocol.
>
> What do you think?
I would argue the opposite. The exis
> On the flip side the presence of the MTU key in the OpenStack
> metadata cannot be used as an indicator for intent from either the
> system or the user that the DHCP server should not be providing the
> MTU either.
>
> Looking at the commit that changed the behaviour in OpenStack the
> intent of
Thanks for the logs Dann,
The error comes from efibootmgr itself; so I don't think this is the
same issue. You can open a new bug; but it still looks like a
firmware/platform issue.
efibootmgr claims there are 5 entries; and at least after a grub
install, there is only one. What happened to all
> I guess it's time for me to ask a question: is it cloud-init that
> renders /etc/netplan/50-cloud-init.yaml? If so where does netplan
> fit in when the difference is how that file is rendered and not
> how it is interpreted. As you can see in #10 the mtu statement is
> not in the file on bionic,
Looking back at your patch:
Index: curtin-20.1-29-g81144052/curtin/util.py
===
--- curtin-20.1-29-g81144052.orig/curtin/util.py
+++ curtin-20.1-29-g81144052/curtin/util.py
@@ -886,6 +886,7 @@ def get_efibootmgr(target=None):
"""
On Thu, Oct 15, 2020 at 10:45 AM Frode Nordahl <1899...@bugs.launchpad.net>
wrote:
> Ryan, thanks for those pointers, will check. I also see in #15 that
> Bionic uses Fallback while Focal uses an actual ds, don't know why
> though.
>
Bah, I *keep* forgetting, that Bionic does *NOT* read OpenStack
@Dann
OK. That sounds reasonable. For this issue, curtin can (and I think it
makes sense) ignore a BootCurrent value if there is no corresponding
entry; warn in the logs that it's missing, check your firmware, etc...
and proceed if it can.
** Changed in: curtin (Ubuntu)
Importance: Undecide
@Eric
Yeah, I *think* that will work; I believe at the time I manually
performed that step and it worked.
I'm not sure w.r.t Secure Boot and shim-signed; Maybe @vorlon can
confirm if the xfs grub2 module is signed/included in shim-signed?
> As follow:
> https://salsa.debian.org/grub-team/grub/-
You might just mark this bug duplicate of the other so we can close both
if this fixes things; and if so, I can update our vmtest which exercises
this path. Note this is broken all the way back through Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi Dan,
Could you summarize the problem with flash-kernel and this system?
* dann frazier <1918...@bugs.launchpad.net> [2021-03-15 18:25]:
> Attached is a patch for curtin that works for me, though it could use
> some cleanup. It installs flash-kernel in the same place GRUB gets
> installed for E
** Also affects: curtin
Importance: Undecided
Status: New
** Also affects: subiquity (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/191632
Hi,
Thank you for filing a bug and helping make Ubuntu better. I believe
the regex restriction is happening in the Ubuntu Server Live Installer
(subiquity). I've added that package to this bug.
Here's the source code in question you're hitting.
https://github.com/canonical/subiquity/blob/a76581
301 - 400 of 1382 matches
Mail list logo
