Public bug reported:

1) lsb_release -rd

Description:    Ubuntu 20.04.1 LTS
Release:        20.04

2) Package version
Unknown. Whatever version is part of ubuntu-20.04.1-live-server-amd64.iso 
2020-07-31 17:35

3) What I expected

For valid manual network settings to work.

4) What happened instead

Manual network configuration fails saying:

"'xxx.xxx.17.114' is not contained in '255.255.254.0/23'"

With network settings:

Subnet: 255.255.254.0/23
Address: xxx.xxx.17.114
Gateway: xxx.xxx.16.1

Subnet certainly contains xxx.xxx.16.1 - xxx.xxx.17.254

We attempted to define /23 on Address instead, but that is not allowed.

I work for NASA GSFC and we're having to proceed without network and
then manually edit /etc/netplan/*.yaml after install.

If this is an error on our part, can you please clarify what we were
supposed to enter for subnet? Since Subnet line requires an entry in
CIDR form with error "should be in CIDR form (xx.xx.xx.xx/yy)"

Manual network config works fine with:

# This is the network config written by 'subiquity'
network:
  version: 2
  renderer: networkd
  ethernets:
    enp49s0f1:
      dhcp4: no
      addresses:
        - xxx.xxx.17.114/23
      gateway4: xxx.xxx.16.1
      nameservers:
          addresses: [xxx.xxx.10.134, xxx.xxx.50.17]

**IPs redacted for security purposes

** Affects: subiquity (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "Subnet calculation error"
   
https://bugs.launchpad.net/bugs/1910155/+attachment/5449278/+files/Ubuntu-installer-subnet-error.jpg

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

Title:
  Installation manual network config fails with "x.x.x.x is not in
  contained in x.x.x.x/yy"

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to