Comment 7 for bug 1996007

Hi liwbj,
that looks all good - your system got and installed the updates during the installation.
netplan package version is correct and also all the log messages are reasonable (from comment #5: some facilities are not reachable, probably because your proxy does not allow them, which is fine; from comment #6: there is a seeding ongoing that needs to be completed, also normal, if it occurs it takes a just while).

I just did an interactive 22.04.1 installation on our z15 (actually a L1III) that is a DPM system (but I don't know which version, where can I find it? Haven't seen it in 'System Information') and it booted nicely after the install and I could immediately login from remote afterwards, hence the netplan was properly applied.

So I am not able to recreate your case...

Just a few things to double check (and please be careful, because by coincidence my OSA device address is '1300', which is in your case the same as your VLAN Id).

How is your OSA device configured in DPM?
(mine is configured like shown in the attached screenshot).

Have you specified your OSA address at the 'zdev to activate' step (here my '1300'):
--------%<----------------%<----------------%<----------------%<--------
Attempt interactive netboot from a URL?
yes no (default yes):
yes
Available qeth devices:
lszdev: No device was selected!

zdev to activate (comma separated, optional):
1300
[ 114.051390] lcs: Loading LCS driver
A manual update of the initial RAM-disk is required.
QETH device 0.0.1300:0.0.1301:0.0.1302 configured
Note: The initial RAM-disk must be updated for these changes to take effect:
       - QETH device 0.0.1300:0.0.1301:0.0.1302
Two methods available for IP configuration:
  * static: for static IP configuration
  * dhcp: for automatic IP configuration
static dhcp (default 'dhcp'):
--------%<----------------%<----------------%<----------------%<--------
(That is just out of curiosity, since devices are on DPM systems usually auto-enabled).

Was your OSA device listed at the zdev screen, like this:

--------%<----------------%<----------------%<----------------%<--------
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
  Zdev setup [ Help ]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
  ID ONLINE NAMES

  qeth
  0.0.1300:0.0.1301:0.0.1302 auto enc1300 ▸

                                 [ Continue ]
                                 [ Back ]

--------%<----------------%<----------------%<----------------%<-------
(Btw. there is nothing you need to do at that screen - since we are on a DPM system.)

And where your interfaces properly listed at the network connections screen ?

--------%<----------------%<----------------%<----------------%<--------
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
  Network connections [ Help ]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
  Configure at least one interface this server can use to talk to other
  machines, and which preferably provides sufficient access for updates.

  [ enc1300 eth - ▸ ] ▴
    2e:3a:cd:8d:cd:ef / Unknown Vendor / Unknown Model

  [ enc1300.2780 vlan - ▸ ]
    static 10.103.104.105/24
    VLAN 2780 on interface enc1300
                                                                             █
                                 [ Done ]
                                 [ Back ]

--------%<----------------%<----------------%<----------------%<--------
(Again, usually nothing todo, just proceed with 'Done' ...)

If possible it would be good if you can share the entire /var/log folder (+ subfolders), since that will incl. also the installer logs on top (and check if /var/crash is empty, if not share the content, too) - maybe that would provide more details ...