[Yahoo-eng-team] [Bug 2008952] Re: DNS failure while trying to fetch user-data

2023-06-09 Thread Dan Bungert
** Changed in: subiquity
   Status: New => Invalid

-- 
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/2008952

Title:
  DNS failure while trying to fetch user-data

Status in cloud-init:
  Fix Released
Status in netplan:
  Invalid
Status in subiquity:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  In testing netboot + autoinstall of the new ubuntu desktop subiquity
  based installer for 23.04 I found cloud-init is failing to retrieve
  user-data because it can't resolved the hostname in the URL.  This
  same configuration does work for 22.04 based subiquity, so seems a
  regression.

  From the ipxe config:

  imgargs vmlinuz initrd=initrd \
   ip=dhcp \
   iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso 
\
   fsck.mode=skip \
   layerfs-path=minimal.standard.live.squashfs \
   autoinstall \
   'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \

  That fails, but if we replace boot.linuxgroove.com with the IP it
  works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 2015605] Re: desktop live installer: cloud-init/ubuntu-desktop-installer network config naming collisions

2023-04-07 Thread Dan Bungert
** Also affects: livecd-rootfs (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/2015605

Title:
  desktop live installer: cloud-init/ubuntu-desktop-installer network
  config naming collisions

Status in cloud-init:
  New
Status in livecd-rootfs package in Ubuntu:
  New

Bug description:
  Seen on live desktop isos build date:
  $ cat /cdrom/.disk/info
  Ubuntu 23.04 "Lunar Lobster" - Dail amd64 (20230407)
  $ snap list ubuntu-desktop-installer
  Name  Version Rev  Tracking Publisher   
Notes
  ubuntu-desktop-installer  0+git.f46d534e  922  latest/stable/…  canonical✓  
classic

  
  Desktop live installer prefers NetworkManager backend for network config due 
to a netplan config file /etc/netplan/01-network-manager.yaml which contains:

  network:
    version: 2
    renderer: NetworkManager

  livecd-rootfs configures cloud-init to write directly to 
/etc/NetworkManager/system-connections when discovering network due to a config 
snippet at
  /etc/cloud/cloud.cfg.d/99-installer-use-networkmanager.cfg which sets 
cloud-init to write directly to /etc/NetworkManager/system-connections with 
this config:
  # Automatically generated by installer build process
  system_info:
    network:
  renderers: ['network-manager']
  activators: ['network-manager']

  -
  This tells cloud-init to write out 
/etc/NetworkManager/system-connections/cloud-init-enp1s0.nmconnection directly.

  Later Ubuntu-desktop-installer(subiquity) starts, it may set network
  config and write it to /etc/netplan/00-installer.yaml and trigger a
  'netplan apply'.

  If there is a non-empty netplan config at this time, subiquity writes
  out /etc/netplan/00-installer.yaml and renames any other existing
  netplan yaml files to /etc/netplan/*.yaml.dist-subiquity.

  Then subiquity(ubuntu-desktop-installer)  invokes netplan apply to
  render all applicable network config to the ephemeral (installer)
  environment.

  When netplan is rendering to `backend: NetworkManager` instead of the
  default networkd and it'll write
  /etc/NetworkManager/netplan-*.nmconnection files with connection names
  scoped under `netplan-`. Cloud-init's rendered connections are scoped
  under `cloudinit-`. This results in a split brain problem where
  cloudinit's configuration and netplan's configuration are not aware of
  each other and netplan isn't aware of any pre-existing
  /etc/NetworkManager artifacts. We then have conflicting nm connections
  being defined and named for the same underlying network interfaces.
  This results in inability to run: nmcli load
  /etc/NetworkManager/system-connections/cloud-init-enp1s0.nmconnection
  with errors such as "unknown connection" or "ipv4.gateway: gateway
  cannot be set if there are no addresses configured"

  Ideally we probably want both cloud-init and subiquity to be
  configuring network in netplan config files so that any merged network
  config is well known by netplan and results in a single source of
  truth for network config.

  This may mean dropping the overrides provided by livecd-roots setting
  cloud-init to render directly to network-manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2015605/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 2014999] Re: curtin in-target sudo copy command fails and crashes installer

2023-04-03 Thread Dan Bungert
Fixing the Affects components, should not be a cloud-init issue.

** Changed in: cloud-init
   Status: New => Invalid

** Also affects: subiquity
   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/2014999

Title:
  curtin in-target sudo copy command fails and crashes installer

Status in cloud-init:
  Invalid
Status in subiquity:
  New
Status in curtin package in Ubuntu:
  New

Bug description:
  full command in cloud-inits user-data late-commands section:
  curtin in-target -- sudo cp /cdrom/cargo/posinst-temp /target/etc/sudoers.d/

  ubuntu 22.04.2 lts
  21.3-0ubuntu1 curtin

  I expected file to be copied

  File wasn't copied.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: curtin (not installed)
  Uname: Linux 5.15.0-67-generic x86_64
  Architecture: amd64
  Date: Sun Apr  2 14:01:44 2023
  ProcEnviron:
   LANG=C.UTF-8
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: curtin

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2014999/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 2008952] Re: DNS failure while trying to fetch user-data

2023-03-24 Thread Dan Bungert
What a mess!

I have uploaded the livecd-rootfs change proposed by Chad in #26.  Note
that there is another problem around jsonschema exposed by this that is
in progress.

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Fix Committed

-- 
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/2008952

Title:
  DNS failure while trying to fetch user-data

Status in cloud-init:
  In Progress
Status in netplan:
  Invalid
Status in subiquity:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New

Bug description:
  In testing netboot + autoinstall of the new ubuntu desktop subiquity
  based installer for 23.04 I found cloud-init is failing to retrieve
  user-data because it can't resolved the hostname in the URL.  This
  same configuration does work for 22.04 based subiquity, so seems a
  regression.

  From the ipxe config:

  imgargs vmlinuz initrd=initrd \
   ip=dhcp \
   iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso 
\
   fsck.mode=skip \
   layerfs-path=minimal.standard.live.squashfs \
   autoinstall \
   'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \

  That fails, but if we replace boot.linuxgroove.com with the IP it
  works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 2008952] Re: DNS failure while trying to fetch user-data

2023-03-07 Thread Dan Bungert
Looking at the desktop ISOs, while the system is configured with Netplan
to use NetworkManager, there seems to be some conflict here where
systemd-networkd is trying to interact with the device.  Some feedback
would be appreciated.  The practical result is that early boot cloud-
init is not able to fetch data that it should be able to retrieve.

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

** Also affects: systemd (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/2008952

Title:
  DNS failure while trying to fetch user-data

Status in cloud-init:
  Triaged
Status in netplan:
  New
Status in subiquity:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In testing netboot + autoinstall of the new ubuntu desktop subiquity
  based installer for 23.04 I found cloud-init is failing to retrieve
  user-data because it can't resolved the hostname in the URL.  This
  same configuration does work for 22.04 based subiquity, so seems a
  regression.

  From the ipxe config:

  imgargs vmlinuz initrd=initrd \
   ip=dhcp \
   iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso 
\
   fsck.mode=skip \
   layerfs-path=minimal.standard.live.squashfs \
   autoinstall \
   'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \

  That fails, but if we replace boot.linuxgroove.com with the IP it
  works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1986781] Re: [Ubuntu 22.04]cloud-init failed to complete after 10 minutes of waiting was shown during Installation via iDRAC Virtual Console

2022-11-28 Thread Dan Bungert
** Also affects: casper (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: casper (Ubuntu Jammy)
   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/1986781

Title:
  [Ubuntu 22.04]cloud-init failed to complete after 10 minutes of
  waiting was shown during Installation via iDRAC Virtual Console

Status in cloud-init:
  Invalid
Status in subiquity:
  Invalid
Status in casper package in Ubuntu:
  Fix Released
Status in casper source package in Focal:
  New
Status in casper source package in Jammy:
  New

Bug description:
  Description:

  On Dell EMC PowerEdge system when Install Ubuntu 22.04 via iDRAC
  Virtual Console, cloud-init failed to complete after 10 minutes of
  waiting.

  Steps to Reproduce:

  1. Login to iDRAC and Launch Virtual Console.
  2. Connect to Virtual Media and Map ubuntu 22.04 iso file using Map CD/DVD 
option.
  3. Try Installing Ubuntu server.
  4. "cloud-init" failed to complete after 10 minutes of waiting was shown 
during Installation.

  Expected Results :-

  Installation should be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1986781/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1986781] Re: [Ubuntu 22.04]cloud-init failed to complete after 10 minutes of waiting was shown during Installation via iDRAC Virtual Console

2022-11-16 Thread Dan Bungert
Hi Narendra - yes, the plan is to have this done in time for 22.04.2.
Thanks for specifically pointing this out, we need to make sure it's
included in the Jammy Stable Release Updates.

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

-- 
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/1986781

Title:
  [Ubuntu 22.04]cloud-init failed to complete after 10 minutes of
  waiting was shown during Installation via iDRAC Virtual Console

Status in cloud-init:
  Invalid
Status in subiquity:
  Invalid
Status in casper package in Ubuntu:
  In Progress

Bug description:
  Description:

  On Dell EMC PowerEdge system when Install Ubuntu 22.04 via iDRAC
  Virtual Console, cloud-init failed to complete after 10 minutes of
  waiting.

  Steps to Reproduce:

  1. Login to iDRAC and Launch Virtual Console.
  2. Connect to Virtual Media and Map ubuntu 22.04 iso file using Map CD/DVD 
option.
  3. Try Installing Ubuntu server.
  4. "cloud-init" failed to complete after 10 minutes of waiting was shown 
during Installation.

  Expected Results :-

  Installation should be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1986781/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1986781] Re: [Ubuntu 22.04]cloud-init failed to complete after 10 minutes of waiting was shown during Installation via iDRAC Virtual Console

2022-11-01 Thread Dan Bungert
We propose no longer having the md5check block multi-user.  I'm opening
a matching MP.

** Also affects: casper (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: casper (Ubuntu)
   Status: New => In Progress

** Changed in: casper (Ubuntu)
   Importance: Undecided => High

** Changed in: casper (Ubuntu)
 Assignee: (unassigned) => Dan Bungert (dbungert)

-- 
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/1986781

Title:
  [Ubuntu 22.04]cloud-init failed to complete after 10 minutes of
  waiting was shown during Installation via iDRAC Virtual Console

Status in cloud-init:
  Invalid
Status in subiquity:
  New
Status in casper package in Ubuntu:
  In Progress

Bug description:
  Description:

  On Dell EMC PowerEdge system when Install Ubuntu 22.04 via iDRAC
  Virtual Console, cloud-init failed to complete after 10 minutes of
  waiting.

  Steps to Reproduce:

  1. Login to iDRAC and Launch Virtual Console.
  2. Connect to Virtual Media and Map ubuntu 22.04 iso file using Map CD/DVD 
option.
  3. Try Installing Ubuntu server.
  4. "cloud-init" failed to complete after 10 minutes of waiting was shown 
during Installation.

  Expected Results :-

  Installation should be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1986781/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1986551] Re: Current kinetic ISO images not installable on s390x

2022-08-25 Thread Dan Bungert
Cloud-init folks, may I get your opinion on this one?


2022-08-16 10:16:29,345 - util.py[WARNING]: failed stage init-local 
   
failed run of stage init-local  
   

   
Traceback (most recent call last):  
   
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 745, in 
status_wrapper 
ret = functor(name, args)   
   
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 411, in 
main_init  
init.apply_network_config(bring_up=bring_up_interfaces) 
   
  File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 937, in 
apply_network_config 
return self.distro.apply_network_config(
   
  File "/usr/lib/python3/dist-packages/cloudinit/distros/__init__.py", line 
244, in apply_network_config   
network_state = parse_net_config_data(netconfig)
   
  File "/usr/lib/python3/dist-packages/cloudinit/net/network_state.py", line 
1062, in parse_net_config_data
nsi.parse_config(skip_broken=skip_broken)   
   
  File "/usr/lib/python3/dist-packages/cloudinit/net/network_state.py", line 
280, in parse_config  
self.parse_config_v2(skip_broken=skip_broken)   
   
  File "/usr/lib/python3/dist-packages/cloudinit/net/network_state.py", line 
330, in parse_config_v2   
self._v2_common(command)
   
  File "/usr/lib/python3/dist-packages/cloudinit/net/network_state.py", line 
785, in _v2_common
real_if_name = find_interface_name_from_mac(mac_address)
   
  File "/usr/lib/python3/dist-packages/cloudinit/net/__init__.py", line 933, in 
find_interface_name_from_mac   
if mac.lower() == interface_mac.lower():
   
AttributeError: 'NoneType' object has no attribute 'lower'  
   

   
Cloud-init v. 22.2-115-g6e498773-0ubuntu1~22.10.1 running 'init' at Tue, 16 Aug 
2022 10:16:29 +. Up 226.22 seconds.
ci-info: ++Net device 
info+++  
ci-info: 
+--+---+--+---++---+
  
ci-info: |Device|   Up  |   Address|  Mask 
| Scope  | Hw-Address|  
ci-info: 
+--+---+--+---++---+
  
ci-info: |   encc000|  True | fe80::4433:4bff:fea2:146b/64 |   .   
|  link  | f6:4c:f0:f1:ea:27 |  
ci-info: | encc000.2653 |  True |10.245.236.14 | 255.255.255.0 
| global | f6:4c:f0:f1:ea:27 |  
ci-info: | encc000.2653 |  True | fe80::4433:4bff:fea2:146b/64 |   .   
|  link  | f6:4c:f0:f1:ea:27 |  
ci-info: |ens298| False |  .   |   .   
|   .| 82:0d:2d:0c:b8:70 |  
ci-info: |   ens298d1   | False |  .   |   .   
|   .| 82:0d:2d:0c:b8:71 |  
ci-info: |ens314| False |  .   |   .   
|   .| 82:0d:2d:0c:b7:00 |  
ci-info: |   ens314d1   | False |  .   |   .   
|   .| 82:0d:2d:0c:b7:01 |  
ci-info: |  lo  |  True |  127.0.0.1   |   255.0.0.0   
|  host  | . |  
ci-info: |  lo  |  True |   ::1/128|   .   
|  host  | . |  


** Also affects: cloud-init
   

[Yahoo-eng-team] [Bug 1937319] Re: namespace collision on url kernel arg results in downloading iso multiple times

2021-07-23 Thread Dan Bungert
** Also affects: casper (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/1937319

Title:
  namespace collision on url kernel arg results in downloading iso
  multiple times

Status in cloud-init:
  Triaged
Status in casper package in Ubuntu:
  New

Bug description:
  As listed at https://discourse.ubuntu.com/t/netbooting-the-live-
  server-installer/14510/135

  When attempting a netboot, we can end up in a situation where cloud-
  init downloads a full iso, only to decide that the first few bytes
  aren't the expected header and to ignore it.

  I suggest an enhancement where a small amount of data is downloaded at
  first, we check this data for the required #cloud-config, and then use
  that info to decide to continue to download the file or not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1937319/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1937319] [NEW] cloud-init can attempt to download an iso from kernel arg url

2021-07-22 Thread Dan Bungert
Public bug reported:

As listed at https://discourse.ubuntu.com/t/netbooting-the-live-server-
installer/14510/135

When attempting a netboot, we can end up in a situation where cloud-init
downloads a full iso, only to decide that the first few bytes aren't the
expected header and to ignore it.

I suggest an enhancement where a small amount of data is downloaded at
first, we check this data for the required #cloud-config, and then use
that info to decide to continue to download the file or not.

** Affects: cloud-init
 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/1937319

Title:
  cloud-init can attempt to download an iso from kernel arg url

Status in cloud-init:
  New

Bug description:
  As listed at https://discourse.ubuntu.com/t/netbooting-the-live-
  server-installer/14510/135

  When attempting a netboot, we can end up in a situation where cloud-
  init downloads a full iso, only to decide that the first few bytes
  aren't the expected header and to ignore it.

  I suggest an enhancement where a small amount of data is downloaded at
  first, we check this data for the required #cloud-config, and then use
  that info to decide to continue to download the file or not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1937319/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp