[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-10-17 Thread Olivier Gayot
** Changed in: subiquity
   Status: Fix Committed => Fix Released

** Changed in: subiquity (Ubuntu)
   Status: Fix Committed => 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/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-20 Thread Frank Heimes
@Dan, I could retest snapshot1, sure.
But we did tests all snapshots before, and this did not happen so far (until I 
wanted to try 6.17 and used the daily from pending from Sept 10th).
(And I should have added that we always use the same systems.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-20 Thread Olivier Gayot
My previous understanding was flawed. I anticipated that renaming the
00-installer-config.yaml to 10-livefs.yaml (because 00-installer-
config.yaml is special to Subiquity) would work but it doesn't.

The main problem is that Subiquity and netplan (or the underlying
network daemon, really) have different understandings of priority when
multiple network configs match for the same interface. (obviously
netplan should be considered right and ideally Subiquity should defer to
netplan).

For instance, in the following situation:

/etc/netplan/00-installer-config.yaml
network: 2
  version:
  ethernets:
zz-all-en:
  match:
name: "en*"
  dhcp4: true

/etc/netplan/50-cloud-init.yaml
network
  version: 2
  ethernets:
 enc600:
   addresses: [10.245.236.23/24]

1. netplan (systemd-networkd) decides to honor the static addressing from 
50-cloud-init.yaml.
Indeed the generated conf files for systemd-networkd are:
   * /run/systemd/network/10-netplan-enc600.network
   * /run/systemd/network/10-netplan-zz-all-en.network
Quote from systemd.network(5): 
> The network file contains a [Match] section, which determines if a given 
> network file may
> be applied to a given interface; and a [Network] section specifying how the 
> interface
> should be configured. The first (in alphanumeric order) of the network files 
> that matches
> a given interface is applied, all later files are ignored, even if they match 
> as well.

so 10-netplan-enc600.network (generated from /etc/netplan/50-cloud-
init.yaml) is honored.

2. Subiquity decides to honor DHCP addressing because it takes the first
matching config from /etc/netplan/*.yaml (and it reads 00-installer-
config.yaml before 50-cloud-init.yaml).

In an ideal world, Subiquity should use the same logic as netplan but
netplan defers to the underlying network daemon so that will be a
challenging task. Maybe going forward Subiquity should read the
currently active network config (e.g., netplan status?) rather than
parsing /etc/netplan?

In any case, we have a few options today:

* Rename 00-installer-config.yaml to 60-livefs.yaml. This will not impact 
netplan but will impact make Subiquity give more priority to 50-cloud-init.yaml
* Drop 00-installer-config.yaml completely
* Change Subiquity so that it guesses better which config will be used after 
netplan apply.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-19 Thread Frank Heimes
From my point of view we could update this bug to Fix Released,
since using image 20250915.1 has this solved for me on s390x.

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-18 Thread Frank Heimes
Also fine with 20250917.2, which seems to become the beta image.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-17 Thread Olivier Gayot
The 00-installer-config.yaml was not present on the installer live layer
on 24.04.3. But on questing, it is present in ubuntu-server-
minimal.ubuntu-server.installer.squashfs

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-15 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   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/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-15 Thread Olivier Gayot
** Changed in: subiquity (Ubuntu)
   Status: Incomplete => Fix Committed

** Also affects: subiquity
   Importance: Undecided
   Status: New

** Changed in: subiquity
   Status: New => Incomplete

** Changed in: subiquity
   Status: Incomplete => Fix Committed

** Changed in: subiquity
 Assignee: (unassigned) => Olivier Gayot (ogayot)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-12 Thread Olivier Gayot
https://github.com/canonical/subiquity/pull/2257 should make Subiquity
behave more like netplan when determining which network config should be
honored (assuming multiple configs).

** Changed in: subiquity (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-11 Thread Olivier Gayot
Hi Frank,

Would you mind trying again but pause before reaching the network screen
and investigate the network configuration?

* ip link
* ip addr
* cat /etc/netplan/*

and potentially collect the logs?

We did change the implementation of probert.network recently but I see
no reason for it to enable a configuration that is not what you asked
for ..

Thank you,
Olivier

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-11 Thread Frank Heimes
Hi Olivier,
I've entered the installer shell right after the zDev screen (which is right 
before the NW config and could see this:

root@ubuntu-server:/# ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enc600:  mtu 1500 qdisc mq state UP mode 
DEFAULT group default qlen 1000
link/ether 02:28:0a:00:00:b3 brd ff:ff:ff:ff:ff:ff
altname enx02280ab3
root@ubuntu-server:/# ip addr
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute 
   valid_lft forever preferred_lft forever
2: enc600:  mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether 02:28:0a:00:00:b3 brd ff:ff:ff:ff:ff:ff
altname enx02280ab3
inet 10.245.236.23/24 brd 10.245.236.255 scope global enc600
   valid_lft forever preferred_lft forever
inet6 fe80::28:aff:fe00:b3/64 scope link proto kernel_ll 
   valid_lft forever preferred_lft forever
root@ubuntu-server:/# ls -ld /etc/netplan/*
-rw-r--r-- 1 root root 455 Sep  8 19:18 /etc/netplan/00-installer-config.yaml
-rw--- 1 root root 216 Sep 11 13:10 /etc/netplan/50-cloud-init.yaml
root@ubuntu-server:/# cat /etc/netplan/00-installer-config.yaml
# This is the initial network config.
# It can be overwritten by cloud-init or subiquity.
# For more information, see netplan(5)

network:
version: 2
ethernets:
zz-all-en:
match:
name: "en*"
dhcp4: true
dhcp6: true
accept-ra: true
zz-all-eth:
match:
name: "eth*"
dhcp4: true
dhcp6: true
accept-ra: true
root@ubuntu-server:/# cat /etc/netplan/50-cloud-init.yaml
network:
  version: 2
  ethernets:
enc600:
  addresses:
  - "10.245.236.23/24"
  nameservers:
addresses:
- 10.245.236.1
  routes:
  - to: "default"
via: "10.245.236.1"
root@ubuntu-server:/#

So for the installation session interface enc600 should be active with
static IP - and it seems to be the case, one screen prior to the NW
config.

Then when proceeding to the NW config screen I an stuck again with:

Network configuration   [ Help ]

  Configure at least one interface this server can use to talk to other   
  machines, and which preferably provides sufficient access for updates.  
  
NAMETYPE  NOTES   
  [ enc600  eth   -   ▸ ] 
DHCPv6  2001:67c:1562:8020:28:aff:fe00:b3/64  
02:28:0a:00:00:b3 / Unknown Vendor / Unknown Model
  
  [ Create bond ▸ ] 


I'll check again on LPAR (I might get more details there, since it allows me to 
proceed with the integrated ASCII console ...)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-11 Thread Dan Bungert
** Changed in: subiquity (Ubuntu)
Milestone: None => ubuntu-25.10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-11 Thread Dan Bungert
@frank - would you retest against snapshot 1 of questing?  We changed
things here all the way at the beginning of the cycle.

** Changed in: subiquity (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/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2122583] Re: Current questing daily installation hangs on NW config screen

2025-09-11 Thread Olivier Gayot
Observation from an amd64 VM running questing:

Before reaching the network screen
--

  $ ls /etc/netplan/
  00-installer-config.yaml  50-cloud-init.yaml

After reaching the network screen
-

  $ ls /etc/netplan
  00-installer-config.yaml  50-cloud-init.yaml.dist-subiquity

This would explain the behavior observed by Frank. However, it's not
clear to me why we would have a different behavior between questing and
previous releases.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122583

Title:
  Current questing daily installation hangs on NW config screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2122583/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs