from:"\"smith\""

thank you Mauricio  for the detailed review!

>>It looks like most tests in the requested test_hotplug.py are SKIPPED 
>>(summary below), so I just wanted to confirm:
>> 1) Is that is expected? And

Yes, this skipping is expected on all platforms except for Noble and Ec2
which have a bit more detailed coverage because the platform has better
support for automated testing of these features in our integration
tests. For the sake of brevity in integration testing I wanted to
reference the known integration-test/modules/test_hotplug.py in it's
entirety for all platforms as I know the integration tests automatically
skip inapplicable tests due to extensive skipIf decorators based on the
test platform.

Truly, on most platforms the only test we really cared about validating in that 
integration test module was 
test_hotplug_enabled_by_cmd.

For ec2 though, we have more thorough integration-test support, so we did want 
to see runs of additional tests including: 
test_hotplug_enable_cmd_ec2,  
test_multi_nic_hotplug,test_no_hotplug_triggered_by_docker,  
test_nics_before_config_trigger_hotplug and test_multi_nic_hotplug_vpc



2) Is the level of confidence sufficient, based on `test_hotplug_enable_cmd`, 
which is the test that PASSED in all of azure/ec2/gce and lxd_container/lxd_vm?

Yes this testing is sufficient because we only need to see that the
hotplug.socket/service is working at all because that (plus the full
integration test suite of lxd_vm/lxd_container) confirms no systemd
ordering cycles present preventing cloud-init-hotplug.* services/sockets
from starting and running.

The more detailed ec2 hotplug tests assert hotplug specific behavior in more 
complex hotplug scenarios which is really above and beyond the bug we are 
checking for here. But, since those tests were easy to trigger, I added that to 
coverage matrix for validation. Sorry for the suspect additional data/SKIPs 
which prompted your investigation. But, good question too.
Thank you!

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

updated test-case-1 desktop logs showing all formerly affected systemd
sevices are healthy on first boot

** Attachment added: "test-case-1-desktop-ordering-cycle.log"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2081124/+attachment/5823530/+files/test-case-1-desktop-ordering-cycle.log

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

OEM team would like to expedite SRU aging on this bug now that it is
verified because the affected offerings for  noble use daily image
builds. So, the sooner this fix releases the sooner builds are
unblocked.

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

test-case-1: confirm ordering cycle issues on daily Noble desktop,
confirm fix with noble-propose cloud-init

** Attachment added: "test-case-1-desktop-ordering-cycle.log"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2081124/+attachment/5823529/+files/test-case-1-desktop-ordering-cycle.log

** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

2024-09-27 Thread Chad Smith

Thank you Andreas.

Attached are the logs for all testcases in test case 2. The TLDR is happy 
hotplug tests on ec2, azure, gce and a solid performance improvement in 
bootspeed.log time measurements (across 3 samples):
   - Avg time to ssh:`1.12 seconds faster
   - Avg time to spent in systemd on userspace: 0.5 seconds less
   - Avg time spent on all cloud-init boot stages: 0.17 seconds less 

** Attachment added: "sru-20729224-testcase2.tar"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2081124/+attachment/5822647/+files/sru-20729224-testcase2.tar

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

** Description changed:

[ Impact ]

cloud-init 24.2 shifted the systemd configuration of cloud-init-
hotplugd.socket to earlier in boot before sysinit.target, but still
retained the systemd unit DefaultDependencies. This lead to a systemd
ordering cycle which affects only Ubuntu Live Desktop image on 24.04
(Noble) and 24.10 (Oracular) due to a custom system drop in for cloud-
init.service provided by livecd-rootfs which orders cloud-init.service
After=NetworkManager.service NetworkManager-wait-online.service.

The affected systemd ordering cycle messages are visible in journalctl
-b 0 in either Desktop ephemeral boot or first boot post-installation.

It may result in either cloud-init-hotplug.service,
NetworkManager.service or dbus.socket deleted from the systemd boot
goals resulting in an unresponsive system at first boot.

Without this changeset, Ubuntu Live Desktop launches of ephemeral boot (or
first boot after install) can see "ordering cycle" messages in journalctl -b 0
which leads systemd to kick outany of the following potential conflicting
services:
- cloud-init-hotplugd.service
- NetworkManager.service
- dbus.service

[ Test Plan ]
Validate both desktop and server images do not expose systemd ordering cycle
issues related to hotplug

== Test case 1 (desktop) ==
Download daily noble desktop live image from
https://cdimage.ubuntu.com/daily-live/20240421/

== Test case 2 (server) broad integration test coverage ==
- 1. Run full suite of cloud-init integration tests for lxd_vm and
lxd_container using packages published to noble-proposed pocket:
+ 1. Run full suite of cloud-init integration tests using the
ppa:cloud-init--proposed PPA against lxd_container lxd_vm
+ CLOUD_INIT_PLATFORM=lxd_vm CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED
CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests

- $ for platform in lxd_vm lxd_container; do
- CLOUD_INIT_PLATFORM=$platform CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED
CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests
- done
+ CLOUD_INIT_PLATFORM=lxd_container CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED

- 2. Run hotplug specific integration tests against ec2 and azure:
- for platform in ec2 azure; do
+ 2. Run hotplug specific integration tests against ec2 and azure
+ CLOUD_INIT_PLATFORM=ec2 CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED
CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests --
tests/integration_tests/modules/test_hotplug.py

- $ CLOUD_INIT_PLATFORM=$platform CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED
CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests --
tests/integration_tests/modules/test_hotplug.py
- done
+ CLOUD_INIT_PLATFORM=azure CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED
+ CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests --
+ tests/integration_tests/modules/test_hotplug.py
+
+ 3. validate no negative impacts to boot speed
+ Leverage https://github.com/canonical/server-test-scripts/pull/201 to get
qemu-kvm samples of before/after this changeset to ensure boot speed is not
negatively impacted.

[ Where problems can occur ]

* This upload is a direct resolution of where problems could occur. If
there are systemd ordering cycles introduced by new systemd units or
services, systemd may punt conflicting services out of boot goals for
the system. If critical services are deleted from boot goals, the
system, and affected services will not be brought up and configured as
anticipated. This leads to misconfigured, unconfigured or inaccessible
systems. The good news is that the symptom of systemd ordering cycles is
easily detected during systemd generator timeframe and systemd leaves
logs in journalctl about any affected serv

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

** Description changed:

  [ Impact ]
  
  cloud-init 24.2 shifted the systemd configuration of cloud-init-
  hotplugd.socket to earlier in boot before sysinit.target, but still
  retained the systemd unit DefaultDependencies. This lead to a systemd
  ordering cycle which affects only Ubuntu Live Desktop image on 24.04
  (Noble) and 24.10 (Oracular) due to a custom system drop in for cloud-
  init.service provided by livecd-rootfs which orders cloud-init.service
  After=NetworkManager.service NetworkManager-wait-online.service.
  
  The affected systemd ordering cycle messages are visible in journalctl
  -b 0 in either Desktop ephemeral boot or first boot post-installation.
  
  It may result in either cloud-init-hotplug.service,
  NetworkManager.service or dbus.socket deleted from the systemd boot
  goals resulting in an unresponsive system at first boot.
  
  Without this changeset, Ubuntu Live Desktop launches of ephemeral boot (or 
first boot after install) can see "ordering cycle" messages in journalctl -b 0 
which leads systemd to kick outany of the following potential conflicting 
services:
  - cloud-init-hotplugd.service
  - NetworkManager.service
  - dbus.service
  
  [ Test Plan ]
  Validate both desktop and server images do not expose systemd ordering cycle 
issues related to hotplug
  
  == Test  case 1 (desktop) ==
  Download daily noble desktop live image from 
https://cdimage.ubuntu.com/daily-live/20240421/
  
  1.Launch in virt-manager or qemu-kvm.
  2. Bring up a gnome terminal during ephemeral boot before responding to any 
configuration prompts Alt-Ctrl-T
  3. Confirm ordering cycle issues: journalctl -b 0 | grep "ordering cycle"
  4. Shutdown daily failing image
  5. Follow 
https://help.ubuntu.com/community/LiveCDCustomization#Amending_the_LiveCD_Squash_Files_System
 to update cloud-init from -proposed in this daily Live Desktop ISO, creating a 
new desktop-noble-cloud-init-proposed.iso
  6. Launch in virt-manager or qemu-kvm
  7. Confirm ordering cycle is resolved: journalctl -b 0 | grep "ordering cycle"
  8. Confirm all affected services are healthy
  for service_name in NetworkManager.service dbus.service 
cloud-init-hotplugd.socket cloud-init-hotplugd.service; do
   systemctl status $service_name
  done
  9. Complete live installer prompts and reboot into "first boot"
  10. Login and confirm no ordering cycles on first boot: Atl-Ctrl-T: 
journalctl -b 0 | grep "ordering cycle"
  11. Assert previously affected services are healthy:
  for service_name in NetworkManager.service dbus.service 
cloud-init-hotplugd.socket cloud-init-hotplugd.service; do
   systemctl status $service_name
  done
  12. Assert cloud-init is healthy: cloud-init status --format=yaml
  
+ == Test  case 2 (server)  broad integration test coverage ==
+ 1. Run full suite of cloud-init integration tests for lxd_vm and 
lxd_container using packages published to noble-proposed pocket:
  
- == Test  case 2 (server)  broad integration test coverage ==
- 1. Run full suite of cloud-init integration tests using the 
ppa:cloud-init--proposed PPA against lxd_container lxd_vm 
- CLOUD_INIT_PLATFORM=lxd_vm CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED 
CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests
+ $ for platform in lxd_vm lxd_container; do 
+ CLOUD_INIT_PLATFORM=$platform CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED 
CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests
+ done
  
- CLOUD_INIT_PLATFORM=lxd_container CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED
+ 2. Run hotplug specific integration tests against ec2 and azure:
+ for platform in ec2 azure; do
  
- 
- 2. Run hotplug specific integration tests against ec2 and azure
- CLOUD_INIT_PLATFORM=ec2 CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED 
CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests -- 
tests/integration_tests/modules/test_hotplug.py
- 
- CLOUD_INIT_PLATFORM=azure CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED
- CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests --
- tests/integration_tests/modules/test_hotplug.py
- 
+ $ CLOUD_INIT_PLATFORM=$platform CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED 
CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests -- 
tests/integration_tests/modules/test_hotplug.py
+ done
  
  [ Where problems can occur ]
  
   * This upload is a direct resolution of where problems could occur. If
  there are systemd ordering cycles introduced by new systemd units or
  services, systemd may punt conflicting services out of boot goals for
  the system. If critical services are deleted from boot goals, the
  system, and affected services will not be brought up and configured as
  anticipated. This leads to misconfigured, unconfigured or inaccessible
  systems. The good news is that the symptom of systemd ordering cycles is
  easily detected during systemd generator timeframe and systemd leaves
  logs in journalctl about any affected services when this occurs.
  
  [ Other Info ]
  
  This bug in systemd ordering was not seen in Oracular Live images
  originally because of a separate bug:

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

** Description changed:

[ Impact ]

The affected systemd ordering cycle messages are visible in journalctl
-b 0 in either Desktop ephemeral boot or first boot post-installation.

It may result in either cloud-init-hotplug.service,
NetworkManager.service or dbus.socket deleted from the systemd boot
goals resulting in an unresponsive system at first boot.

[ Test Plan ]
+ Validate both desktop and server images do not expose systemd ordering cycle
issues related to hotplug

- Download daily noble desktop live image from
- https://cdimage.ubuntu.com/daily-live/20240421/
+ == Test case 1 (desktop) ==
+ Download daily noble desktop live image from
https://cdimage.ubuntu.com/daily-live/20240421/

1.Launch in virt-manager or qemu-kvm.
2. Bring up a gnome terminal during ephemeral boot before responding to any
configuration prompts Alt-Ctrl-T
3. Confirm ordering cycle issues: journalctl -b 0 | grep "ordering cycle"
4. Shutdown daily failing image
5. Follow
https://help.ubuntu.com/community/LiveCDCustomization#Amending_the_LiveCD_Squash_Files_System
to update cloud-init from -proposed in this daily Live Desktop ISO, creating a
new desktop-noble-cloud-init-proposed.iso
6. Launch in virt-manager or qemu-kvm
7. Confirm ordering cycle is resolved: journalctl -b 0 | grep "ordering cycle"
8. Confirm all affected services are healthy
for service_name in NetworkManager.service dbus.service
cloud-init-hotplugd.socket cloud-init-hotplugd.service; do
systemctl status $service_name
done
9. Complete live installer prompts and reboot into "first boot"
10. Login and confirm no ordering cycles on first boot: Atl-Ctrl-T:
journalctl -b 0 | grep "ordering cycle"
11. Assert previously affected services are healthy:
for service_name in NetworkManager.service dbus.service
cloud-init-hotplugd.socket cloud-init-hotplugd.service; do
systemctl status $service_name
done
12. Assert cloud-init is healthy: cloud-init status --format=yaml
+
+
+ == Test case 2 (server) broad integration test coverage ==
+ 1. Run full suite of cloud-init integration tests using the
ppa:cloud-init--proposed PPA against lxd_container lxd_vm
+ CLOUD_INIT_PLATFORM=lxd_vm CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED
CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests
+
+ CLOUD_INIT_PLATFORM=lxd_container CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED
+
+
+ 2. Run hotplug specific integration tests against ec2 and azure
+ CLOUD_INIT_PLATFORM=ec2 CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED
CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests --
tests/integration_tests/modules/test_hotplug.py
+
+ CLOUD_INIT_PLATFORM=azure CLOUD_INIT_CLOUD_INIT_SOURCE=PROPOSED
+ CLOUD_INIT_OS_IMAGE=noble tox -e integration-tests --
+ tests/integration_tests/modules/test_hotplug.py

[ Where problems can occur ]

[ Other Info ]

This bug in systemd ordering was not seen in Oracular Live images
originally because of a separate bug:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2081325
where Desktop image overrides were not being applied to cloud-init-
network.service (Oracular only). So Oracular did not surface this
systemd ordering cycle issue. The livecd-rootfs bug has been accepted
into Oracular Sept 23rd, so that release would have also exhibited this
broken behavior if the resulting fix from cloud-init was not also was
accepted to Oracular Sept 23rd as well.

[ Original Description ]
We got errors that some services like snapd and NetworkM

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

Note that https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/2079224 just cleared SRU. So, this bug should be able to
progress for review into noble-proposed for verification.

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2079224] Re: sru cloud-init (24.3.1 update) focal, jammy and noble

2024-09-24 Thread Chad Smith

** Tags removed: verification-needed verification-needed-focal 
verification-needed-jammy verification-needed-noble
** Tags added: verification-done verification-done-focal 
verification-done-jammy verification-done-noble

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

Title:
  sru cloud-init (24.3.1 update) focal, jammy and noble

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


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

2024-09-23 Thread Chad Smith

** Description changed:

- We got errors that some services like snapd and NetworkManager is not
- started when running cloud-init or desktop, excerpt from journal below:
+ [ Impact ]
+ 
+ cloud-init 24.2 shifted the systemd configuration of cloud-init-
+ hotplugd.socket to earlier in boot before sysinit.target, but still
+ retained the systemd unit DefaultDependencies. This lead to a systemd
+ ordering cycle which affects only Ubuntu Live Desktop image on 24.04
+ (Noble) and 24.10 (Oracular) due to a custom system drop in for cloud-
+ init.service provided by livecd-rootfs which orders cloud-init.service
+ After=NetworkManager.service NetworkManager-wait-online.service.
+ 
+ The affected systemd ordering cycle messages are visible in journalctl
+ -b 0 in either Desktop ephemeral boot or first boot post-installation.
+ 
+ It may result in either cloud-init-hotplug.service,
+ NetworkManager.service or dbus.socket deleted from the systemd boot
+ goals resulting in an unresponsive system at first boot.
+ 
+ Without this changeset, Ubuntu Live Desktop launches of ephemeral boot (or 
first boot after install) can see "ordering cycle" messages in journalctl -b 0 
which leads systemd to kick outany of the following potential conflicting 
services:
+ - cloud-init-hotplugd.service
+ - NetworkManager.service
+ - dbus.service
+ 
+ 
+ [ Test Plan ]
+ 
+ Download daily noble desktop live image from
+ https://cdimage.ubuntu.com/daily-live/20240421/
+ 
+ 1.Launch in virt-manager or qemu-kvm.
+ 2. Bring up a gnome terminal during ephemeral boot before responding to any 
configuration prompts Alt-Ctrl-T
+ 3. Confirm ordering cycle issues: journalctl -b 0 | grep "ordering cycle"
+ 4. Shutdown daily failing image
+ 5. Follow 
https://help.ubuntu.com/community/LiveCDCustomization#Amending_the_LiveCD_Squash_Files_System
 to update cloud-init from -proposed in this daily Live Desktop ISO, creating a 
new desktop-noble-cloud-init-proposed.iso
+ 6. Launch in virt-manager or qemu-kvm
+ 7. Confirm ordering cycle is resolved: journalctl -b 0 | grep "ordering cycle"
+ 8. Confirm all affected services are healthy
+ for service_name in NetworkManager.service dbus.service 
cloud-init-hotplugd.socket cloud-init-hotplugd.service; do
+  systemctl status $service_name
+ done
+ 
+ [ Where problems could occur ]
+ 
+  * This upload is a direct resolution of where problems could occur. If
+ there are systemd ordering cycles introduced by new systemd units or
+ services, systemd may punt conflicting services out of boot goals for
+ the system. If critical services are deleted from boot goals, the
+ system, and affected services will not be brought up and configured as
+ anticipated. This leads to misconfigured, unconfigured or inaccessible
+ systems. The good news is that the symptom of systemd ordering cycles is
+ easily detected during systemd generator timeframe and systemd leaves
+ logs in journalctl about any affected services when this occurs.
+ 
+ [ Other Info ]
+ 
+ This bug in systemd ordering was not seen in Oracular Live images
+ originally because of a separate bug:
+ https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2081325
+ where Desktop image overrides were not being applied to cloud-init-
+ network.service (Oracular only). So Oracular did not surface this
+ systemd ordering cycle issue. The livecd-rootfs bug has been accepted
+ into Oracular Sept 23rd, so that release would have also exhibited this
+ broken behavior if the resulting fix from cloud-init was not also was
+ accepted to Oracular Sept 23rd as well.
+ 
+ 
+ [ Original Description ]
+ We got errors that some services like snapd and NetworkManager is not started 
when running cloud-init or desktop, excerpt from journal below:
  
  Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found 
ordering cycle on NetworkManager-wait-online.service/start
  Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found 
dependency on basic.target/start
  Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found 
dependency on sockets.target/start
  Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found 
dependency on cloud-init-hotplugd.socket/start
  Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found 
dependency on cloud-config.target/start
  Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found 
dependency on cloud-init.service/start
  Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Job 
NetworkManager-wait-online.service/start deleted to break ordering cycle 
starting with cloud-init.service/start
  Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: 
Found ordering cycle on dbus.service/start
  Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: 
Found dependency on basic.target/start
  Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: 
Found dependency on soc

[Bug 2079224] Re: sru cloud-init (24.3.1 update) focal, jammy and noble

2024-09-23 Thread Chad Smith

supplemental successful retries and known upstream bug on lxd_vm focal

** Attachment added: "lxd_vm-focal-retries.log"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2079224/+attachment/5821235/+files/lxd_vm-focal-retries.log

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

Title:
  sru cloud-init (24.3.1 update) focal, jammy and noble

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


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

2024-09-23 Thread Chad Smith

Note that this upload for Noble is queued 
https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=cloud-init 
and sitting behind the active SRU 24.3.1 to Noble.
The SRU process bug https://bugs.launchpad.net/bugs/2079224 is just awaiting 
partner verification feedback on that SRU to publish to Focal, Jammy and Noble. 
All verification performed by canonical is done on that SRU. Once published, 
this fix can be reviewed and allowed into -proposed 

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

** Also affects: cloud-init (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu Noble)
   Status: New => Invalid

** Changed in: cloud-init (Ubuntu Noble)
   Status: New => Fix Committed

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2079224] Re: sru cloud-init (24.3.1 update) focal, jammy and noble

2024-09-22 Thread Chad Smith

Curtin SRU logs success

** Attachment added: "sru-curtin-24.1.3.log"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2079224/+attachment/5820909/+files/sru-curtin-24.1.3.log

** Description changed:

  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:
  
    - Add AOSC linux distribution support (#5310)
    - Add OpenEuler support for cc_spacewalk module (#5530)
    - Add network-config seed support for nocloud datasource (#5566)
    - Support remote URI sources write_files module (#5505)
    - Add trace-level logger (#5414)
    - optimization: eliminate redundant config reads across boot stages 
(https://github.com/canonical/cloud-init/issues/5536)
    - provide option to set empty passwords and fix password unlock when
  lock_passwd: False on Alpine/FreeBSD/OpenBSD/DragonflyBSD 
(https://github.com/canonical/cloud-init/issues/5355)
  
  Bug fixes:
    - NetworkManager network v1 rendering of config ensure bond- prefix
    - collect-logs avoid inclusion of sensitive data updated apport integration
    - WSL support multi-part MIME config parts as well as landscape tags for
  provisioning (https://github.com/canonical/cloud-init/issues/5460, 
https://github.com/canonical/cloud-init/issues/5538)
    - avoid snap refresh on package_upgrade: true when snap refresh is held 
(https://github.com/canonical/cloud-init/issues/5290)
    - fix(netops): fix ip addr flush command (#5651) (GH: 
https://github.com/canonical/cloud-init/issues/5648)
  
  Package patch reverts of upstream breaking changes to retain original 
behavior:
    - Avoid introducing single-process systemd unit cloud-init-main.service
    - deprecation version boundary to indicate cloud-init package downstream 
version before which 'deprecation' logs are treated only as debug logs
    - avoid attempting to read network-config in NoCloud datasource via 
nocloud.read_seeded utility to avoid speed impacts while retrying a file which 
may not be there.
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates
  
  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug.  cloud-init team
  members will not mark ‘verification-done’ until this has happened.
  
  * Automated Test Results
  DONE: LXD_CONTAINER attach automated cloud-init-proposed test artifacts from 
tests for each release with sru-24.3.1.tar
  DONE: attach automated cloud-init-proposed test artifacts from tests for each 
release with LXD_VM  artifacts with sru-24.3.1.tar
- 
+ DONE: attach automated curtin vmtest with cloud-init proposed>
  DONE: attach Solutions Testing team test results for each LTS. (Approval 
message in comments
  
  * Manual Test Results
  DONE: attach manual cloud-init-proposed test artifacts from tests for each 
release on ec2 datasource with sru-24.3.1.tar
  DONE: attach manual cloud-init-proposed test artifacts from tests for each 
release on gce datasource with sru-24.3.1.tar
  DONE: attach manual cloud-init-proposed test artifacts from tests for each 
release on azure datasource with sru-24.3.1.tar
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.
  
  [Discussion]
  
  [Changelog]
   - docs: Clarify v2 set-name behavior (#5639)
   - fix: properly handle blank lines in fstab (#5643)
   - fix: cc_user_groups incorrectly assumes "useradd" never locks password
     field (#5355) [dermotbradley]
   - tests: assert cloud-init user-data cert is the only root cert (#5641)
   - feat: add automation for ubuntu/* branches asserting quilt patches apply
     (#5622)
   - fix(sources/wsl): no error with empty .cloud-init dir (SC-1862) (#5633)
   - feat(azure): add PPS support for azure-proxy-agent (#5601)
     [Ksenija Stanojevic]
   - fix(tests): use instance.clean/restart instead of clean --reboot (#5636)
   - test: fix cmd/test_schema int test (#5629)
   - test: fix test_honor_cloud_dir int test (#5627)
   - docs: alphabetize dsname lookup table. update comment to create the csv
     (#5624)
   - docs: new datasources should update reference/ds_dsname_map (#5624)
   - test: fix ca_certs int test (#5626)
   - chore: update schema docs to use RST bold for config key names (#5562)
   - fix(doc): italics around deprecation prefix, description bolds key names
     (#5562)
   - feat(doc): add env vars to debug config module doc builds (#5562)
   - fix(doc): doc of nested objects under JSON schema items.oneOf (#5562)
   - fix(doc): object type check if patternProperties or properties (#5562)
   - doc(schema): schema descriptions should end with trailing stop (#5562)
   - fix(wsl): Properly assemble mu

[Bug 2079224] Re: sru cloud-init (24.3.1 update) focal, jammy and noble

SRU successful verification logs and test retries for EC2, GCE, Azure,
lxd_vm, lxd_container on Focal, Jammy and Noble.

** Attachment added: "sru-24.3.1.tar"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2079224/+attachment/582/+files/sru-24.3.1.tar

** Description changed:

  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:
  
    - Add AOSC linux distribution support (#5310)
    - Add OpenEuler support for cc_spacewalk module (#5530)
    - Add network-config seed support for nocloud datasource (#5566)
    - Support remote URI sources write_files module (#5505)
    - Add trace-level logger (#5414)
    - optimization: eliminate redundant config reads across boot stages 
(https://github.com/canonical/cloud-init/issues/5536)
    - provide option to set empty passwords and fix password unlock when
  lock_passwd: False on Alpine/FreeBSD/OpenBSD/DragonflyBSD 
(https://github.com/canonical/cloud-init/issues/5355)
  
  Bug fixes:
    - NetworkManager network v1 rendering of config ensure bond- prefix
    - collect-logs avoid inclusion of sensitive data updated apport integration
    - WSL support multi-part MIME config parts as well as landscape tags for
  provisioning (https://github.com/canonical/cloud-init/issues/5460, 
https://github.com/canonical/cloud-init/issues/5538)
    - avoid snap refresh on package_upgrade: true when snap refresh is held 
(https://github.com/canonical/cloud-init/issues/5290)
-   - fix(netops): fix ip addr flush command (#5651) (GH: 
https://github.com/canonical/cloud-init/issues/5648)
- 
+   - fix(netops): fix ip addr flush command (#5651) (GH: 
https://github.com/canonical/cloud-init/issues/5648)
  
  Package patch reverts of upstream breaking changes to retain original 
behavior:
-   - Avoid introducing single-process systemd unit cloud-init-main.service
-   - deprecation version boundary to indicate cloud-init package downstream 
version before which 'deprecation' logs are treated only as debug logs
-   - avoid attempting to read network-config in NoCloud datasource via 
nocloud.read_seeded utility to avoid speed impacts while retrying a file which 
may not be there.
- 
+   - Avoid introducing single-process systemd unit cloud-init-main.service
+   - deprecation version boundary to indicate cloud-init package downstream 
version before which 'deprecation' logs are treated only as debug logs
+   - avoid attempting to read network-config in NoCloud datasource via 
nocloud.read_seeded utility to avoid speed impacts while retrying a file which 
may not be there.
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates
  
  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug.  cloud-init team
  members will not mark ‘verification-done’ until this has happened.
  
  * Automated Test Results
- 
- 
+ DONE: LXD_CONTAINER attach automated cloud-init-proposed test artifacts from 
tests for each release with sru-24.3.1.tar
+ DONE: attach automated cloud-init-proposed test artifacts from tests for each 
release with LXD_VM  artifacts with sru-24.3.1.tar
  
- 
+ DONE: attach Solutions Testing team test results for each LTS. (Approval 
message in comments
  
  * Manual Test Results
- 
- 
- 
+ DONE: attach manual cloud-init-proposed test artifacts from tests for each 
release on ec2 datasource with sru-24.3.1.tar
+ DONE: attach manual cloud-init-proposed test artifacts from tests for each 
release on gce datasource with sru-24.3.1.tar
+ DONE: attach manual cloud-init-proposed test artifacts from tests for each 
release on azure datasource with sru-24.3.1.tar
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.
  
  [Discussion]
- 
  
  [Changelog]
   - docs: Clarify v2 set-name behavior (#5639)
   - fix: properly handle blank lines in fstab (#5643)
   - fix: cc_user_groups incorrectly assumes "useradd" never locks password
     field (#5355) [dermotbradley]
   - tests: assert cloud-init user-data cert is the only root cert (#5641)
   - feat: add automation for ubuntu/* branches asserting quilt patches apply
     (#5622)
   - fix(sources/wsl): no error with empty .cloud-init dir (SC-1862) (#5633)
   - feat(azure): add PPS support for azure-proxy-agent (#5601)
     [Ksenija Stanojevic]
   - fix(tests): use instance.clean/restart instead of clean --reboot (#5636)
   - test: fix cmd/test_schema int test (#5629)
   - test: fix test_honor_cloud_dir int test (#5627)
   - docs: alphabetize dsname lookup table. update comment to create the csv
     (#5624)
   - docs: new datasources should update reference/ds_dsname_m

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

** Changed in: cloud-init (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

This particular bug is not applicable for livecd-rootfs, as this is a 
cloud-init systemd ordering issue.
There is a separate livecd-rootfs bug and fix for Oracular only 
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2081325 which is 
already queued for oracular-proposed

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

Fix uploaded to Ubuntu Oracular as 24.4~3+really24.3.1-0ubuntu4

(blocked per Beta freeze)
https://launchpad.net/ubuntu/oracular/+queue?queue_state=1&queue_text=cloud-
init


Fix uploaded as well to the unapproved queue for SRU as version 
24.3.1-0ubuntu0~24.04.2  it is queued behind current SRU of cloud-init 
24.3.1-0ubuntu0~24.04.1 to Noble that which should have verification logs 
complete Monday of next week.
https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=cloud-init

** Changed in: cloud-init (Ubuntu)
   Status: New => In Progress

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

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

Thanks Alberto!
Upstream cloud-init fix landed per 
https://github.com/canonical/cloud-init/pull/5722.

Related to this bug is an Oracular Desktop livecd-rootfs update which is
needed due to cloud-init.service being renamed to cloud-init-
network.service.

https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2081325.

This livecd-rootfs fix in 2081325 was merged today and I presume
uploaded to Oracular as well.

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081325] Re: Oracular: systemd override file not applied due to systemd unit rename cloud-init.service renamed to cloud-init-network.service in cloud-init v. 24.3.1

** Changed in: livecd-rootfs (Ubuntu Oracular)
   Status: In Progress => Fix Committed

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

Title:
  Oracular: systemd override file not applied due to systemd unit rename
  cloud-init.service renamed to cloud-init-network.service in cloud-init
  v. 24.3.1

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


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

[Bug 2081325] Re: Oracular: systemd override file not applied due to systemd unit rename cloud-init.service renamed to cloud-init-network.service in cloud-init v. 24.3.1

Marking cloud-init task as won't fix as this is something needed in
livecd-rootfs overrides/dropins.

** Changed in: cloud-init (Ubuntu Oracular)
   Status: New => In Progress

** Changed in: cloud-init (Ubuntu Oracular)
 Assignee: (unassigned) => Chad Smith (chad.smith)

** Changed in: livecd-rootfs (Ubuntu Oracular)
   Status: Confirmed => Won't Fix

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

Title:
  Oracular: systemd override file not applied due to systemd unit rename
  cloud-init.service renamed to cloud-init-network.service in cloud-init
  v. 24.3.1

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


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

Tagging this rls-oo-incoming as this ordering issue affects Oracular
Desktop images as well.

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Critical

** Tags added: rls-oo-incoming

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081325] Re: Oracular: systemd override file not applied due to systemd unit rename cloud-init.service renamed to cloud-init-network.service in cloud-init v. 24.3.1

Added cloud-init package for oracular just to track this issue for
visibility. The fix needs to be in livecd-rootfs.

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Critical

** Also affects: livecd-rootfs (Ubuntu Oracular)
   Importance: Critical
 Assignee: Chad Smith (chad.smith)
   Status: Confirmed

** Also affects: cloud-init (Ubuntu Oracular)
   Importance: Critical
   Status: New

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

Title:
  Oracular: systemd override file not applied due to systemd unit rename
  cloud-init.service renamed to cloud-init-network.service in cloud-init
  v. 24.3.1

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


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

[Bug 2081325] [NEW] Oracular: systemd override file not applied due to systemd unit rename cloud-init.service renamed to cloud-init-network.service in cloud-init v. 24.3.1

Public bug reported:

I Oracular 24.10, cloud-init 24.3.1 renamed cloud-init.service to cloud-
init-network.service as part of the single-process mode support.  This
is only introduced in Oracular and not applicable to any stable releases
before Oracular.[1]

livecd-rootfs provides complete override for the entire cloud-
init.service in /etc/systemd/system/cloud-init.service to reorder the
service After=NetworkManager.service NetworkManager-wait-online.service
and drop # Before=sysinit.target. This overridden file is completely
ignored in Desktop Oracular images dated 20240916 because the systemd
unit name cloud-init.service doesn't match the new cloud-init-
network.service name. This results in incorrect systemd ordering that
may impact cloud-init's ability to download configuration when kernel
commandline options provide a nocloud seed url that requires DNS
resolution via a kernel commandline
'ds=nocloud;s=http://myresolvablehostname/'.


To fix this issue, livecd-rootfs should be emitting and override file to 
/etc/systemd/system/cloud-init-network.service with the latest content provided 
by cloud-init 24.3.1 in oracular.

** Affects: livecd-rootfs (Ubuntu)
 Importance: Critical
 Assignee: Chad Smith (chad.smith)
 Status: Confirmed


** Tags: rls-oo-incoming

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

Title:
  Oracular: systemd override file not applied due to systemd unit rename
  cloud-init.service renamed to cloud-init-network.service in cloud-init
  v. 24.3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2081325/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

The differences we are seeing between a working Desktop ubuntu image
with /var/log/installer/media-info 202408271 are that cloud-init
published 24.2 via SRU to the newer Noble image


In that SRU was a shift to when cloud-init-hotplugd.socket and cloud-
init-hotplugd.service units are ordered[1]

The change added:
- After=cloud-config.target to cloud-init-hotplugd.socket  to allow starting 
hotplugd.socket earlier
and
- After=cloud-init.target to cloud-init-hotplugd.service  to avoid attempting 
udev NIC hotplug events while cloud-init is still configuring the base instance.


We'll need further investigation tomorrow to determine the ordering cycles we 
are seeingin Desktop images w/ NetworkManager-wait-online.service here, and why 
on first boot the systemd unit being deleted is dbus.service yet in ephemeral 
environment (before first boot) it happens to be cloud-init-hotplugd.service.


[1] https://github.com/canonical/cloud-init/pull/5058

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

ok I'm able to reproduce the ordering cycle in ephemeral boot stage for
cloud-init-hotplug.service on noble images dated 20240916

cloud-init-hotplugd.service/socket may be the symptom tying into this
ordering issue too. Digging a bit more today as they may be a symptom of
the same problem and systemd might just be deleting NetworkManager-wait-
online.service on 'first boot' but it has a slightly different symptom
during ephemeral boot stage of the desktop installer.

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

I have also confirmed that livecd-rootfs doesn't appear to have changed
their "drop-in" of cloud-init.service files
https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live-
build/functions#n1060 so it's unlikely a new cloud-init issue introduced
across an SRU boundary.

This makes me think something has changed in systemd or NetworkManager
units and ordering on Noble recently to cause this recent issue or
something that the OEM environment is installing that is causing this
issue:

From the looks of the var/log/apt/term.log nvidia-kernel-common-550
package seems to be installing a few systemd units

Created symlink 
/etc/systemd/system/systemd-hibernate.service.wants/nvidia-hibernate.service → 
/usr/lib/systemd/system/nvidia-hibernate.service.^M^M
Created symlink 
/etc/systemd/system/systemd-suspend.service.wants/nvidia-resume.service → 
/usr/lib/systemd/system/nvidia-resume.service.^M^M
Created symlink 
/etc/systemd/system/systemd-hibernate.service.wants/nvidia-resume.service → 
/usr/lib/systemd/system/nvidia-resume.service.^M^M
Created symlink 
/etc/systemd/system/systemd-suspend.service.wants/nvidia-suspend.service → 
/usr/lib/systemd/system/nvidia-suspend.service.^M^M



I'm guessing we want to look at those and their ordering (systemctl show -p 
Before,After nvidia-resume.service
and nvidia-suspend.service as that seems to be the only thing outside of stock 
Desktop images that is altering systemd unit boot order

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

From the SOS report issue presents on image with this build-info with
whatever additional OEM config is presented as autoinstall-user-data

Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20240911)


I'm trying to download latest Ubuntu Desktop noble to reproduce this problem 
from live Desktop installer images dated Sept 19th and not seeing the ordering 
cycle issues on stock daily Desktop noble images.

How is this reproducible?


In the meantime, from sos logs I see the following: 

 1. the Desktop installer ephemeral boot stage successfully ran all 4
boot stages (init-local, init, config-modules and config-final) of
cloud-init during init as seen in the sos report's
var/log/installer/cloud-init.log and cloud-init-output.log.  So, this
means no ordering cycle present in initial unaltered Desktop images as
that would have kicked out Network-Manager-wait-online.service or
dbus.service

2. I see ./sos_commands/logs/journalctl_--no-pager which shows the
ordering cycle issues in the first of two boots which ejects Network-
Manager-wait-online and dbus.service from boot goals on the first boot.

3. I'm not seeing those journal entries mentioned in this bug related to
ordering cycles in  var/log/installer/installer-journal.txt in the
installer ephemeral boot stage which means this problem doesn't seem to
affect the unaltered installer environment before "first boot" occurs.

4. Unrelated to this specific bug, we will need a separate bug  as a see
an undetected systemd ordering cycle in the Desktop ephemeral
environment related only to cloud-init-hotplugd.socket in desktop
images:

From var/log/installer/installer-journal.txt:   sockets.target: Job
cloud-init-hotplugd.socket/start deleted to break ordering cycle
starting with sockets.target/start


5. I see some APT package installs in sos report var/log/apt/history.log for 
pkgs for which may or may not have added additional systemd units which could 
contribute to ordering cycle issues if they also add sytemd units and ordering 
dependencies
- Commandline: apt-get install --assume-yes --install-suggests oem-nantou-meta 
desktop-provision-hp
- Commandline: apt install nvidia-driver-550

Do we know of oem-nantou-meta desktop-provision-hp or nvidia-driver-550
deliver systemd units or services?


#4 warrants a separate bug that I shall file after finishing triage on this 
issue cloud-init hotplug support is optional and opt-in and not generally 
involved in the default install and configuration of Desktop or server images 
so this wouldn't be what's breaking OEM installs (but it's a symptom of other 
ordering problems that need attention in Desktop images

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus

Thank your for filing this bug, if possible, please perform the
following to aid in debugging:

1. inform the bug on which Ubuntu release this issue occurs, possibly
the desktop image build date,

2. # get versions of network-manager, systemd and cloud-init
for pkg in cloud-init systemd network-manager; do
dpkg-query -W $pkg
done

3. # run the following to list expected systemd ordering
for service_name in cloud-init.service NetworkManager-wait-online.service  
dbus.service do
   echo   $service_name systemd ordering dependencies
   systemctl show -p -p Requires,Wants,Before,After $service_name
done

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

Title:
  systemd service dependency loop between cloud-init, NetworkManager and
  dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions


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

[Bug 2067660] Re: deprecate ubuntu_advantage config key from user-data in favor of ubuntu_pro

2024-09-18 Thread Chad Smith

** Changed in: cloud-init (Ubuntu Bionic)
   Status: Incomplete => New

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

Title:
  deprecate ubuntu_advantage config key from user-data in favor of
  ubuntu_pro

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


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

[Bug 2002358] Re: Screen turned off after seconds of inactivity, fixed by xset -dpms; bug depending on kernel version?

2024-09-14 Thread Mark Smith

I've noticed on Ubuntu 24.04 this appears to occur due to a mismatch
between how Xorg blanks the screen and the configuration gnome-settings-
daemon applies.

If you go into GSD -> Power -> Screen Blank and set it to "Never", then
go to Privacy & Security -> Blank Screen Delay -> Never, xset q still
reports

Screen Saver: prefer blanking yes, allow exposures: yes, timeout 600
cycle 600.

In other words, changing the configuration in GSD does not actually turn
off the screen saver in Xorg.

However, this issue does not appear to impact Wayland.

I was able to figure this out because my AMD box on Wayland doesn't have
this problem, only my NVidia box on Xorg.


A workaround is setting putting "xset s off" in your .bashrc or .xinitrc, but 
that still means that the configuration in GSD won't actually control your 
screen blank.

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Screen turned off after seconds of inactivity, fixed by xset -dpms;
  bug depending on kernel version?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2002358/+subscriptions


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

[Bug 2080688] Re: oracular: NoCloudNet datasource `seedfrom` URL in /etc/cloud/cloud.cfg.d results in traceback

2024-09-13 Thread Chad Smith

** Tags added: rls-oo-incoming

** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) => Chad Smith (chad.smith)

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

Title:
  oracular: NoCloudNet datasource `seedfrom` URL in
  /etc/cloud/cloud.cfg.d results in traceback

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


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

[Bug 2080688] Re: oracular: NoCloudNet datasource `seedfrom` URL in /etc/cloud/cloud.cfg.d results in traceback

2024-09-13 Thread Chad Smith

Upstream pull request landed  https://github.com/canonical/cloud-
init/pull/5701

** Changed in: cloud-init (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  oracular: NoCloudNet datasource `seedfrom` URL in
  /etc/cloud/cloud.cfg.d results in traceback

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


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

[Bug 2080688] [NEW] oracular: NoCloudNet datasource `seedfrom` URL in /etc/cloud/cloud.cfg.d results in traceback

2024-09-13 Thread Chad Smith

Public bug reported:

Affects cloud-init version: 
24.4~3+really24.3.1-0ubuntu1 and
24.4~3+really24.3.1-0ubuntu2


A new feature added in Oracular was to allow NoCloudNet configuration to be 
detected by providing system configuration in /etc/cloud/cloud.cfg.d/*.cfg like 
the following:

datasource:
  NoCloud:
seedfrom: http://someurl


When NoCloudNet.ds_detect attempts to process that seedfrom url from the 
respective YAML. It results in the traceback:

root@bug-o:~# grep Traceback -A 16 /var/log/cloud-init.log 
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 
1055, in find_source
if s.update_metadata_if_supported(
   ^^^
  File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 
931, in update_metadata_if_supported
result = self.get_data()
 ^^^
  File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 
487, in get_data
return_value = self._check_and_get_data()
   ^^
  File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 
413, in _check_and_get_data
elif self.ds_detect():
 
  File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceNoCloud.py", 
line 458, in ds_detect
.key("seedfrom")
 ^^^
AttributeError: 'dict' object has no attribute 'key'. Did you mean: 'keys'?


### steps to reproduce
cat > lp-321.cfg  High

** Changed in: cloud-init (Ubuntu)
   Status: New => In Progress

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

Title:
  oracular: NoCloudNet datasource `seedfrom` URL in
  /etc/cloud/cloud.cfg.d results in traceback

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


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

[Bug 2067660] Re: deprecate ubuntu_advantage config key from user-data in favor of ubuntu_pro

2024-09-12 Thread Chad Smith

@racb this was missing SRU documentation as far as the previous bionic
upload was concerned as we thought originally this upload may be taken
direct into esm-infra pockets.


But, because this supplemental cloud-config user-data key is required at 
initial instance launch in non-pro images, providing a package update in 
esm-infra doesn't provide non-pro images with the ability to use the unified 
`ubuntu_pro:` key at initial launch.

I have since added the full SRU template to describe the needs as
verification steps to establish that both old config key and new config
key are allowed to ensure no regressing for users trying to launch and
attach non-pro images to Ubuntu Pro.


Per your deprecation comment in bionic, the deprecation treatment in bionic is 
only a debug level log that leaves a breadcrumb to inform that you probably 
shouldn't be using the ubuntu-advantage or ubuntu_advantage keys long term as 
upgrades to the next stable release may have dropped that functionality in the 
more recent LTS. 

Generally deprecated behavior is not ever something cloud-init will drop
across and SRU boundary. We will continue to retain original behavior
where ever possible.  But, by announcing that it is a deprecated
feature, someone who may be thinking of upgrading to a newer release of
Ubuntu such as Focal++ can be better aware that this deprecated behavior
may cause warnings or be dropped across that Ubuntu release upgrade
boundary.

To reinforce this same type of debug level behavior in other active
stable releases (focal ++), we have also recently added a feature flag
in cloud-init on stable releases to provide this same mechanism of only
logging debug level messages for deprecated features[1] which allows
each stable downstream release to declare the cloud-init package version
boundary at which each deprecated message is considered a deprecation
warning level log versus just a debug level log.


References:
[1] 
https://github.com/canonical/cloud-init/blob/ubuntu/jammy/cloudinit/features.py#L90-L122

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

Title:
  deprecate ubuntu_advantage config key from user-data in favor of
  ubuntu_pro

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


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

[Bug 2067660] Re: deprecate ubuntu_advantage config key from user-data in favor of ubuntu_pro

2024-09-12 Thread Chad Smith

** Description changed:

  [ Impact ]
  
-  * This backport supplements cloud-config user-data schema to allow
+  * This backport supplements cloud-config user-data schema to allow
  customers to provide an `ubuntu_pro:` key in cloud-config user-data to
  auto-attach non-pro images to Ubuntu Pro at instance launch.  This
  ubuntu_pro key support is provided in addition to the existing `ubuntu-
  advantage:` keys that are currently supported on Xenial/Bionic. This
  allows uniform configuration and tooling when launching instances across
  either ESM releases and active supported LTS such as Jammy and Noble.
  
  * It also standardizes customer documentation for 'how to attach to Ubuntu 
Pro' to allow a single documented procedure and config that is applicable 
across ESM and active support LTS.  It provides customers with the ability to 
launch any instance in Xenial and Bionic and automatically attach or modify 
Ubuntu Pro services using the same #cloud-config user-data which can also be 
used on all active supported LTSes such as Jammy and Noble.
  * There are additional motivations to migrate away from ubuntu-advantage and 
ubuntu_advantage references in all Canonical products as the product name 
Ubuntu Advantage has been replaced with Ubuntu Pro, so aligning customer 
expectation with the proper product name reduces customer confusion and 
documentation concerns.
  
  * Without this backport to unify cloud-config schema for Pro-related
  functionality, users wishing to attach Xenial, Bionic and Jammy/Noble
  VMs with cloud-config user-data have to provide separate user-data for
  each release. Like the following:
  
  - Xenial or Bionic token attach  and limit services enabled to esm-infra
  
  #cloud-config
  ubuntu-advantage:
-token: 
-enable: [esm-infra]
+    token: 
+    enable: [esm-infra]
  
  -- or --
  
  #cloud-config
  ubuntu_advantage:
-token: 
-enable: [esm-infra]
+    token: 
+    enable: [esm-infra]
  
  - Focal, Jammy and Noble
  #cloud-config
  ubuntu_pro:
-token: 
- enable: [esm-infra]  
- 
- 
- * This uploaded fixes this feature gap by addition supplemental cloud-config 
schema support for ubuntu_pro: key while also retaining support for previous 
ubuntu-advantage and ubuntu_advantage schema.
- 
+    token: 
+ enable: [esm-infra]
+ 
+ * This uploaded fixes this feature gap by addition supplemental cloud-
+ config schema support for ubuntu_pro: key while also retaining support
+ for previous ubuntu-advantage and ubuntu_advantage schema.
  
  [ Test Plan ]
  
+ SRU verification manual testing to perform:
+ 
+ - SRU behavior verification:
+ 
+ 1. Assert ubuntu_pro key is ignored on released xenial cloud-init
+ 2. Assert ubuntu_pro key is honored on -proposed cloud-init. (pro 
detach/cloud-init clean)
+ 3. Assert ubuntu-advantage key is honored on -proposed cloud-init (pro 
detach/cloud-init clean)
+ 4. Assert ubuntu-advantage key debug logs about deprecation in 
/var/log/cloud-init.og
+ 
+ ```
+ #!/bin/bash
+ set -ex
+ RELEASE=$1
+ UA_TOKEN=$2
+ VM_NAME=backport-$1-ubuntu-pro
+ lxc init ubuntu-daily:$RELEASE --vm $VM_NAME
+ lxc config device add $VM_NAME config disk source=cloud-init:config
+ 
+ WAIT_CMD="cloud-init status --wait --long"
+ wait_for_cloud_init() {
+ sleep 5
+ while ! lxc exec $VM_NAME -- $WAIT_CMD; do
+  echo 'waiting...'
+  sleep 5
+ done
+ }
+ 
+ if [ $RELEASE = "xenial" ]; then
+ lxc config set $VM_NAME cloud-init.user-data - << EOF
+ #cloud-config
+ packages:
+   - ubuntu-advantage-tools
+   - linux-image-virtual-hwe-16.04 # 16.04 GA kernel as a problem with vsock
+ runcmd:
+   - mount -t 9p config /mnt
+   - cd /mnt
+   - ./install.sh
+   - cd /
+   - umount /mnt
+   - systemctl start lxd-agent # XXX: causes a reboot
+ EOF
+ else
+ lxc config set $VM_NAME cloud-init.user-data - << EOF
+ #cloud-config
+ packages:
+   - ubuntu-advantage-tools
+ runcmd:
+   - mount -t 9p config /mnt
+   - cd /mnt
+   - ./install.sh
+   - cd /
+   - umount /mnt
+   - systemctl start lxd-agent # XXX: causes a reboot
+ EOF
+ fi
+ 
+ lxc start --console $VM_NAME || true # hit enter on prompt
+ 
+ echo "-- confirm cloud-init boot complete"
+ wait_for_cloud_init
+ 
+ echo "-- setup ubuntu_pro attach user-data"
+ cat > ubuntu_pro.yaml << EOF
+ #cloud-config
+ ubuntu_pro:
+   token: $UA_TOKEN
+ EOF
+ 
+ echo "-- setup ubuntu-advantage attach user-data"
+ cat > ubuntu_adv.yaml << EOF
+ #cloud-config
+ ubuntu-advantage:
+   token: $UA_TOKEN
+ EOF
+ 
+ echo "-- setup ubuntu-advantage commands user-data"
+ cat > ubuntu_adv_cmd.yaml << EOF
+ #cloud-config
+ ubuntu-advantage:
+   commands:
+  00: [attach, $UA_TOKEN]
+ EOF
+ 
+ lxc config set $VM_NAME cloud-init.user-data="$(cat ubuntu_pro.yaml)"
+ lxc exec $VM_NAME -- cloud-init clean --logs --reboot || true
+ 
+ echo "-- confirm orig cloud-init ignores ubuntu_pro"
+ wait_for_cloud_init
+ lxc exec $VM_NAME -- pro status --format=json | jq .attached | grep "false" 
&& echo "SUCCESS: expected ignored ubuntu_pro before u

