[Yahoo-eng-team] [Bug 1868246] Re: No network after subiquity LPAR installation on s390x with VLAN

2020-04-14 Thread Michael Hudson-Doyle
** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1868246 Title: No network after subiquity LPAR installation

[Yahoo-eng-team] [Bug 1868246] Re: No network after subiquity LPAR installation on s390x with VLAN

2020-04-08 Thread Dimitri John Ledkov
and one more typo ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1868246 Title: No network

[Yahoo-eng-team] [Bug 1868246] Re: No network after subiquity LPAR installation on s390x with VLAN

2020-04-07 Thread Dimitri John Ledkov
When using today's ISO, with only a single disk drive attached, and snap refreshed from edge channel, one should be able to complete the install with networking not getting interrupted, and correctly have networking in the target too. ** Changed in: ubuntu-z-systems Status: New => Fix

[Yahoo-eng-team] [Bug 1868246] Re: No network after subiquity LPAR installation on s390x with VLAN

2020-03-26 Thread Dimitri John Ledkov
1) cloud-init should be fixed for /run/netplan/* which is another bug 2) this bug is about subiquity not deleting/tearing down critical connections ** This bug is no longer a duplicate of bug 1861460 cloud-init should parse initramfs rendered netplan if present ** Changed in: cloud-init

[Yahoo-eng-team] [Bug 1868246] Re: No network after subiquity LPAR installation on s390x with VLAN

2020-03-20 Thread Frank Heimes
Some additional information: Early in the subiquity installation process (right after disk device enablement) I can see two files in /etc/netplan/: 00-installer-config.yaml 50-cloud-init.yaml.dist-subiquity I think both are not as they should be for this VLAN environment.