Have to netplan apply again, after reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
New
|
Undecided
|
Unassigned | ||
subiquity |
New
|
Undecided
|
Unassigned |
Bug Description
I am trying to install ubuntu-
And I am using vlan to set the network, the installation process looks good.
But after I reboot the OS, I found we can not ssh it, and lost all of route setting.
Have to input the command of netplan apply again to set route info again.
If you need more info, please let me know.
ubuntu@ubut13:~$ sudo netplan --debug apply
[sudo] password for ubuntu:
** (generate:2388): DEBUG: 02:35:03.714: starting new processing pass
** (generate:2388): DEBUG: 02:35:03.714: enc1000.1300: adding new route
** (generate:2388): DEBUG: 02:35:03.714: We have some netdefs, pass them through a final round of validation
** (generate:2388): DEBUG: 02:35:03.714: enc1000: setting default backend to 1
** (generate:2388): DEBUG: 02:35:03.714: Configuration is valid
** (generate:2388): DEBUG: 02:35:03.714: enc1000.1300: setting default backend to 1
** (generate:2388): DEBUG: 02:35:03.714: Configuration is valid
** (generate:2388): DEBUG: 02:35:03.715: Generating output files..
** (generate:2388): DEBUG: 02:35:03.715: openvswitch: definition enc1000 is not for us (backend 1)
** (generate:2388): DEBUG: 02:35:03.715: NetworkManager: definition enc1000 is not for us (backend 1)
** (generate:2388): DEBUG: 02:35:03.715: openvswitch: definition enc1000.1300 is not for us (backend 1)
** (generate:2388): DEBUG: 02:35:03.715: NetworkManager: definition enc1000.1300 is not for us (backend 1)
DEBUG:netplan generated networkd configuration changed, reloading networkd
DEBUG:enc1000 not found in {}
DEBUG:enc1000.1300 not found in {}
DEBUG:Merged config:
network:
ethernets:
enc1000:
accept-ra: false
dhcp4: false
dhcp6: false
renderer: networkd
version: 2
vlans:
enc1000.1300:
addresses:
- 10.20.103.63/24
id: 1300
link: enc1000
nameservers:
addresses:
- 10.20.0.2
routes:
- to: default
via: 10.20.103.254
DEBUG:no netplan generated NM configuration exists
DEBUG:enc1000 not found in {}
DEBUG:enc1000.1300 not found in {}
DEBUG:Merged config:
network:
ethernets:
enc1000:
accept-ra: false
dhcp4: false
dhcp6: false
renderer: networkd
version: 2
vlans:
enc1000.1300:
addresses:
- 10.20.103.63/24
id: 1300
link: enc1000
nameservers:
addresses:
- 10.20.0.2
routes:
- to: default
via: 10.20.103.254
DEBUG:Link changes: {}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enc1000
DEBUG:netplan triggering .link rules for enc1000.1300
** (process:2386): DEBUG: 02:35:04.072: starting new processing pass
** (process:2386): DEBUG: 02:35:04.072: enc1000.1300: adding new route
** (process:2386): DEBUG: 02:35:04.072: We have some netdefs, pass them through a final round of validation
** (process:2386): DEBUG: 02:35:04.072: enc1000: setting default backend to 1
** (process:2386): DEBUG: 02:35:04.072: Configuration is valid
** (process:2386): DEBUG: 02:35:04.072: enc1000.1300: setting default backend to 1
** (process:2386): DEBUG: 02:35:04.072: Configuration is valid
DEBUG:enc1000 not found in {}
DEBUG:enc1000.1300 not found in {}
DEBUG:Merged config:
network:
ethernets:
enc1000:
accept-ra: false
dhcp4: false
dhcp6: false
renderer: networkd
version: 2
vlans:
enc1000.1300:
addresses:
- 10.20.103.63/24
id: 1300
link: enc1000
nameservers:
addresses:
- 10.20.0.2
routes:
- to: default
via: 10.20.103.254
affects: | subiquity → ubuntu-z-systems |
tags: | added: installer s390x |
Changed in ubuntu-z-systems: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
Changed in ubuntu-z-systems: | |
assignee: | Skipper Bug Screeners (skipper-screen-team) → nobody |
tags: |
added: installation removed: installer |
Hi 'liwbj',
I see some advanced configurations like openvswitch, special routes, etc.
Usually the installer is supposed to deal with the initial and more basic setup,
and it's recommended to perform further and more advanced configurations after the installation got completed.
So if you follow the steps here: /ubuntu. com/server/ docs/install/ s390x-lpar
https:/
especially the basic network configuration for a VLAN environment - search for "Proceed with the interactive network configuration, here in this case in a VLAN environment"
and then just accept the network config in the subiquity network config screen as it is,
your system should come up after the post-install reboot.
Please could you confirm this?
If that's the case I recommend to create a backup of the existing (basic) netplan yaml file: 00-installer- config. yaml
/etc/netplan/
perform your specific modifications
verify your netplan modifications using 'dryrun':
sudo netplan apply --dryrun
and if no problems are reported, apply it finally with re-running the command, just w/o 'dryrun':
sudo netplan apply
(And yes, always use the latest point release of an Ubuntu LTS, like you did here by using 'ubuntu- 22.04.1- live-server- s390x.iso' .)