[Bug 2067660] Re: deprecate ubuntu_advantage config key from user-data in favor of ubuntu_pro

2024-09-12 Thread Chad Smith

** Description changed:

+ [ Impact ]
+ 
+  * This backport supplements cloud-config user-data schema to allow
+ customers to provide an `ubuntu_pro:` key in cloud-config user-data to
+ auto-attach non-pro images to Ubuntu Pro at instance launch.  This
+ ubuntu_pro key support is provided in addition to the existing `ubuntu-
+ advantage:` keys that are currently supported on Xenial/Bionic. This
+ allows uniform configuration and tooling when launching instances across
+ either ESM releases and active supported LTS such as Jammy and Noble.
+ 
+ * It also standardizes customer documentation for 'how to attach to Ubuntu 
Pro' to allow a single documented procedure and config that is applicable 
across ESM and active support LTS.  It provides customers with the ability to 
launch any instance in Xenial and Bionic and automatically attach or modify 
Ubuntu Pro services using the same #cloud-config user-data which can also be 
used on all active supported LTSes such as Jammy and Noble.
+ * There are additional motivations to migrate away from ubuntu-advantage and 
ubuntu_advantage references in all Canonical products as the product name 
Ubuntu Advantage has been replaced with Ubuntu Pro, so aligning customer 
expectation with the proper product name reduces customer confusion and 
documentation concerns.
+ 
+ * Without this backport to unify cloud-config schema for Pro-related
+ functionality, users wishing to attach Xenial, Bionic and Jammy/Noble
+ VMs with cloud-config user-data have to provide separate user-data for
+ each release. Like the following:
+ 
+ - Xenial or Bionic token attach  and limit services enabled to esm-infra
+ 
+ #cloud-config
+ ubuntu-advantage:
+token: 
+enable: [esm-infra]
+ 
+ -- or --
+ 
+ #cloud-config
+ ubuntu_advantage:
+token: 
+enable: [esm-infra]
+ 
+ - Focal, Jammy and Noble
+ #cloud-config
+ ubuntu_pro:
+token: 
+ enable: [esm-infra]  
+ 
+ 
+ * This uploaded fixes this feature gap by addition supplemental cloud-config 
schema support for ubuntu_pro: key while also retaining support for previous 
ubuntu-advantage and ubuntu_advantage schema.
+ 
+ 
+ [ Test Plan ]
+ 
+ 
+ [ Where problems could occur ]
+ 
+  * This changeset is limited to the cc_ubuntu_pro(formerly
+ cc_ubuntu_advantage) module and will only potentially impact users who
+ provide #cloud-config user-data containing config keys for ubuntu-
+ advantage, ubuntu_advantage or ubuntu_pro. The cc_ubuntu_pro module
+ itself is not run unless the specific configuration keys are provided in
+ user-data or in the image in /etc/cloud/cloud.cfg.d/*.cfg files. On
+ typical system boots, this module is skipped at the beginning of the
+ cc_ubuntu_pro.handle function.
+ 
+ 
+ * Problems could occur in the rename of cc_ubuntu_advantage -> cc_ubunt_pro 
module if there are customized /etc/cloud/cloud.cfg files in an image. If the 
customized /etc/cloud/cloud.cfg file retained the former name ubuntu_advantage, 
and the image maintainer didn't accept upstream packaging change contained here 
to rename ubuntu_advantage -> ubuntu_pro, the cloud-init would skip running the 
ubuntu_pro module during boot. This would only affect custom images launched 
with cloud-config user-data containing pro token attach config and also 
retaninig an unsupported /etc/cloud/cloud.cfg file in their images. The result 
would be that cloud-init would succeed booting , but ignore pro-specific 
configuration from user-data.
+ 
+ 
+ [ Other Info ]
+ 
+ [ Original description ]
+ 
  In upstream cloud-init ubuntu_advantage user-data cloud-config key is
  deprecated in favor of ubuntu_pro to better align with current Ubuntu
  Pro product naming and to avoid confusion in howtos, tutorials or
  tooling when interacting with Ubuntu Pro offerings.
  
  In an effort to standardize product naming across all Ubuntu supported
  releases, we will target a backport of this key deprecation to Xenial
  and Bionic to ensure Ubuntu Pro's releases covered by Extended Security
  Maintenance will also align with active Ubuntu Long Term Support(LTS)
  and interim release configuration keys.
  
- 
- This bug is an SRU process bug representing the intent to backport a limited 
scope of functionality related to the cc_ubuntu_advantage module for better 
Ubuntu Pro support ESM releases. 
+ This bug is an SRU process bug representing the intent to backport a
+ limited scope of functionality related to the cc_ubuntu_advantage module
+ for better Ubuntu Pro support ESM releases.
  
  No other functional changes are intended beyond logged messages, user-
  data schema and config-key deprecation.

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

Title:
  deprecate ubuntu_advantage config key from user-data in favor of
  ubuntu_pro

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


--

[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8

2024-09-10 Thread Adam Smith

Hi Jeffrey, yes that workaround solves the problem.  I should have
probably said that.

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

Title:
  Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
  Linux 6.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions


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

[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8

2024-09-10 Thread Adam Smith

lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Celeron 
N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller 
[8086:5a84] (rev 0b)
Subsystem: Acer Incorporated [ALI] Celeron N3350/Pentium N4200/Atom 
E3900 Series Integrated Graphics Controller [1025:1190]
Kernel driver in use: i915
Kernel modules: i915

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

Title:
  Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
  Linux 6.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions


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

[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8

2024-09-10 Thread Adam Smith

Installed 24.04 to a usb drive. Still flickering and with linux-
oem-6.11.  Having a quick look at the patch I guess my device id is
missing.  As noted in the comments above, this hits more than just
Skylake processors.  I think mine is an Apollo lake.

** Tags removed: verification-needed-noble-linux-oem-6.11
** Tags added: verification-failed-noble-linux-oem-6.11

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

Title:
  Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
  Linux 6.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions


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

[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8

2024-09-09 Thread Adam Smith

I've corrected my previous message as I'm actually running 22.04.  I've
tried the 6.8.0-44 kernel which still has the fault.  I don't think
there are any higher packages than that in 22.04?  So I manually
downloaded and installed the 6.11.0-1004-oem and 6.11.0-6 kernels from
24.04/24.10, but these also still have the fault.  With these latter
kernels I do get an update-initramfs warning relating to i915 (missing
bmg_dmc.bin and xe2lpd_dmc.bin files), so I'm not sure if that is a fair
test.  Updating linux-firmware turned into a bit of a nightmare of
dependencies so I gave up.

Hopefully a 24.04 user will be able to test 6.11 properly.

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

Title:
  Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
  Linux 6.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions


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

[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8

2024-09-09 Thread Adam Smith

I believe I have this bug with my N4200 Acer swift laptop.  I was
convinced it was a hardware problem.  Screen flashing (the picture gets
stretched and repeated horizontally while flashing) when the mouse
pointer is at certain positions in the screen.  It is easily repeatable
in Lubuntu 24.04 with the hwe kernel with the mouse just above the task
bar on the right hand side.  I spent the weekend looking for a new
laptop, but before I parted with some money I thought I better double
check there was not a cheaper solution!

Plugging in an external monitor to the hdmi port fixes the problem.  As
does forcing the hdmi port on with the laptop screen mirrored to that
port.  So that's another workaround.

Reverting to a 6.5 kernel also fixes the problem.  This led me to this
bug report.  If you haven't done that though, it is hard to find this
bug.

Surely this should be urgently fixed?  I can't be the only one to be
looking at buying new hardware unnecessarily?

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

Title:
  Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
  Linux 6.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions


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

[Bug 2079849] [NEW] Package dependencies - Where's Lua 5.4?

2024-09-06 Thread Brian Smith

Public bug reported:

Luarocks seems to work well with Lua 5.4, at least in Noble, so is there
any particular reason why it still doesn't allow for 5.4 as a
dependency? I'd love to be able to clean out the parts of 5.3 that
aren't required by anything else.

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

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

Title:
  Package dependencies - Where's Lua 5.4?

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


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

[Bug 2079224] Re: sru cloud-init (24.3.1 update) focal, jammy and noble

2024-09-05 Thread Chad Smith

** Description changed:

  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:
  
-   - Add AOSC linux distribution support (#5310)
-   - Add OpenEuler support for cc_spacewalk module (#5530)
-   - Add network-config seed support for nocloud datasource (#5566)
-   - Support remote URI sources write_files module (#5505)
-   - Add trace-level logger (#5414)
-   - WSL support multi-part MIME config parts as well as landscape tags for
- provisioning (#ttps://github.com/canonical/cloud-init/issues/5460, 
https://github.com/canonical/cloud-init/issues/5538)
-   - avoid snap refresh on package_upgrade: true when snap refresh is held 
(https://github.com/canonical/cloud-init/issues/5290)
-   - optimization: eliminate redundant config reads across boot stages 
(https://github.com/canonical/cloud-init/issues/5536)
-   - provide option to set empty passwords and fix password unlock when
- lock_passwd: False on Alpine/FreeBSD/OpenBSD/DragonflyBSD 
(https://github.com/canonical/cloud-init/issues/5355)
+   - Add AOSC linux distribution support (#5310)
+   - Add OpenEuler support for cc_spacewalk module (#5530)
+   - Add network-config seed support for nocloud datasource (#5566)
+   - Support remote URI sources write_files module (#5505)
+   - Add trace-level logger (#5414)
+   - optimization: eliminate redundant config reads across boot stages 
(https://github.com/canonical/cloud-init/issues/5536)
+   - provide option to set empty passwords and fix password unlock when
+ lock_passwd: False on Alpine/FreeBSD/OpenBSD/DragonflyBSD 
(https://github.com/canonical/cloud-init/issues/5355)
  
  Bug fixes:
-   - NetworkManager network v1 rendering of config ensure bond- prefix
-   - collect-logs avoid inclusion of sensitive data updated apport integration
+   - NetworkManager network v1 rendering of config ensure bond- prefix
+   - collect-logs avoid inclusion of sensitive data updated apport integration
+   - WSL support multi-part MIME config parts as well as landscape tags for
+ provisioning (https://github.com/canonical/cloud-init/issues/5460, 
https://github.com/canonical/cloud-init/issues/5538)
+   - avoid snap refresh on package_upgrade: true when snap refresh is held 
(https://github.com/canonical/cloud-init/issues/5290)
+   - fix(netops): fix ip addr flush command (#5651) (GH: 
https://github.com/canonical/cloud-init/issues/5648)
+ 
+ 
+ Package patch reverts of upstream breaking changes to retain original 
behavior:
+   - Avoid introducing single-process systemd unit cloud-init-main.service
+   - deprecation version boundary to indicate cloud-init package downstream 
version before which 'deprecation' logs are treated only as debug logs
+   - avoid attempting to read network-config in NoCloud datasource via 
nocloud.read_seeded utility to avoid speed impacts while retrying a file which 
may not be there.
+ 
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates
  
  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug.  cloud-init team
  members will not mark ‘verification-done’ until this has happened.
  
  * Automated Test Results
  
  
  
  
  
  * Manual Test Results
  
  
  
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.
  
  [Discussion]
  
  
  [Changelog]
-  - docs: Clarify v2 set-name behavior (#5639)
-  - fix: properly handle blank lines in fstab (#5643)
-  - fix: cc_user_groups incorrectly assumes "useradd" never locks password
-field (#5355) [dermotbradley]
-  - tests: assert cloud-init user-data cert is the only root cert (#5641)
-  - feat: add automation for ubuntu/* branches asserting quilt patches apply
-(#5622)
-  - fix(sources/wsl): no error with empty .cloud-init dir (SC-1862) (#5633)
-  - feat(azure): add PPS support for azure-proxy-agent (#5601)
-[Ksenija Stanojevic]
-  - fix(tests): use instance.clean/restart instead of clean --reboot (#5636)
-  - test: fix cmd/test_schema int test (#5629)
-  - test: fix test_honor_cloud_dir int test (#5627)
-  - docs: alphabetize dsname lookup table. update comment to create the csv
-(#5624)
-  - docs: new datasources should update reference/ds_dsname_map (#5624)
-  - test: fix ca_certs int test (#5626)
-  - chore: update schema docs to use RST bold for config key names (#5562)
-  - fix(doc): italics around deprecation prefix, description bolds key names
-(#5562)
-  - feat(doc): add env vars to debug config module doc builds (#5562)
-  - fix(doc): doc of nested objects under JSON schema items.oneOf (#5562)
-  - fix(doc): object type check if patternProperties or p

[Bug 2079224] [NEW] sru cloud-init (24.3.1 update) focal, jammy and noble

2024-09-05 Thread Chad Smith

Public bug reported:

== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:

  - Add AOSC linux distribution support (#5310)
  - Add OpenEuler support for cc_spacewalk module (#5530)
  - Add network-config seed support for nocloud datasource (#5566)
  - Support remote URI sources write_files module (#5505)
  - Add trace-level logger (#5414)
  - WSL support multi-part MIME config parts as well as landscape tags for
provisioning (#ttps://github.com/canonical/cloud-init/issues/5460, 
https://github.com/canonical/cloud-init/issues/5538)
  - avoid snap refresh on package_upgrade: true when snap refresh is held 
(https://github.com/canonical/cloud-init/issues/5290)
  - optimization: eliminate redundant config reads across boot stages 
(https://github.com/canonical/cloud-init/issues/5536)
  - provide option to set empty passwords and fix password unlock when
lock_passwd: False on Alpine/FreeBSD/OpenBSD/DragonflyBSD 
(https://github.com/canonical/cloud-init/issues/5355)

Bug fixes:
  - NetworkManager network v1 rendering of config ensure bond- prefix
  - collect-logs avoid inclusion of sensitive data updated apport integration

See the changelog entry below for a full list of changes and bugs.

[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/CloudinitUpdates

The cloud-init team will be in charge of attaching the artifacts and
console output of the appropriate run to the bug.  cloud-init team
members will not mark ‘verification-done’ until this has happened.

* Automated Test Results





* Manual Test Results




[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned integration tests are attached to this bug.

[Discussion]


[Changelog]
 - docs: Clarify v2 set-name behavior (#5639)
 - fix: properly handle blank lines in fstab (#5643)
 - fix: cc_user_groups incorrectly assumes "useradd" never locks password
   field (#5355) [dermotbradley]
 - tests: assert cloud-init user-data cert is the only root cert (#5641)
 - feat: add automation for ubuntu/* branches asserting quilt patches apply
   (#5622)
 - fix(sources/wsl): no error with empty .cloud-init dir (SC-1862) (#5633)
 - feat(azure): add PPS support for azure-proxy-agent (#5601)
   [Ksenija Stanojevic]
 - fix(tests): use instance.clean/restart instead of clean --reboot (#5636)
 - test: fix cmd/test_schema int test (#5629)
 - test: fix test_honor_cloud_dir int test (#5627)
 - docs: alphabetize dsname lookup table. update comment to create the csv
   (#5624)
 - docs: new datasources should update reference/ds_dsname_map (#5624)
 - test: fix ca_certs int test (#5626)
 - chore: update schema docs to use RST bold for config key names (#5562)
 - fix(doc): italics around deprecation prefix, description bolds key names
   (#5562)
 - feat(doc): add env vars to debug config module doc builds (#5562)
 - fix(doc): doc of nested objects under JSON schema items.oneOf (#5562)
 - fix(doc): object type check if patternProperties or properties (#5562)
 - doc(schema): schema descriptions should end with trailing stop (#5562)
 - fix(wsl): Properly assemble multipart data (#5538) [Carlos Nihelton]
 - feat: collect-logs improvements (#5619)
 - tests: fix test_ca_certs.py for gcp (#5621)
 - fix(nm): Ensure bond property name formatting matches schema definition
   (#5383) [Curt Moore]
 - Update behavior of base bond interface with NetworkManager (#5385)
   [Curt Moore]
 - ci: Drop Python 3.6 and 3.7 (#5607)
 - chore(black): Bump version (#5607)
 - chore(mypy): Fix failures on newer versions of mypy (#5607)
 - chore(tox.ini): Simplify configuration, fix minor bugs (#5607)
 - chore(mypy): Lint log module (#5607)
 - fix(systemd): Correct location of installed drop-in files(#5615)
   [Noah Meyerhans]
 - fix(btrfs): Version parsing (#5618)
 - docs: Remove unnecessary section, add feature flag page (#5617)
 - docs: Drop Python 3.6 and 3.7 support (#5617)
 - chore: explain other use of oauth (#5616)
 - chore(actions): add doc label for any doc related subdir file matches
 - doc(boot): Make first boot a dedicated page (#5595)
 - doc: Describe all stages in a single process (#5595)
 - chore: Deprecate old commands in help output (#5595)
 - chore: add comment explaining the NetworkManager may-fail setting
   (#5598) [Ani Sinha]
 - Revert "fix(vmware): Set IPv6 to dhcp when there is no IPv6 addr
   (#5471)" (#5596) [PengpengSun]
 - fix: read_optional_seed to set network-config when present (#5593)
 - feat(snap): avoid refresh on package_upgrade: true and refresh.hold
   (#5426)
 - fix: Fix tests which have outdated strings (#5585)
 - fix: Fix ftp failures (#5585)
 - doc: improve integration testing configuration instructions (#5556)
   [Alec Warren]
 - azure: check azure-proxy-agent status (#5138) [Ksenija Stanojevic]
 - refactor: refactor and fix

[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy and noble

2024-09-05 Thread Chad Smith

** Changed in: cloud-init (Ubuntu)
   Status: New => Fix Released

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

Title:
  sru cloud-init (24.2 update) to focal, jammy and noble

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


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

[Bug 2078650] [NEW] package pkg-config:amd64 (not installed) failed to install/upgrade: dependency problems - not removing

2024-09-01 Thread Graham Smith

Public bug reported:

$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04.1 LTS
Release:24.04


and obviously pkg-config is not installed:
$ apt-cache policy pkg-config
pkg-config:
  Installed: (none)
  Candidate: 1.8.1-2build1
  Version table:
 1.8.1-2build1 500
500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: pkg-config:amd64 (not installed)
ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
Uname: Linux 6.8.0-40-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sun Sep  1 20:15:23 2024
ErrorMessage: dependency problems - not removing
InstallationDate: Installed on 2024-06-07 (86 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.22.6ubuntu6.1
 apt  2.7.14build2
SourcePackage: pkgconf
Title: package pkg-config:amd64 (not installed) failed to install/upgrade: 
dependency problems - not removing
UpgradeStatus: Upgraded to noble on 2024-09-02 (0 days ago)
modified.conffile..etc.dpkg.dpkg.cfg.d.pkg-config-hook-config: [deleted]
mtime.conffile..etc.init.d.apport: 2024-07-22T07:59:07

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


** Tags: amd64 apport-package noble

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

Title:
  package pkg-config:amd64 (not installed) failed to install/upgrade:
  dependency problems - not removing

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


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

[Bug 2059149] Re: Crash

2024-09-01 Thread Danny Smith

Ok, can confirm after having disabled Gnome's 'screen lock' entirely,
that this is triggered merely by the 'Screen blanking' being invoked.
For now will workaround by disabling that, but in case it's useful
here's the dmesg output from when this happened just now when the screen
blanked. Leaving out the remaining call stack as it's no different from
previously.

```
[Sun Sep  1 22:11:08 2024] audit: type=1400 audit(1725225069.215:107): 
apparmor="DENIED" operation="capable" class="cap" 
profile="/usr/lib/snapd/snap-confine" pid=8136 comm="snap-confine" 
capability=12  capname="net_admin"
[Sun Sep  1 22:11:08 2024] audit: type=1400 audit(1725225069.215:108): 
apparmor="DENIED" operation="capable" class="cap" 
profile="/usr/lib/snapd/snap-confine" pid=8136 comm="snap-confine" 
capability=38  capname="perfmon"
[Sun Sep  1 22:19:09 2024] simple-framebuffer simple-framebuffer.0: swiotlb 
buffer is full (sz: 1802240 bytes), total 32768 (slots), used 86 (slots)
[Sun Sep  1 22:19:09 2024] simple-framebuffer simple-framebuffer.0: swiotlb 
buffer is full (sz: 1802240 bytes), total 32768 (slots), used 86 (slots)
[Sun Sep  1 22:19:10 2024] simple-framebuffer simple-framebuffer.0: swiotlb 
buffer is full (sz: 2068480 bytes), total 32768 (slots), used 12 (slots)
[Sun Sep  1 22:19:12 2024] usb 1-3.2: USB disconnect, device number 5
[Sun Sep  1 22:19:15 2024] simple-framebuffer simple-framebuffer.0: swiotlb 
buffer is full (sz: 442368 bytes), total 32768 (slots), used 6096 (slots)
[Sun Sep  1 22:19:15 2024] [ cut here ]
[Sun Sep  1 22:19:15 2024] simple-framebuffer simple-framebuffer.0: 
drm_WARN_ON(map->is_iomem)
[Sun Sep  1 22:19:15 2024] WARNING: CPU: 9 PID: 2746 at 
drivers/gpu/drm/drm_gem_shmem_helper.c:319 drm_gem_shmem_vmap+0x1a5/0x1e0
[Sun Sep  1 22:19:15 2024] Modules linked in: veth xt_MASQUERADE 
nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter nft_chain_nat 
xt_nat nf_nat nfnetlink_queue xt_commen>
[Sun Sep  1 22:19:15 2024]  btusb ac97_bus videobuf2_memops snd_pcm_dmaengine 
videobuf2_v4l2 btrtl snd_usb_audio kvm_intel snd_hda_intel btintel videodev 
btbcm snd_intel_dspcfg btmtk s>
[Sun Sep  1 22:19:15 2024]  hid_logitech_dj hid_generic cdc_ncm usbhid 
cdc_ether usbnet hid mii nvme crc32_pclmul r8169 nvme_core i2c_i801 
spi_intel_pci intel_lpss_pci ahci xhci_pci sp>
[Sun Sep  1 22:19:15 2024] CPU: 9 PID: 2746 Comm: Xorg Tainted: P   OE  
6.8.0-40-generic #40~22.04.3-Ubuntu
[Sun Sep  1 22:19:15 2024] Hardware name: Gigabyte Technology Co., Ltd. B760M 
DS3H DDR4/B760M DS3H DDR4, BIOS F17 05/08/2024
[Sun Sep  1 22:19:15 2024] RIP: 0010:drm_gem_shmem_vmap+0x1a5/0x1e0
[Sun Sep  1 22:19:15 2024] Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 c4 a3 
ec ff 48 c7 c1 39 19 09 a5 4c 89 ea 48 c7 c7 17 9b 08 a5 48 89 c6 e8 ab 34 46 
ff <0f> 0b 48 8b 83 f0 00 00>
[Sun Sep  1 22:19:15 2024] RSP: 0018:bfb243e2b940 EFLAGS: 00010246
[Sun Sep  1 22:19:15 2024] RAX:  RBX: 9f9b84897000 RCX: 

[Sun Sep  1 22:19:15 2024] RDX:  RSI:  RDI: 

[Sun Sep  1 22:19:15 2024] RBP: bfb243e2b960 R08:  R09: 

[Sun Sep  1 22:19:15 2024] R10:  R11:  R12: 
9f9dfa6634c8
[Sun Sep  1 22:19:15 2024] R13: 9f9b829c6e20 R14: 9f9dfa6634c8 R15: 
9f9dfa6634c8
[Sun Sep  1 22:19:15 2024] FS:  7a451114ea80() 
GS:9faaff88() knlGS:
[Sun Sep  1 22:19:15 2024] CS:  0010 DS:  ES:  CR0: 80050033
[Sun Sep  1 22:19:15 2024] CR2: 5d8582fb9e1c CR3: 00010ad88000 CR4: 
00f50ef0
[Sun Sep  1 22:19:15 2024] PKRU: 5554
[Sun Sep  1 22:19:15 2024] Call Trace:
[Sun Sep  1 22:19:15 2024]  
[Sun Sep  1 22:19:15 2024]  ? show_regs+0x6d/0x80
[Sun Sep  1 22:19:15 2024]  ? __warn+0x89/0x160
```

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

Title:
  Crash

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


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

[Bug 2059149] Re: Crash

2024-09-01 Thread Danny Smith

I'm having the same issue right now. I've just applied latest updates,
but not sure whether they're relevant - seems more relevant that I've
just moved to using HDMI audio based on the content of this crash, but
either could be involved.

Attaching requested diagnostic files - please let me know if I need to
re-open this as a new bug since this one is 'Expired'.

`sudo journalctl -b0 > journal.txt` -> `journal.txt`
`sudo journalctl -b-1 > prevjournal.txt` -> `prevjournal.txt`
`sudo find /var/crash -mtime -1` yields no new files (crash was about 10 
minutes ago).
`/var/lib/whoopsie/whoopsie-id` is dated several hours prior to this particular 
crash.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059149/+attachment/5812024/+files/journal.txt

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

Title:
  Crash

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


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

[Bug 2059149] Re: Crash

2024-09-01 Thread Danny Smith

`prevjournal.txt` (looks like I can't attach multiple files to a single
post)

If it helps, current system with the issue is an i7-12700F with an NVIDIA 
GeForce RTX 4070 SUPER (pci-id 10de:2783).
I also have a suspicion that problematic behaviour only ensues after playing 
Steam games full screen, and Gnome screensaver then kicking in, but I have yet 
to gather firm evidence of that.

** Attachment added: "prevjournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059149/+attachment/5812025/+files/prevjournal.txt

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

Title:
  Crash

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


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

[Bug 2075968] Re: cloud-init locks out user `ubuntu` after upgrade from 22.04 to 24.04

2024-08-30 Thread Chad Smith

Confirmed the URU 1:24.04.21 disables cloud-init across upgrade via
marker file. Marking invalid for cloud-init as running on first boot is
cloud-init default mode of operation.

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

** Changed in: cloud-init (Ubuntu Noble)
   Status: New => Invalid

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

Title:
  cloud-init locks out user `ubuntu` after upgrade from 22.04 to 24.04

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


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

[Bug 2039594] Re: sgdisk - Unexpected Behavior with Decimal Point in Partition Size Specification

2024-08-29 Thread Rod Smith

I'm gdisk's upstream author. I'm pretty busy with other things right
now, so I don't really have the time to invest in implementing floating-
point support in gdisk's inputs. Done poorly, that's the sort of thing
that could create additional bugs. Thus, I don't recommend holding off
on implementing the existing fix.

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

Title:
  sgdisk - Unexpected Behavior with Decimal Point in Partition Size
  Specification

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


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

[Bug 2073163] Re: Please update to 20240716.00

2024-08-27 Thread Chloé Smith

Related bug (https://bugs.launchpad.net/ubuntu/+source/google-guest-
agent/+bug/2057965) is now verified as well

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

Title:
  Please update to 20240716.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2073163/+subscriptions


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

[Bug 2057965] Re: google-startup-scripts runs before cloud-init finished network setup

2024-08-27 Thread Chloé Smith

 VALIDATION 

All images used below were built with snapshots from 20240306T030400Z
and 20240510T030400Z for cloud-init and ubuntu-pro-client respectively.

=== FOCAL FOSSA ===

kajiya@little-HAL:~$ cat startup.sh 
#!/bin/bash
cp /etc/apt/sources.list /tmp/startup-sources.list

touch /home/ubuntu/hello.txt

--

kajiya@little-HAL:~$ gcloud compute instances create focal-startup-
bug-2057965 --image testing-ubuntu-guest-2004-focal-v20240823 --image-
project ubuntu-kajiya --metadata-from-file=startup-script=startup.sh

kajiya@little-HAL:~$ ssh ubuntu@35.204.59.206

--

ubuntu@focal-startup-bug-2057965:~$ pro --version
31.2.3~20.04

ubuntu@focal-startup-bug-2057965:~$ cloud-init --version
/usr/bin/cloud-init 23.4.4-0ubuntu0~20.04.1

ubuntu@focal-startup-bug-2057965:~$ ls
hello.txt

ubuntu@focal-startup-bug-2057965:~$ diff /tmp/startup-sources.list
/etc/apt/sources.list

ubuntu@focal-startup-bug-2057965:~$

=== JAMMY JELLYFISH ===

kajiya@little-HAL:~$ cat startup.sh 
#!/bin/bash
cp /etc/apt/sources.list /tmp/startup-sources.list

touch /home/ubuntu/hello.txt

--

kajiya@little-HAL:~$ gcloud compute instances create jammy-startup-
bug-2057965 --image testing-ubuntu-guest-2204-jammy-v20240823 --image-
project ubuntu-kajiya --metadata-from-file=startup-script=startup.sh

kajiya@little-HAL:~$ ssh ubuntu@34.90.192.236

--

ubuntu@jammy-startup-bug-2057965:~$ pro --version
31.2.3~22.04

ubuntu@jammy-startup-bug-2057965:~$ cloud-init --version
/usr/bin/cloud-init 23.4.4-0ubuntu0~22.04.1

ubuntu@jammy-startup-bug-2057965:~$ ls
hello.txt

ubuntu@jammy-startup-bug-2057965:~$ diff /tmp/startup-sources.list
/etc/apt/sources.list

ubuntu@jammy-startup-bug-2057965:~$

=== NOBLE NUMBAT ===

kajiya@little-HAL:~$ cat startup.sh 
#!/bin/bash
cp /etc/apt/sources.list /tmp/startup-sources.list

touch /home/ubuntu/hello.txt

--

kajiya@little-HAL:~$ gcloud compute instances create noble-startup-
bug-2057965 --image testing-ubuntu-guest-2404-noble-amd64-v20240823
--image-project ubuntu-kajiya --metadata-from-file=startup-
script=startup.sh

kajiya@little-HAL:~$ ssh ubuntu@35.204.72.82

--

ubuntu@noble-startup-bug-2057965:~$ ls
hello.txt

ubuntu@noble-startup-bug-2057965:~$ pro --version
31.2.3
ubuntu@noble-startup-bug-2057965:~$ cloud-init --version
/usr/bin/cloud-init 24.1-0ubuntu1

ubuntu@noble-startup-bug-2057965:~$ diff /tmp/startup-sources.list
/etc/apt/sources.list

ubuntu@noble-startup-bug-2057965:~$

ubuntu@noble-startup-bug-2057965:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @23.527s
└─multi-user.target @23.527s
  └─getty.target @23.527s
└─getty@tty1.service @23.527s
  └─system-getty.slice @23.522s
└─setvtrgb.service @23.462s +57ms
  └─plymouth-quit-wait.service @23.435s +11ms
└─systemd-user-sessions.service @23.394s +34ms
  └─cloud-config.service @22.305s +1.080s   
<<<
└─basic.target @11.709s
  └─sockets.target @11.700s
└─snapd.socket @11.628s +59ms
  └─sysinit.target @11.517s
└─cloud-init.service @8.942s +2.206s
  └─systemd-networkd-wait-online.service @8.893s +31ms
└─systemd-networkd.service @8.692s +175ms
  └─network-pre.target @8.677s
└─cloud-init-local.service @4.842s +3.822s
  └─systemd-remount-fs.service @2.192s +117ms
└─systemd-fsck-root.service @1.917s +243ms
  └─systemd-journald.socket @1.643s
└─-.mount @1.520s
  └─-.slice @1.520s

** Tags removed: verification-needed verification-needed-focal 
verification-needed-jammy verification-needed-noble
** Tags added: verification-done verification-done-focal 
verification-done-jammy verification-done-noble

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

Title:
  google-startup-scripts runs before cloud-init finished network setup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2057965/+subscriptions


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

[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy and noble

2024-08-23 Thread Chad Smith

The blocking release of python3-defaults just published to noble and
jammy yesterday per bug
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337.
We should be able to proceed with release of cloud-init as all
verification was done as of 08-01-2024

** Tags removed: verification-needed-noble
** Tags added: verification-done-noble

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

Title:
  sru cloud-init (24.2 update) to focal, jammy and noble

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


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

[Bug 2075337] Re: [SRU] py3clean fails when using alternate character set

Adapted script to support installing sqt-launcher from universe in
jammy.


** Attachment added: "sru-2075337.sh"
   
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337/+attachment/5808150/+files/sru-2075337.sh

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

Title:
  [SRU] py3clean fails when using alternate character set

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


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

[Bug 2075337] Re: [SRU] py3clean fails when using alternate character set

Verification logs success noble.
csmith@midtown:~$ ./sru-2075337.sh 
+ cat
+ SET_LOCALE_YAML='#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True
locale: fr_FR
'
+ export LANG=en_AU.ISO-8859-1
+ LANG=en_AU.ISO-8859-1
+ for RELEASE in noble
+ NAME=sru-2075337-noble
+ lxc launch ubuntu:noble sru-2075337-noble -c 
'cloud-init.user-data=#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True
locale: fr_FR
'
Creating sru-2075337-noble
Starting sru-2075337-noble
+ sleep 10
+ lxc exec sru-2075337-noble -- dpkg-query -W python3-minimal
python3-minimal 3.12.3-0ubuntu1
+ echo 'Run: sudo apt install --reinstall cloud-init to validate failure'
Run: sudo apt install --reinstall cloud-init to validate failure
+ lxc console sru-2075337-noble
To detach from the console, press: +a q

sru-2075337-noble login: ubuntu
Password: 
Welcome to Ubuntu 24.04 LTS (GNU/Linux 6.5.0-44-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/pro

 System information as of jeu. 22 ao�t 2024 21:36:55 UTC

  System load:   2.21
  Usage of /:53.9% of 839MB
  Memory usage:  0%
  Swap usage:0%
  Temperature:   52.0 C
  Processes: 20
  Users logged in:   0
  IPv4 address for eth0: 10.125.221.103
  IPv6 address for eth0: fd42:e810:4b9b:718:216:3eff:fedf:1d30

Expanded Security Maintenance for Applications is not enabled.

0 updates can be applied immediately.

Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status


The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

ubuntu@sru-2075337-noble:~$ sudo apt-get install --reinstall cloud-init 
Lecture des listes de paquets... Fait
Construction de l'arbre des d�pendances... Fait
Lecture des informations d'�tat... Fait
0 mis � jour, 0 nouvellement install�s, 1 r�install�s, 0 � enlever et 0 non mis 
� jour.
Il est n�cessaire de prendre 598 ko dans les archives.
Apr�s cette op�ration, 0 o d'espace disque suppl�mentaires seront utilis�s.
R�ception de�:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 
cloud-init all 24.1.3-0ubuntu3.3 [598 kB]
598 ko r�ceptionn�s en 0s (1�398 ko/s)
Pr�configuration des paquets...
(Lecture de la base de donn�es... 34407 fichiers et r�pertoires d�j� install�s.)
Pr�paration du d�paquetage de .../cloud-init_24.1.3-0ubuntu3.3_all.deb ...
Traceback (most recent call last):
  File "/usr/bin/py3clean", line 210, in 
main()
  File "/usr/bin/py3clean", line 196, in main
pfiles = set(dpf.from_package(options.package))
 ^^
  File "/usr/share/python3/debpython/files.py", line 54, in from_package
stdout = str(stdout, 'utf-8')
 
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
dpkg: avertissement: le sous-processus ancien paquet cloud-init script 
pre-removal a renvoy� un �tat de sortie d'erreur 1
dpkg: tentative d'ex�cution du script du nouveau paquet � la place...
Traceback (most recent call last):
  File "/usr/bin/py3clean", line 210, in 
main()
  File "/usr/bin/py3clean", line 196, in main
pfiles = set(dpf.from_package(options.package))
 ^^
  File "/usr/share/python3/debpython/files.py", line 54, in from_package
stdout = str(stdout, 'utf-8')
 
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb (--unpack)�:
 le sous-processus nouveau cloud-init paquet pre-removal script a renvoy� un 
�tat de sortie d'erreur 1
dmesg: read kernel buffer failed: Operation not permitted
Traceback (most recent call last):
  File "/usr/bin/py3compile", line 323, in 
main()
  File "/usr/bin/py3compile", line 302, in main
compile(files, versions,
  File "/usr/bin/py3compile", line 185, in compile
for fn, versions_to_compile in filter_files(files, e_patterns, versions):
  File "/usr/bin/py3compile", line 128, in filter_files
for fpath in files:
  File "/usr/share/python3/debpython/files.py", line 71, in filter_public
for fn in files:
  File "/usr/share/python3/debpython/files.py", line 54, in from_package
stdout = str(stdout, 'utf-8')
 
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
dpkg: erreur lors du nettoyage:
 le sous-processus paqu

[Bug 2075337] Re: [SRU] py3clean fails when using alternate character set

Verification script for noble

- verify current failure with existing python3-defaults and cloud-init reinstall
- verify success with python3-defaults from -proposed and cloud-init reinstall

** Attachment added: "sru-2075337.sh"
   
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337/+attachment/5808149/+files/sru-2075337.sh

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

Title:
  [SRU] py3clean fails when using alternate character set

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


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

[Bug 2075337] Re: [SRU] py3clean fails when using alternate character set

Since cloud-init is blocking our releases on this bug. I'll take this
test plan and tag when finished

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

Title:
  [SRU] py3clean fails when using alternate character set

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


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

[Bug 2074559] Re: [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered with black flickering rectangle

2024-08-14 Thread Jackson Smith

Please see https://gitlab.gnome.org/GNOME/mutter/-/issues/3619

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3619
   https://gitlab.gnome.org/GNOME/mutter/-/issues/3619

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

Title:
  [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered
  with black flickering rectangle

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


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

[Bug 2074559] Re: [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered with black flickering rectangle

2024-08-12 Thread Jackson Smith

I logged in with 'Ubuntu on Xorg' selected. There is no artefact when
locking/unlocking the screen, or when changing refresh rates. The list
of refresh rates is shorter, containing only 59.88, 100, 110, & 120Hz;
seemingly in agreement with the edid data.

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

Title:
  [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered
  with black flickering rectangle

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


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

[Bug 2074559] Re: [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered with black flickering rectangle

2024-08-09 Thread Jackson Smith

Thanks.

I ran this:

for e in /sys/class/drm/*/edid ; do echo -e "\n\n$e" ; edid-decode $e ;
done > edid.txt

