In addition to the verification tests performed on the specific bugs, I performed some additional testing for this top-level SRU bug.
Using version 26.02.2-0ubuntu1~22.04.1 on jammy and 26.02.2-0ubuntu1~24.04.1 on noble, I attached a Pro token to each client, and pro-enabled landscape. On noble, this succeeded, and the client registered. On jammy, this failed because "Landscape cannot be enabled via Pro Client on Ubuntu 22.04 and earlier", a limitation of pro-client, not landscape. Manual registration of the jammy client worked around this. I validated that both clients properly reported Ubuntu Pro information to Landscape Server, and were appropriately licensed. Message exchanges, including package reporting, progress normally. I also tested upgrading from the previous version on both clients. Both upgraded cleanly, still registered, service active, exchanging with Landscape Server without re-registering. I also tested pro-disabling landscape on the noble client, then re- enabling it, which succeeded and persisted config. I also tested dispatching a "change Pro token" activity for the noble client. This succeeded without disruption. ** Tags removed: verification-needed-jammy verification-needed-noble ** Tags added: 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/2143088 Title: [SRU] Update noble, jammy to landscape-client 26.02.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/2143088/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