So that the path is also copied in. I guess that
/sys/class/drm/card0-DVI-D-1/edid is the interesting one because the DVI
is connected to the offending SyncMaster.

** Attachment added: "edid.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074559/+attachment/5804173/+files/edid.txt

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

Title:
  [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered
  with black flickering rectangle

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


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

[Bug 2075968] Re: cloud-init locks out user `ubuntu` after upgrade from 22.04 to 24.04

I can confirm in Ubuntu cloudimages on LXD that do-release-upgrade
across Jammy -> Noble succeeds having run cloud-init on first image
launch in Jammy, removing the cache due to python3 version upgrade, and
redetecting LXD datasource config on reboot into Noble with proper
instance-id detection.

In this scenario where cloud-init was run before upgrade,
/var/lib/cloud/data/previous-iid cache recorded LXD platform's instance-
id on first boot, and across upgrade cloud-init determines that
instance-id had no delta and doesn't need to run again.

Nick mentioned in comment #13 that cloud-init is being installed across
the upgrade path to noble in Xubuntu due to "Recommends: cloud-init".

In the Xubuntu 22.04 -> 24.04 scenario, across reboot into 24.04, there
is no cached /var/lib/cloud/data/previous-iid because cloud-init has
never run in this image, so the boot of 24.04 triggers cloud-init to
attempt to detect datasources, finds potential LXD datasource, so it
tries to run as a 'new instance first boot' which applies cloud-init
defaults from /etc/cloud/cloud.cfg which states "lock_passwd: true" for
the ubuntu user.


So, if cloud-init is being pulled in during do-release-upgrade where it wasn't 
previously installed, I think we may need to think of a path/hook in 
do-release-upgrade that can leave cloud-init in a disabled state in that image 
(because it wasn't originally run in the original image) as it will by default 
be enabled on next boot and perform default setup and config which will lock 
down certain users and passwords, create new SSH host keys etc.

One way to disable cloud-init easily is creating an /etc/cloud/cloud-
init.disabled file on the system which will keep cloud-init inert
intentionally (which is generally a good idea for desktop images to
avoid exposure to rogue USB sticks which contain cloud-init user-data
being plugged into a laptop and forcing reconfiguration of a laptop)


By providing a quirk if cloud-init gets included in an image that doesn't 
already contain cloud-init, we can prevent this pitfall by adding something 
like the following across upgrade.

cat > /etc/cloud/cloud-init.disabled

[Bug 2075968] Re: cloud-init locks out user `ubuntu` after upgrade from 22.04 to 24.04

>  If so, when doing a release upgrade, cloud-init will see a new python
version, clear it's cache, then run as if it was first boot again.

Ahh the cleared cache is what triggers cloud-init to re-run thereby
reapplying any user-data it detects on that subsequent boot. Since
default system configuration in this image /etc/cloud/cloud.cfg is to
lock_passwd cloud-init happily locks down that passwd access with that
leading ! in /etc/shadow

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

Title:
  cloud-init locks out user `ubuntu` after upgrade from 22.04 to 24.04

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


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

[Bug 2075968] Re: cloud-init locks out user `ubuntu` after upgrade from 22.04 to 24.04

In the logs there we can see that cloud-init across reboot added a
WARNING because it was unable to redetect the LXD datasource in noble:

2024-08-08 18:55:53,280 - cc_final_message.py[WARNING]: Used fallback
datasource


This discovery of a new datasource triggers cloud-init to re-run on a system 
for all modules including:

- setting the default user up (and setting it's password)
- creating new SSH host keys
- re-applying any user-data found


Also what's strange in the attached /var/log/cloud-init.log is that something 
disrupted cloud-init before it completed all boot stages on the initial run. I 
see only two of 4 boot stages run before possibly a reboot:


2024-08-08 18:50:34,099 - util.py[DEBUG]: Cloud-init v. 24.1.3-0ubuntu3.3 
running 'init-local' at Thu, 08 Aug 2024 18:50:34 +. Up 4.19 seconds.
...
2024-08-08 18:50:35,421 - util.py[DEBUG]: Cloud-init v. 24.1.3-0ubuntu3.3 
running 'init' at Thu, 08 Aug 2024 18:50:35 +. Up 5.51 seconds.
2024-08-08 18:50:37,131 - handlers.py[DEBUG]: finish: init-network: SUCCESS: 
searching for network datasources
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@2024-08-08
 18:51:31,954 - util.py[DEBUG]: Cloud-init v. 24.1.3-0ubuntu3.3 running 
'init-local' at Thu, 08 Aug 2024 18:51:31 +. Up 4.06 seconds.


All those concatonated Null bytes in logs are concerning. Something else is 
going on on the system that is disrupting cloud-init services.


Unfortunately the attached journalctl log in the tar file doesn't tell us what 
happened prior to the most recent boot which triggered cloud-init to only 
complete 'init-local' and 'init' stages on that first boot and restart in 
init-local on second boot, but it's that reboot that I expect is triggering 
that re-

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

Title:
  cloud

[Bug 2075968] Re: cloud-init locks out user `ubuntu` after upgrade from 22.04 to 24.04

Can we upload cloud-init collect-logs to this bug to see cloud-init's
behavior across this reboot?  If cloud-init thinks it didn't run for
some reason across upgrade then it may re-run thinking it is a fresh
install. Having visiblity to the full /var/log/cloud-init.log would be
helpful here.

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

Title:
  cloud-init locks out user `ubuntu` after upgrade from 22.04 to 24.04

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


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

[Bug 2074559] Re: [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered with black flickering rectangle

2024-08-07 Thread Jackson Smith

I wonder whether your observation about refresh rate isn't on the right
track. The drop-down list in Settings > Displays > Samsung Electric
Company 22" > Refresh Rate is as follows (in Hz):

120.00
110.00
100.00
 89.94
 59.95
 59.88

The default setting is for 59.88Hz, where I get clipping. If I change to
59.95Hz then I cannot seem to trigger clipping. When swapping from
59.95Hz to 59.88Hz, though, I get immediate clipping. Clipping is also
induced when I select 100.00, 110.00, or 120.00; at 89.94Hz, the entire
screen is black.

The only reliable performance appears to be at 59.95Hz.

Therefore, your earlier suggestion to try different refresh rates is the
likely solution, here. However, I would expect to see stable performance
at least at 120Hz, that being approximately an integer multiple of
59.95Hz.

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

Title:
  [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered
  with black flickering rectangle

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


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

[Bug 2074559] Re: [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered with black flickering rectangle

2024-08-06 Thread Jackson Smith

The Samsung SyncMaster 2233 does have a menu button that leads to an
information panel which reports:

64.6kHz
60Hz
PN
1680x1050

Alas, 'Adjust for TV' broke everything. I had to Alt + SysRq + REISUB,
and reboot into recovery mode. Remounted the file system for read/write
and removed ~/.config/monitors.xml. Then everything worked again.

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

Title:
  [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered
  with black flickering rectangle

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-08-02 Thread Jackson Smith

Sorry, you'd asked about that, before.

My secondary monitor shows no signal if the resolution is anything but
the maximum, native resolution of the screen.

Changing the refresh rate may temporarily restore drawing to the full
screen. However, locking the screen and then allowing it to sleep will
trigger another black region at the top of the screen. The effect of
different refresh rates is to change the width of the screen. For
example, the secondary monitor can run at 120Hz, in which case the black
region fills half of the screen, rather than a small slice, as it does
at around 60Hz.

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

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-08-01 Thread Jackson Smith

ps - I don't know whether this information was preserved in the original
bug report, but it may be important.

First, the secondary monitor is positioned to the left hand side,
relative to the primary monitor. This was set by moving the small icon
of the secondary monitor in Settings>Displays to the left of the primary
monitor's icon.

Second, the Dock is on the left edge of the primary monitor, and the
Dock's auto-hide behaviour is active. Therefore, to move the mouse
cursor from the primary monitor to the secondary monitor, I must push
the cursor through the Dock and onto the secondary monitor.

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

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-08-01 Thread Jackson Smith

Just to be clear, I associate restarting gnome with logging out then
logging in again. Not with unplugging the monitor and reconnecting.

Concerning the present bug report, I'm becoming confident that the
flickering black bar appears at the top of the secondary monitor after
the following steps:

1 - Lock the screen, either manually or waiting for the timeout.
2 - Wait for screen to sleep.
3 - Unlock the screen

Logging out/in eliminates the black bar, and restores normal behaviour
until the next time the screen locks and sleeps.

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

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-07-31 Thread Jackson Smith

The trigger may be when a) the screen is locked, and b) the screen
blacks out. Logging back in after this leads to the flickering black
rectangle at the top of the secondary monitor. This occurs without any
use of SDL.

Switching the monitor off and on does not fix the problem. Disconnecting
and reconnecting the monitor causes the second monitor to loose signal.
At this point, it is possible to logout and then login again. I guess
that this restarts gnome. In any case, signal to both monitors is
restored, and the black bar at the top of the second monitor has
disappeared.

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

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2074290] Re: Kernel Panic on Boot with Linux 6.8.0-39-generic

2024-07-31 Thread Lynn Smith

** Changed in: linux (Ubuntu)
   Status: Incomplete => New

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

Title:
  Kernel Panic on Boot with Linux 6.8.0-39-generic

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-07-30 Thread Jackson Smith

pps - there is also a correlation with locking and unlocking the screen
via OS_Key + L.

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

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-07-30 Thread Jackson Smith

The issue persists when MUTTER_DEBUG_FORCE_KMS_MODE=simple has been
added to /etc/environment. Note that Wayland is enabled; that is,
/etc/gdm3/custom.conf has commented out the line reading
WaylandEnable=false.

It may be relevant to note how the problem does not appear following a
fresh reboot. There is a correlation with the use of SDL2 libraries. In
fact, I am tracking down an issue in which a program that was stable in
Ubuntu 22.04 is now experiencing segmentation faults when installed on
Ubuntu 24.04.

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

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-07-30 Thread Jackson Smith

ps - I should have mentioned that the program faults when using an older
version of libSDL2-2.0.so.0.

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

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2074559] [NEW] Top margin of secondary monitor covered with black flickering rectangle

2024-07-29 Thread Jackson Smith

Public bug reported:

The system has two monitors. Workspaces are activated on the primary
monitor, but not the second. A custom background image is used on both
monitor desktops. Windows created on primary monitor then moved to
secondary e.g. firefox. Window moved towards top of secondary monitor.
However, window is clipped. Background image is also clipped. The
clipped area is about one eighth of the monitor, from the top, and spans
the full area from left to right.

$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 29 15:35:05 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. TU116 [GeForce GTX 1660 SUPER] [3842:1068]
InstallationDate: Installed on 2024-07-29 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: To Be Filled By O.E.M. Z590 Phantom Gaming 4
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=01105987-3c51-4daa-947e-0b4af195e3a6 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P2.10
dmi.board.name: Z590 Phantom Gaming 4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.10:bd10/21/2021:br5.19:svnToBeFilledByO.E.M.:pnZ590PhantomGaming4:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: Z590 Phantom Gaming 4
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug noble ubuntu wayland-session

** Attachment added: "Movie that shows flickering black rectangle at top of 
monitor."
   
https://bugs.launchpad.net/bugs/2074559/+attachment/5801216/+files/VID_20240729_153047814~2.mp4

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

Title:
  Top margin of secondary monitor covered with black flickering
  rectangle

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


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

[Bug 2074290] Re: Kernel Panic on Boot with Linux 6.8.0-39-generic

2024-07-29 Thread Lynn Smith

yes, linux-modules-extra-6.8.0-39-generic is installed.

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

Title:
  Kernel Panic on Boot with Linux 6.8.0-39-generic

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


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

[Bug 2074290] [NEW] Kernel Panic on Boot with Linux 6.8.0-39-generic

2024-07-28 Thread Lynn Smith

Public bug reported:

After updating to the kernel version 6.8.0-39-generic, my system fails
to boot, displaying the following error messages:

/dev/root: can't open blockdev
VFS cannot open root device /dev/nvme0n1p2 or unknown-block error -6
Please append a correct root= boot option: here are the available partitions:
...
Kernel panic - not syncing VFS unable to mount root fs on unknown-block
Cpu 8pid 1comm ...

Booting into the previous kernel version 6.8.0-38-generic works without
issues.

Steps to Reproduce:

Boot into the latest kernel (6.8.0-39 recovery mode).
Observe the kernel panic and error messages.
Reboot and select the previous kernel (6.8.0-38-generic) from the GRUB menu.
System boots successfully.
System Information:

Ubuntu Version: Ubuntu 24.04 LTS x86_64
Kernel Version: 6.8.0-39-generic (problematic), 6.8.0-38-generic (working)
Hardware: [Attached]

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-38-generic 6.8.0-38.38
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:lynnux 2831 F pipewire
 /dev/snd/controlC0:  lynnux 2837 F wireplumber
 /dev/snd/controlC1:  lynnux 2837 F wireplumber
 /dev/snd/controlC2:  lynnux 2837 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 28 10:19:19 2024
InstallationDate: Installed on 2024-06-02 (56 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Gigabyte Technology Co., Ltd. B550 AORUS PRO AC
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic 
root=UUID=370a2f8e-0951-4a14-9a28-8dabee36caa4 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.8.0-38-generic N/A
 linux-backports-modules-6.8.0-38-generic  N/A
 linux-firmware20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F16c
dmi.board.asset.tag: Default string
dmi.board.name: B550 AORUS PRO AC
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF16c:bd03/23/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSPROAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSPROAC:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B550 MB
dmi.product.name: B550 AORUS PRO AC
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug noble wayland-session

** Attachment added: "Hardware info (if needed)"
   
https://bugs.launchpad.net/bugs/2074290/+attachment/5800856/+files/hardware_info.txt

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

Title:
  Kernel Panic on Boot with Linux 6.8.0-39-generic

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


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

[Bug 2069391] Re: debsums reports file changed /usr/lib/systemd/system/cloud-init.service

2024-07-18 Thread Chad Smith

1. Confirmed diff from packaged cloud-init.service and override
root@lcd-o:~# diff -urN /lib/systemd/system/cloud-init.service 
/etc/systemd/system/cloud-init.service
--- /lib/systemd/system/cloud-init.service  2024-06-26 18:30:42.0 
+
+++ /etc/systemd/system/cloud-init.service  2024-07-18 21:37:31.201082523 
+
@@ -1,3 +1,6 @@
+# Based on cloud-init 24.2 for Desktop LiveCD
+# Redact sysinit.target from Before, add After=NetworkManager*.service
+# (LP: #2008952)
 [Unit]
 # https://cloudinit.readthedocs.io/en/latest/explanation/boot.html
 Description=Cloud-init: Network Stage
@@ -8,11 +11,12 @@
 After=cloud-init-local.service
 After=systemd-networkd-wait-online.service
 After=networking.service
+After=NetworkManager.service NetworkManager-wait-online.service
 Before=network-online.target
 Before=sshd-keygen.service
 Before=sshd.service
 Before=systemd-user-sessions.service
-Before=sysinit.target
+# Before=sysinit.target Redacted due to NetworkManager.service dbus depends
 Before=shutdown.target
 Conflicts=shutdown.target
 ConditionPathExists=!/etc/cloud/cloud-init.disabled

2. Confirmed override shows up properly via systemctl show same functional 
cloud-init.service deltas
 WantedBy=cloud-init.target cloud-config.target
 Conflicts=shutdown.target
-Before=network-online.target sysinit.target cloud-config.target 
sshd-keygen.service systemd-user-sessions.service shutdown.target sshd.service
-After=cloud-init-local.service systemd-networkd-wait-online.service 
systemd-journald.socket system.slice networking.service
+Before=sshd.service shutdown.target cloud-config.target 
systemd-user-sessions.service network-online.target sshd-keygen.service
+After=NetworkManager-wait-online.service cloud-init-local.service system.slice 
systemd-journald.socket networking.service systemd-networkd-wait-online.service 
NetworkManager.service
 Description=Cloud-init: Network Stage
 LoadState=loaded
 ActiveState=active
 FreezerState=running
 SubState=exited

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

Title:
  debsums reports file changed /usr/lib/systemd/system/cloud-
  init.service

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


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

[Bug 2069391] Re: debsums reports file changed /usr/lib/systemd/system/cloud-init.service

2024-07-18 Thread Chad Smith

Thanks @alberto. I confirmed the following:


The question of whether apt upgrade would show us the Files changed prompt 
which would break unattended upgrades. The answer is we don't have to worry 
about it because apt upgrade only reacts to changes in files registered by the 
deb package as conffiles. Any other non-conffiles are not monitored for that 
change  dialog.  From dpkg --status cloud-init or directly at 
/var/lib/dpkg/info/cloud-init.conffiles we can see that our registered 
conffiles all live under /etc, so the fact that livecd-rootfs has a modified 
/lib/systemd/system/cloud-init.service conf doesn't register for apt upgrade 
type config changed dialogs.That said, any modified path installed which 
has an md5sum listed in /var/lib/dpkg/info/cloud-init.md5sums would be noted by 
 debsums -c if the md5sum changes on those files. 


So, there is nothing in cloud-init upstream packaging to do here related to 
this fix because a modified /lib/systemd/system/cloud-init.service doesn't 
trigger that prompt on apt upgrade or unattended upgrades.

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

Title:
  debsums reports file changed /usr/lib/systemd/system/cloud-
  init.service

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


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

[Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen

2024-07-17 Thread Tom Smith

I tested 5.15.0-116 on a HP ProDesk 405 G6 Desktop running Mint 20.1 (using 
linux-hwe for the 5.15 kernel) and 5.15.0-116 resolved the problem. Thanks all 
:)
(Now I just have to wait for it to hit general release so I can update the 
other 20 or so I'm responsible for ;)

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

Title:
  AMD GPUs fail with null pointer dereference when IOMMU enabled,
  leading to black screen

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


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

[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy and noble

2024-07-16 Thread Chad Smith

@andreas thank you for the review here.

We resolved my cut-n-paste issues in debian/changelog and have redacted
the duplicated entries pulled up from a prior debian/changelog section.

The superfluous d/p/chad was due to snap-shotting from a local
development branch instead of our public downstream branch at
https://github.com/canonical/cloud-init/tree/ubuntu/jammy.

All queued unapproved uploads should be resolved as of 2024-07-11 and we
would like to seek additional review if possible.

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

Title:
  sru cloud-init (24.2 update) to focal, jammy and noble

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


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

[Bug 2069391] Re: debsums reports file changed /usr/lib/systemd/system/cloud-init.service

2024-07-16 Thread Chad Smith

@Dan Bungert. Since this was my changeset, I thought I'd put up a PR as food 
for thought which uses the override that Brett mentioned. It avoids the 
wholesale replacement of the entire unit file and just addresses Before and 
After config in the supplemental override file.
 
I also updated the After snapshot to align with cloud-init 24.2 which added a 
Before=systemd-user-sessions.service

https://code.launchpad.net/~chad.smith/livecd-rootfs/+git/livecd-
rootfs/+merge/469479


Note that cloud-init SRU of 24.2 is queued in unapproved queue for focal/jammy 
and noble 
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2071762

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

Title:
  debsums reports file changed /usr/lib/systemd/system/cloud-
  init.service

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


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

[Bug 2073166] [NEW] Please update to 20240701.00

Public bug reported:

Following on from previous similar package update requests @ LP:
#2043001, LP: #1995620, LP: #1944718 and LP: #1938289, this bug is a
request to update the google-compute-engine-oslogin package to the
upstream version `20240701.00` @
https://github.com/GoogleCloudPlatform/guest-
oslogin/releases/tag/20240701.00

This package has an SRU exception @
https://wiki.ubuntu.com/StableReleaseUpdates#google-compute-engine-
oslogin including an ageing exception detailed @
https://wiki.ubuntu.com/google-compute-engine-oslogin-Updates

[Impact]

This package is provided by Google for installation within guests that
run on Google Compute Engine. It is part of a collection of tools and
daemons, that ensure that the Ubuntu images published to GCE run
properly on their platform.

Cloud platforms evolve at a rate that can't be handled in six-month
increments, and they will often develop features that they would like to
be available to customers who don't want to upgrade from earlier Ubuntu
releases. As such, updating this package to more recent upstream
releases is required within all Ubuntu releases, so they continue to
function properly in their environment.

[Test Case]

When a new version of this package is uploaded to -proposed, the
following will happen:

 * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
 * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

If all the testing indicates that the image containing the new package
is acceptable, verification will be considered to be done.

[Vendored Dependency]

There a no re-vendored dependencies (in oracular/devel anyway)

[Where Problems Could Occur]

There are many upstream changes in `20240701.00-0ubuntu1` vs.
`20231004.00-0ubuntu5`; however between the guest-test-infra suite [0]
(which is run for validation by CPC _and_ Google) and CPC's own internal
test harness (CTF), there is confidence that most if not all "edge
cases" and/or obvious regressions concerns can be dismissed before the
new version lands in `-updates`

[Other Information]

This bug is used for tracking of releasing the new upstream version for
all supported series, as per the approved policy mentioned in the
following MRE:

https://wiki.ubuntu.com/google-compute-engine-oslogin-Updates

The updated package is not built for armhf and riscv64 due to upstream
regressions but the package is not used on those architectures thus
please release the SRU without the armhf and risc64 binaries.

The package does not build for powerpc on Xenial, but this is OK since
it is not used on powerpc either.

[0]: https://github.com/GoogleCloudPlatform/guest-test-infra

** Affects: google-compute-engine-oslogin (Ubuntu)
 Importance: Undecided
 Assignee: Chloé Smith (kajiya)
 Status: New

** Changed in: google-compute-engine-oslogin (Ubuntu)
 Assignee: (unassigned) => Chloé Smith (kajiya)

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

Title:
  Please update to 20240701.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/2073166/+subscriptions


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

[Bug 2073164] [NEW] Please update to 20240607.00

Public bug reported:

Following on from previous similar package update requests @ LP:
#2066314, LP: #2033061, LP: #2020770 and LP: #1973159 this bug is a
request to update gce-compute-image-packages to the upstream version
`20240607.00` @ https://github.com/GoogleCloudPlatform/guest-
configs/releases/tag/20240607.00

This package has an SRU exception @
https://wiki.ubuntu.com/StableReleaseUpdates#gce-compute-image-packages
including an ageing exception detailed @ https://wiki.ubuntu.com/gce-
compute-image-packages-Updates

[Impact]

This package is provided by Google for installation within guests that
run on Google Compute Engine. It is part of a collection of tools and
daemons, that ensure that the Ubuntu images published to GCE run
properly on their platform.

Cloud platforms evolve at a rate that can't be handled in six-month
increments, and they will often develop features that they would like to
be available to customers who don't want to upgrade from earlier Ubuntu
releases. As such, updating this package to more recent upstream
releases is required within all Ubuntu releases, so they continue to
function properly in their environment.

[Test Case]

When a new version of this package is uploaded to -proposed, the
following will happen:

 * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
 * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

If all the testing indicates that the image containing the new package
is acceptable, verification will be considered to be done.

[Vendored Dependency]

There a no re-vendored dependencies (in oracular/devel anyway)

[Where Problems Could Occur]

There are many upstream changes in `20240607.00-0ubuntu1` vs.
`20240307.00-0ubuntu1`; however between the guest-test-infra suite [0]
(which is run for validation by CPC _and_ Google) and CPC's own internal
test harness (CTF), there is confidence that most if not all "edge
cases" and/or obvious regressions concerns can be dismissed before the
new version lands in `-updates`

[Other Information]

This bug is used for tracking of releasing the new upstream version for
all supported series, as per the approved policy mentioned in the
following MRE:

https://wiki.ubuntu.com/gce-compute-image-packages-Updates

The updated package is not built for armhf and riscv64 due to upstream
regressions but the package is not used on those architectures thus
please release the SRU without the armhf and risc64 binaries.

The package does not build for powerpc on Xenial, but this is OK since
it is not used on powerpc either.

[0]: https://github.com/GoogleCloudPlatform/guest-test-infra

** Affects: gce-compute-image-packages (Ubuntu)
 Importance: Undecided
 Assignee: Chloé Smith (kajiya)
 Status: New

** Changed in: gce-compute-image-packages (Ubuntu)
 Assignee: (unassigned) => Chloé Smith (kajiya)

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

Title:
  Please update to 20240607.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2073164/+subscriptions


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

[Bug 2073163] [NEW] Please update to 20240701.00

Public bug reported:

Following on from previous similar package update requests @ LP:
#2040945, LP: #2018272 and LP: #1959392, this bug is a request to update
the google-guest-agent package to the upstream version `20240701.00` @
https://github.com/GoogleCloudPlatform/guest-
agent/releases/tag/20240701.00

This package has an SRU exception @
https://wiki.ubuntu.com/StableReleaseUpdates#google-guest-agent
including an ageing exception detailed @ https://wiki.ubuntu.com/google-
guest-agent-Updates

[Impact]

This package is provided by Google for installation within guests that
run on Google Compute Engine. It is part of a collection of tools and
daemons, that ensure that the Ubuntu images published to GCE run
properly on their platform.

Cloud platforms evolve at a rate that can't be handled in six-month
increments, and they will often develop features that they would like to
be available to customers who don't want to upgrade from earlier Ubuntu
releases. As such, updating this package to more recent upstream
releases is required within all Ubuntu releases, so they continue to
function properly in their environment.

[Test Case]

When a new version of this package is uploaded to -proposed, the
following will happen:

 * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
 * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

If all the testing indicates that the image containing the new package
is acceptable, verification will be considered to be done.

[Vendored Dependency]

## Add notes here Chlo ##

[Where Problems Could Occur]

There are many upstream changes in `20240701.00-0ubuntu1` vs.
`20240213.00-0ubuntu4`; however between the guest-test-infra suite [0]
(which is run for validation by CPC _and_ Google) and CPC's own internal
test harness (CTF), there is confidence that most if not all "edge
cases" and/or obvious regressions concerns can be dismissed before the
new version lands in `-updates`

[Other Information]

This bug is used for tracking of releasing the new upstream version for
all supported series, as per the approved policy mentioned in the
following MRE:

https://wiki.ubuntu.com/google-guest-agent-Updates

The updated package is not built for armhf and riscv64 due to upstream
regressions but the package is not used on those architectures thus
please release the SRU without the armhf and risc64 binaries.

The package does not build for powerpc on Xenial, but this is OK since
it is not used on powerpc either.

[0]: https://github.com/GoogleCloudPlatform/guest-test-infra

** Affects: google-guest-agent (Ubuntu)
 Importance: Undecided
 Assignee: Chloé Smith (kajiya)
 Status: New

** Changed in: google-guest-agent (Ubuntu)
 Assignee: (unassigned) => Chloé Smith (kajiya)

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

Title:
  Please update to 20240701.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2073163/+subscriptions


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

[Bug 2073161] [NEW] Please update to 20240524.03

Public bug reported:

Following on from previous similar package update requests @ LP:
#2064580 LP: #2020762, LP: #1996735, LP: #1938553 and LP: #1911689, this
bug is a request to update the google-osconfig-agent package to the
upstream version `20240524.03` @
https://github.com/GoogleCloudPlatform/osconfig/releases/tag/20240524.03

This package has an SRU exception @
https://wiki.ubuntu.com/StableReleaseUpdates#google-osconfig-agent
including an ageing exception detailed @ https://wiki.ubuntu.com/google-
osconfig-agent-Updates

[Impact]

This package is provided by Google for installation within guests that
run on Google Compute Engine. It is part of a collection of tools and
daemons, that ensure that the Ubuntu images published to GCE run
properly on their platform.

Cloud platforms evolve at a rate that can't be handled in six-month
increments, and they will often develop features that they would like to
be available to customers who don't want to upgrade from earlier Ubuntu
releases. As such, updating this package to more recent upstream
releases is required within all Ubuntu releases, so they continue to
function properly in their environment.

[Test Case]

When a new version of this package is uploaded to -proposed, the
following will happen:

 * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
 * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

If all the testing indicates that the image containing the new package
is acceptable, verification will be considered to be done.

[Vendored Dependency]

In this update there are no re-vendored dependencies (for oracular/devel
anyway)

[Where Problems Could Occur]

There are many upstream changes in `20240320.00-0ubuntu2` vs.
`20240524.03-0ubuntu1`; however between the guest-test-infra suite [0]
(which is run for validation by CPC _and_ Google) and CPC's own internal
test harness (CTF), there is confidence that most if not all "edge
cases" and/or obvious regressions concerns can be dismissed before the
new version lands in `-updates`

[Other Information]

This bug is used for tracking of releasing the new upstream version for
all supported series, as per the approved policy mentioned in the
following MRE:

https://wiki.ubuntu.com/google-osconfig-agent-Updates

The updated package is not built for armhf and riscv64 due to upstream
regressions but the package is not used on those architectures thus
please release the SRU without the armhf and risc64 binaries.

The package does not build for powerpc on Xenial, but this is OK since
it is not used on powerpc either.

[0]: https://github.com/GoogleCloudPlatform/guest-test-infra

** Affects: google-osconfig-agent (Ubuntu)
 Importance: Undecided
 Assignee: Chloé Smith (kajiya)
 Status: New

** Changed in: google-osconfig-agent (Ubuntu)
 Assignee: (unassigned) => Chloé Smith (kajiya)

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

Title:
  Please update to 20240524.03

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2073161/+subscriptions


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

[Bug 2067886] Re: Remove the XFS /boot upgrade check for noble

2024-07-08 Thread Phillip Smith

This appears to still be blocking 22.04 to 24.04 upgrades.

With `do-release-upgrade -d` I get the original error:


  Cannot upgrade this system

  Due to a bug in grub, this system cannot be safely upgraded at this
time.

  See https://launchpad.net/bugs/2039172.


With `do-release-upgrade -p` it tries to upgrade to 23.10 instead of
24.04

I have installed all available updates, include python3-update-manager
ubuntu-minimal ubuntu-server ubuntu-standard update-manager-core which
were "kept back"

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

Title:
  Remove the XFS /boot upgrade check for noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2067886/+subscriptions


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

[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy, mantic and noble

** Description changed:

  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:
  
   - feat: Add support for FTP and FTP over TLS (#4834)
   - feature(schema): add networkv2 schema (#4892)
   - feat: Add new distro 'azurelinux' for Microsoft Azure Linux. (#4931)
   - feat: Use NetworkManager renderer by default in RHEL family
   - feat(ca_certs): Add AlmaLinux OS and CloudLinux OS support (#5264)
   - feat(sysconfig): Add DNS from interface config to resolv.conf (#5401)
   - feat(alpine): add support for Busybox adduser/addgroup (#5176)
   - feat(disk_setup): Add support for nvme devices (#5263)
   - fix: Make DataSourceOracle more resilient to early network issues (LP: 
#2056194)
   - bug(wait_for_url): when exceptions occur url is unset, use url_exc
     (LP: #2055077)
   - bug(vmware): initialize new DataSourceVMware attributes at unpickle
     (#5021) (LP: #2056439)
   - bug(maas): register the correct DatasourceMAASLocal in init-local
     (#5068) (LP: #2057763)
   - fix(net): klibc ipconfig PROTO compatibility (#5437)
     [Alexsander de Souza] (LP: #2065787)
   - fix(snapd): ubuntu do not snap refresh when snap absent (LP: #2064300)
  
  Downstream Packaging changes:
   - downstream ubuntu packaging will now pin a feature 
DEPRECATION_INFO_BOUNDARY to match the first version of cloud-init released on 
each series. This boundary gates whether cloud-init will raise only INFO level 
logs or DEPRECATED logs (which result in an exit 2 on cloud-init status) based 
on whether the defined deprecation_version defined for each key in json schema.
  
   - drop all debian/cpick-* patches now included due to pulling all commits 
from upstream
   - drop package dependency on netifaces
   - logrotate config added
   - enable WSL datasource for discovery
   - shuffle common logic for apport out of debian/apport-general-hook.py and 
into the main repo to get better test coverage.
   - drop now unnecessary d/p/do-not-block-user-login.patch because upstream 
systemd ordering now aligns with previous downstream unit ordering
-  - Focal-only: redact unsupported ConditionEnvironment config from hotplug 
units. systemd in focal doesn't support this key anyway which results in a 
warning log in journalctl.
- 
- This allows stable releases to retain original behavior for keys which
- are recently deprecated in a newer version of cloud-init.
+  - Focal-only: redact unsupported ConditionEnvironment config from hotplug 
units. systemd in focal doesn't support this key anyway which results in a 
warning log in journalctl. 
+  NOTE: This config setting was a supplemental gate in systemd units to 
prevent the individual units from being loaded in boot target if the 
environment provides "KERNEL_CMDLINE=cloud-init=disabled" and was only provided 
as a short-circuit to ds-identify which also checks for KERNEL_CMDLINE in 
/proc/cmdline during systemd generator timeframe to disable loading cloud-init 
systemd units.
+ 
+ 
+ This allows stable releases to retain original behavior for keys which are 
recently deprecated in a newer version of cloud-init.
  
  The feature.DEPRECATION_INFO_BOUNDARY for each targeted series:
     - focal: 20.1
     - jammy: 22.1
     - noble: 24.1
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates
  
  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug.  cloud-init team
  members will not mark ‘verification-done’ until this has happened.
  
  * Automated Test Results
  
  
  
  
  
  * Manual Test Results
  
  
  
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.
  
  [Discussion]
  - Given that this SRU packaging is touching systemd unit ordering we want an 
additional manual test performed to validate/assert that there is not a 
degradation to time to SSH and perceived boot time. This can likely be 
performed in KVM to aensure a clean boot scenario with and without cloud-init 
24.2 installed in the base image.
  
  [ChangeLog]
  
  24.2
   - test: Fix no default user in test_status.py (#5478)
   - fix: correct deprecated_version=22.2 for users.sudo
   - test: Add jsonschema guard in test_cc_ubuntu_pro.py (#5479)
   - fix(test): Fix pycloudlib types in integration tests (#5350)
   - fix(test): Fix ip printing for non-lxd instances (#5350)
   - chore(mypy): Drop unused missing import exclusions (#5350)
   - type: Add stub types for network v1/v2 config (#5350)
   - chore: Auto-format network jsonschema in ci (#5350)
   - fix(tox): Update tox.ini (#5350)
   - chore(typing): Remove type ignores and casts (#5350)
   - refactor(typing): Re

[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy, mantic and noble

** Description changed:

  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:
  
   - feat: Add support for FTP and FTP over TLS (#4834)
   - feature(schema): add networkv2 schema (#4892)
   - feat: Add new distro 'azurelinux' for Microsoft Azure Linux. (#4931)
   - feat: Use NetworkManager renderer by default in RHEL family
   - feat(ca_certs): Add AlmaLinux OS and CloudLinux OS support (#5264)
   - feat(sysconfig): Add DNS from interface config to resolv.conf (#5401)
   - feat(alpine): add support for Busybox adduser/addgroup (#5176)
   - feat(disk_setup): Add support for nvme devices (#5263)
   - fix: Make DataSourceOracle more resilient to early network issues (LP: 
#2056194)
   - bug(wait_for_url): when exceptions occur url is unset, use url_exc
     (LP: #2055077)
   - bug(vmware): initialize new DataSourceVMware attributes at unpickle
     (#5021) (LP: #2056439)
   - bug(maas): register the correct DatasourceMAASLocal in init-local
     (#5068) (LP: #2057763)
   - fix(net): klibc ipconfig PROTO compatibility (#5437)
     [Alexsander de Souza] (LP: #2065787)
   - fix(snapd): ubuntu do not snap refresh when snap absent (LP: #2064300)
  
  Downstream Packaging changes:
   - downstream ubuntu packaging will now pin a feature 
DEPRECATION_INFO_BOUNDARY to match the first version of cloud-init released on 
each series. This boundary gates whether cloud-init will raise only INFO level 
logs or DEPRECATED logs (which result in an exit 2 on cloud-init status) based 
on whether the defined deprecation_version defined for each key in json schema.
  
   - drop all debian/cpick-* patches now included due to pulling all commits 
from upstream
-  - drop package dependency on netifaces
+  - drop package dependency on netifaces
   - logrotate config added
   - enable WSL datasource for discovery
   - shuffle common logic for apport out of debian/apport-general-hook.py and 
into the main repo to get better test coverage.
   - drop now unnecessary d/p/do-not-block-user-login.patch because upstream 
systemd ordering now aligns with previous downstream unit ordering
+  - Focal-only: redact unsupported ConditionEnvironment config from hotplug 
units. systemd in focal doesn't support this key anyway which results in a 
warning log in journalctl.
  
  This allows stable releases to retain original behavior for keys which
  are recently deprecated in a newer version of cloud-init.
  
  The feature.DEPRECATION_INFO_BOUNDARY for each targeted series:
     - focal: 20.1
     - jammy: 22.1
     - noble: 24.1
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates
  
  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug.  cloud-init team
  members will not mark ‘verification-done’ until this has happened.
  
  * Automated Test Results
  
  
  
  
  
  * Manual Test Results
  
  
  
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.
  
  [Discussion]
  - Given that this SRU packaging is touching systemd unit ordering we want an 
additional manual test performed to validate/assert that there is not a 
degradation to time to SSH and perceived boot time. This can likely be 
performed in KVM to aensure a clean boot scenario with and without cloud-init 
24.2 installed in the base image.
  
  [ChangeLog]
  
  24.2
   - test: Fix no default user in test_status.py (#5478)
   - fix: correct deprecated_version=22.2 for users.sudo
   - test: Add jsonschema guard in test_cc_ubuntu_pro.py (#5479)
   - fix(test): Fix pycloudlib types in integration tests (#5350)
   - fix(test): Fix ip printing for non-lxd instances (#5350)
   - chore(mypy): Drop unused missing import exclusions (#5350)
   - type: Add stub types for network v1/v2 config (#5350)
   - chore: Auto-format network jsonschema in ci (#5350)
   - fix(tox): Update tox.ini (#5350)
   - chore(typing): Remove type ignores and casts (#5350)
   - refactor(typing): Remove unused code paths (#5350)
   - fix(typing): Add / update type annotations (#5350)
   - fix(typing): Remove type annotation for unused variable (#5350)
   - fix(typing): Remove invalid type annotations (#5350)
   - ci(mypy): Set default follow_imports value (#5350)
   - test: Update integration tests to pass on focal (#5476)
   - tests: update ubuntu_pro test to account for info-level deprecations
     (#5475)
   - tests: update nocloud deprecation test for boundary version (#5474)
   - fix(rh_subscription): add string type to org (#5453)
   - tests: integration tests aware of features.DEPRECATION_INFO_BOUNDARY
   - tests: update keyserver PPA key fur curtin-dev (#

[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy, mantic and noble

** Description changed:

  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:
  
   - feat: Add support for FTP and FTP over TLS (#4834)
   - feature(schema): add networkv2 schema (#4892)
   - feat: Add new distro 'azurelinux' for Microsoft Azure Linux. (#4931)
   - feat: Use NetworkManager renderer by default in RHEL family
   - feat(ca_certs): Add AlmaLinux OS and CloudLinux OS support (#5264)
   - feat(sysconfig): Add DNS from interface config to resolv.conf (#5401)
   - feat(alpine): add support for Busybox adduser/addgroup (#5176)
   - feat(disk_setup): Add support for nvme devices (#5263)
   - fix: Make DataSourceOracle more resilient to early network issues (LP: 
#2056194)
   - bug(wait_for_url): when exceptions occur url is unset, use url_exc
     (LP: #2055077)
   - bug(vmware): initialize new DataSourceVMware attributes at unpickle
     (#5021) (LP: #2056439)
   - bug(maas): register the correct DatasourceMAASLocal in init-local
     (#5068) (LP: #2057763)
   - fix(net): klibc ipconfig PROTO compatibility (#5437)
     [Alexsander de Souza] (LP: #2065787)
   - fix(snapd): ubuntu do not snap refresh when snap absent (LP: #2064300)
  
  Downstream Packaging changes:
   - downstream ubuntu packaging will now pin a feature 
DEPRECATION_INFO_BOUNDARY to match the first version of cloud-init released on 
each series. This boundary gates whether cloud-init will raise only INFO level 
logs or DEPRECATED logs (which result in an exit 2 on cloud-init status) based 
on whether the defined deprecation_version defined for each key in json schema.
  
-  - drop package dependency on netifaces
+  - drop all debian/cpick-* patches now included due to pulling all commits 
from upstream
+  - drop package dependency on netifaces
   - logrotate config added
   - enable WSL datasource for discovery
   - shuffle common logic for apport out of debian/apport-general-hook.py and 
into the main repo to get better test coverage.
   - drop now unnecessary d/p/do-not-block-user-login.patch because upstream 
systemd ordering now aligns with previous downstream unit ordering
  
  This allows stable releases to retain original behavior for keys which
  are recently deprecated in a newer version of cloud-init.
  
  The feature.DEPRECATION_INFO_BOUNDARY for each targeted series:
     - focal: 20.1
     - jammy: 22.1
     - noble: 24.1
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates
  
  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug.  cloud-init team
  members will not mark ‘verification-done’ until this has happened.
  
  * Automated Test Results
  
  
  
  
  
  * Manual Test Results
  
  
  
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.
  
  [Discussion]
  - Given that this SRU packaging is touching systemd unit ordering we want an 
additional manual test performed to validate/assert that there is not a 
degradation to time to SSH and perceived boot time. This can likely be 
performed in KVM to aensure a clean boot scenario with and without cloud-init 
24.2 installed in the base image.
  
- 
  [ChangeLog]
- 
  
  24.2
   - test: Fix no default user in test_status.py (#5478)
   - fix: correct deprecated_version=22.2 for users.sudo
   - test: Add jsonschema guard in test_cc_ubuntu_pro.py (#5479)
   - fix(test): Fix pycloudlib types in integration tests (#5350)
   - fix(test): Fix ip printing for non-lxd instances (#5350)
   - chore(mypy): Drop unused missing import exclusions (#5350)
   - type: Add stub types for network v1/v2 config (#5350)
   - chore: Auto-format network jsonschema in ci (#5350)
   - fix(tox): Update tox.ini (#5350)
   - chore(typing): Remove type ignores and casts (#5350)
   - refactor(typing): Remove unused code paths (#5350)
   - fix(typing): Add / update type annotations (#5350)
   - fix(typing): Remove type annotation for unused variable (#5350)
   - fix(typing): Remove invalid type annotations (#5350)
   - ci(mypy): Set default follow_imports value (#5350)
   - test: Update integration tests to pass on focal (#5476)
   - tests: update ubuntu_pro test to account for info-level deprecations
     (#5475)
   - tests: update nocloud deprecation test for boundary version (#5474)
   - fix(rh_subscription): add string type to org (#5453)
   - tests: integration tests aware of features.DEPRECATION_INFO_BOUNDARY
   - tests: update keyserver PPA key fur curtin-dev (#5472)
   - test: Fix deprecation test failures (#5466)
   - chore: fix schema.py formatting (#5465)
   - fix: dont double-log deprecated INFOs (#5465)
   - fix(test): Mock ver

[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy, mantic and noble