** Summary changed:
- Mutli-nic ENI rendering fails if ENI activator not used
+ EC2 multi-nic ENI rendering fails if ENI activator not used
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066985
** Summary changed:
- cloud-init network fails in ipv6-only subnet with multi-NICs
+ EC2: cloud-init network fails in ipv6-only subnet with multi-NICs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
sru validation complete noble
csmith@downtown:~$ bash ./sru-2064132.sh
+ cat
+ cat
+ for SERIES in "noble"
+ echo '-- SRU verification: noble'
-- SRU verification: noble
+ name=test-no-snap-noble
+ lxc launch ubuntu-daily:noble test-no-snap-noble
Creating
=== SRU verification complete jammy ===
csmith@downtown:~$ bash ./sru-2064132.sh
+ cat
+ cat
+ for SERIES in "jammy"
+ echo '-- SRU verification: jammy'
-- SRU verification: jammy
+ name=test-no-snap-jammy
+ lxc launch ubuntu-daily:jammy test-no-snap-jammy
Creating
focal SRU verification complete ===
echo '-- SRU verification: focal'
-- SRU verification: focal
+ name=test-no-snap-focal
+ lxc launch ubuntu-daily:focal test-no-snap-focal
Creating test-no-snap-focal
Starting test-no-snap-focal
+ sleep 6
+ lxc exec test-no-snap-focal --
# verification complete mantic #
csmith@midtown:~$ lxc launch ubuntu-daily:mantic test-m
Creating test-m
Starting test-m file push myfile.yaml
csmith@midtown:~$ lxc file push myfile.yaml test-m/
csmith@midtown:~$ lxc file push setup_proposed.sh test-m/
test verification complete jammy
csmith@midtown:~$ lxc launch ubuntu-daily:jammy test-jammy
Creating test-jammy
Starting test-jammy
csmith@midtown:~$ lxc file push myfile.yaml test-jammy/
csmith@midtown:~$ lxc file push setup_proposed.sh test-jammy/
Thanks Timo!
focal verification complete =
csmith@midtown:~$ lxc launch ubuntu-daily:focal test-focal
Creating test-focal
Starting test-focal
csmith@midtown:~$ lxc exec test-focal bash
root@test-focal:~# hostname # confirm test-focal from standard meta-data
test-focal
root@test-focal:~#
This fix is also uploaded for SRU to noble in cloud-init version
24.1.3-0ubuntu3.2
** Tags removed: verification-needed-focal verification-needed-jammy
verification-needed-mantic verification-needed-noble
** Tags added: verification-failed-focal verification-failed-jammy
** Tags added: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064132
Title:
images without snapd installed error on `upgrade_packages: true` user-
data
To manage
Upload to oracular 24.2~2g51c6569f-0ubuntu1 released upstream commit
51c6569f96bee4f91aad5db58765c7abab7ffcdf which resolves this issue.
Uploads are in the unapproved queue which resolve the SRU verification failures
discovered in comment #13:
- mantic: 24.1.3-0ubuntu1~23.10.5
- jammy:
mantic verification complete
csmith@midtown:~$ lxc launch ubuntu-daily:mantic test-mantic
Creating test-mantic
Starting test-mantic
csmith@midtown:~$ lxc file push myfile.yaml test-mantic/
csmith@midtown:~$ lxc file push setup_proposed.sh test-mantic/
csmith@midtown:~$ lxc exec
= jammy verification complete
csmith@midtown:~$ lxc launch ubuntu-daily:jammy test-jammy
Creating test-jammy
Starting test-jammy
csmith@midtown:~$ lxc file push myfile.yaml test-jammy/
csmith@midtown:~$ lxc file push setup_proposed.sh test-jammy/
csmith@midtown:~$ lxc exec test-jammy bash
focal verification complete
csmith@midtown:~$ lxc file push myfile.yaml test-focal/
csmith@midtown:~$ lxc exec test-focal bash
root@test-focal:~# # confirm usage failure
root@test-focal:~# cloud-init -f /myfile.yaml init
usage: /usr/bin/cloud-init [-h] [--version] [--debug] [--force]
SRU verification determined that the fix in -proposed was not complete
enough to fix the package_ugprade: true case.
Upstream commit has landed fixing this
issue:https://github.com/canonical/cloud-
init/commit/51c6569f96bee4f91aad5db58765c7abab7ffcdf
Uploads will be pushed to
Sru validation script
** Attachment removed: "sru-2064132.sh"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+attachment/5774506/+files/sru-2064132.sh
** Attachment added: "sru-2064132.sh"
** Summary changed:
- images without snapd installed error on `update_packages: true` user-data
+ images without snapd installed error on `upgrade_packages: true` user-data
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[ Impact ]
* SRU of cloud-init 24.1.3 to Focal, Jammy and Mantic introduced a
regression where cloud-init will attempt to call `snap refresh` on new
Ubuntu instance launches if the Ubuntu image does not contain snapd deb
package and optional #cloud-config
** Description changed:
[ Impact ]
* SRU of cloud-init 24.1.3 to Focal, Jammy and Mantic introduced a
regression where cloud-init will attempt to call `snap refresh` on new
Ubuntu instance launches if the Ubuntu image does not contain snapd deb
package and optional #cloud-config
** Summary changed:
- cli behavior changed
+ cli behavior changed for commands passing optional --file argument to
cloud-init init, modules or single subcommand
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Originally reported on Github[1], cloud-init released a change in the
- cli[2] that broke former cloud-init cli commands.
+ [ Impact ]
- Previously `cloud-init -f init` was allowed, but after the 24.1 SRU
release to Jammy, this broke and
+ * Environments or
** Also affects: cloud-init (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: cloud-init
Given that all Canonical Ubuntu images (including server minimal and
cloud minimal images) contain snapd deb package, this is not a critical
path concern for Canonical stable supported Ubuntu images. So,
`regression-update` tag is dropped for our specific support paths as
this doesn't regress
** Description changed:
- In Ubuntu images that do not have snapd debian package installed
- launching with the following user-data triggers cloud-init to run `snap
- refresh` when that command doesn't exist.
+ [ Impact ]
+ * SRU of cloud-init 24.1.3 to Focal, Jammy and Mantic introduced a
+
Upstream commit merged https://github.com/canonical/cloud-
init/commit/a6f7577d582aa51d51ca129fcff65313e210d47b
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Committed
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Chad Smith (chad.smith)
--
You re
Upstream github issue re-opened representing this fix:
https://github.com/canonical/cloud-init/issues/5143
upstream Pull request fixing this issue:
https://github.com/canonical/cloud-init/pull/5224
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
In Ubuntu images that do not have snapd debian package installed
launching with the following user-data triggers cloud-init to run `snap
refresh` when that command doesn't exist.
reproducer:
lxc launch ubuntu-daily:jammy test-no-snap
sleep 3
lxc exec test-no-snap --
Just because tags show verification needed. I ran through and validated
the netplan on jammy has right limited perms as root-rw and no warnings
emitted by netplan apply due to permissions
## test logs
csmith@midtown:~$ lxc launch ubuntu-daily:jammy t-j
Creating t-j
Starting t-j
csmith@midtown:~$
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059337
Title:
noble: needrestart triggering SIGTERM of cloud-final.service
Thanks Lukas: +1 on this changeset not degrading early boot install
scenarios where systemd services are ordered After=systemd-networkd-
wait-online.service
Preliminary testing on Azure platform look good with accelerated networking
enabled have confirmed dual-nic tests correctly configure the
Marking won't fix as the resolution was in needrestart not cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059337
Title:
noble: needrestart triggering SIGTERM of cloud-final.service
Closing cloud-init task for this bug as cloudimages created after
20240408 contain appropriate needrestart to defer cloud-final.service
during cloud-init package upgrade.
** Changed in: cloud-init (Ubuntu Noble)
Status: Confirmed => Won't Fix
--
You received this bug notification because
For the cloud-init element/task of this bug, before we change our
current upstream grub_dpkg debconf set-selections behavior for boot
device detection, we need to consider the following scenarios where the
absence of cloud-init grub_dpkg behavior may be insufficient.
If Ubuntu primary use-cases
Thanks Dan, on a patch for subiquity placing an /etc/cloud/cloud.cfg.d/
snippet into the target installed system. This approach will still allow
for live server/desktop install path where customers which require
cloud-init's default grub_dpkg behavior for some corner case could still
turn that
@Mate thanks for the patch suggestion and triage work here.
While this approach will work for live-server/live-desktop and or Ubuntu
cloudimage which have downstream grub2 deb fixes for handling the 'new'
grub-pc/cloud_style_intialization debconf setting, are we missing other
use-cases that will
In foundations leadership sync on this today. I believe we determined
that the best course of action we should take at the moment is to pursue
an Ubuntu downstream needrestart patch to register cloud-init system
services as skipped during automatic restarts when apt commands are run
in
** Description changed:
Recent downstream ubuntu-specific changes in needrestart version
- 3.6-7ubuntu1 [1] set Ubuntu into autorestart mode during non-interactive
+ 3.6-7ubuntu1 [1] set Ubuntu into autorestart mode when non-interactive
apt-get dist-upgrade is being performed.
This
** Summary changed:
- sru cloud-init 23.4.4 to 24.1.2
+ sru cloud-init 23.4.4 to 24.1.3
** 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
:) Thanks again David for the context on your immediate workarounds you
would pursue here in the meantime while needrestart folks determine best
course of action for Ubuntu.
While I think one solution could be hard-appending all critical or
oneshot services of the world into upstream's
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059317
Title:
> think the change at issue is adding the flags "-m u" to apt-pinvoke
in /etc/apt/apt.conf.d/99needrestart, which also means needrestart now
ignores a setting of "NEEDRESTART_MODE=l" in the environment when run
from apt.
@demyers I also saw this behavior too in initial testing and didn't
Thanks @demyers for context here too. I've just proposed the following
for cloud-final.service that seems to work on my side when testing in
lxd
https://code.launchpad.net/~chad.smith/ubuntu/+source/needrestart/+git/needrestart/+merge/463236
** Description changed:
Recent downstream
Public bug reported:
Recent downstream ubuntu-specific changes in needrestart version
3.6-7ubuntu1 [1] set Ubuntu into autorestart mode during non-interactive
apt-get dist-upgrade is being performed.
This causes an acute issue for cloud-init when #cloud-config user-data tries to
perform
** Summary changed:
- sru cloud-init 23.4.4 to 24.1
+ sru cloud-init 23.4.4 to 24.1.2
** 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
+1 I confirmed yesterday as well. subiquity no longer calls cloud-init's
stages.Init() when cloud-init is disabled. This was the source of the
delay originally which performed all that rediscovery of every cloud-
init datasource, including Ec2. Full install with cloud-init disabled on
default
** Summary changed:
- sru cloud-init 23.4.4 to 24.1.1
+ sru cloud-init 23.4.4 to 24.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056100
Title:
sru cloud-init 23.4.4 to 24.1
To manage
https://github.com/canonical/cloud-init/pull/4994 just merged for cloud-
init to fix inconclusive logging of 'None'. Expect cloud-init logs in
this regard to be fixed in 24.2 and/or next "bugfix release" of cloud-
init into Noble.
** Changed in: cloud-init (Ubuntu)
Status: In Progress =>
Excellent to hear that worked for you. Thanks again for filing a bug to
alert us of this issue and I'm glad this resolved your concerns.
** Changed in: cloud-init (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you so much for filing the bug and making cloud-init better.
From the provided traceback, it looks like this is a private DataSourceUI that
isn't upstream in cloud-init importing getLogger from cloudinit.log which no
longer exists in our upstream repository as of commit
Better logging from cloud-init to fix the 'None' warning
https://github.com/canonical/cloud-init/pull/4994
** Changed in: cloud-init (Ubuntu)
Status: Invalid => In Progress
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Chad Smith (chad.smith)
--
You received th
** Changed in: livecd-rootfs (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: subiquity
Status: Invalid => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- live installer isos: cloud-init clean shell-script needs an declared
interpreter
+ live installer isos: cloud-init clean shell-script needs a declared
interpreter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: cloud-init (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/2055077
Title:
cloudinit.sources.DataSourceEc2:583 Calling 'None' failed
To manage
If we want this kind of fix for subiquity to avoid edge cases where someone
manually tries to disable cloud-init via kernel command-line params:
https://github.com/canonical/subiquity/pull/1923
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Reflecting this context to the bug instead of IRC messages.
There are a number of issues at play here:
1. edubuntu images do not provide /var/lib/cloud/seed/nocloud/user-data
or meta-data files which allow cloud-init in Ubuntu Desktop images to
detect cloud-init's NoCloud datasource.
2.
attempted commands
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Assignee: Chad Smith (chad.smith)
Status: New
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Chad Smith (chad.smith)
--
You received this bug notification because you are a mem
Thanks for filing this bug.
While we triage, it would be helpful if we can attach the results of `sudo
cloud-init collect-logs` during the installation stage to this bug?
- ideally we want to look at /run/cloud-init/ds-identify.log and the full
/var/log/cloud-init.log which will give us more
Uploads queued to focal jammy and mantic -proposed for review.
New integration tests cover this test case:
CLOUD_INIT_PLATFORM=lxd_vm tox -e integration-tests --
tests/integration_tests/datasources/test_nocloud.py::test_smbios_seed_network
Upstream PR landed fixing this issue:
https://github.com/canonical/cloud-init/commit/66b5ce9d5f94c0c6625972fdfdca3796d365b069
upstream commit with integration test for ongoing validaiton of this behavior:
https://github.com/canonical/cloud-init/commit/4b694a45db2f9043700e6a619bb943086be2f0c9
**
** 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/2055081
Title:
NoCloud SMBIOS seed broken in 23.4
To manage notifications about
Thanks for the bug and triage folks.
While this is confirmed/known behavior, I don't think cloud-init should
be automatically removing core configuration files that are not packaged
by cloud-init's deb package especially if removal of those config files
can have catastrophic consequences on the
This trace makes me think something in ppc64el image contains YAML
config that our YamlDumper can't understand. I'm curious if we have
access to dump of the files in /etc/cloud/cloud.cfg and
/etc/cloud/cloud.cfg.d/*.cfg
--
You received this bug notification because you are a member of Ubuntu
ry ppa:cloud-init-dev/daily
$ lxc exec test-jammy -- apt install cloud-init
$ lxc exec test-jammy -- DEBUG_LEVEL=2 DI_LOG=stderr
/usr/lib/cloud-init/ds-identify --force
"Found single datasource: LXD"
** Affects: cloud-init (Ubuntu)
Importance: High
Assignee: Chad Smit
sru-22.1-lxd-container-focal.log SUCCESS logs for full integration tests
on lxd-container to ensure we didn't break anything outside of this
minor changeset.
** Attachment added: "sru-22.1-lxd-container-focal.log"
Supplemental full integration test suite on bionic lxd-container to
ensure no other functionality broke
** Attachment added: "sru-22.1-lxd-container-full-tests.log"
https://bugs.launchpad.net/cloud-init/+bug/1966085/+attachment/5572719/+files/sru-22.1-lxd-container-full-tests.log
--
You
** Description changed:
[Impact]
* In environments where coud-init-generator detects no viable
datasources, cloud-init systemd units are not included in the boot
process and `cloud-init status --wait` blocks indefinitely reporting
"not run" state instead of "disabled". Utilities
Uploads queued for -proposed testing on bionic focal and impish:
verification will start once -proposed are published and accessible
$ rmadison cloud-init | grep proposed
cloud-init | 22.1-14-g2e17a0d6-0ubuntu1~18.04.2 | bionic-proposed | all
cloud-init | 22.1-14-g2e17a0d6-0ubuntu1~18.04.3 |
** Description changed:
[Impact]
- * In environments where coud-init-generator detects no viable
+ * In environments where coud-init-generator detects no viable
datasources, cloud-init systemd units are not included in the boot
process and `cloud-init status --wait` blocks indefinitely
** Description changed:
+ [Impact]
+
+ * In environments where coud-init-generator detects no viable
+ datasources, cloud-init systemd units are not included in the boot
+ process and `cloud-init status --wait` blocks indefinitely reporting
+ "not run" state instead of "disabled". Utilities
Fix released to Jammy [ubuntu/jammy-proposed] cloud-init
22.1-14-g2e17a0d6-0ubuntu1~22.04.4 (Accepted)
** Changed in: cloud-init (Ubuntu Jammy)
Status: In Progress => Fix Released
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug
Upstream fix merged at https://github.com/canonical/cloud-
init/commit/eee603294f120cf98696351433e7e6dbc9a3dbc2
** Changed in: cloud-init
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upstream fix for this posted to https://github.com/canonical/cloud-
init/pull/1349
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966085
Title:
cloud-init status --wait never returns if datasource
** Changed in: cloud-init
Status: Triaged => 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/1966085
Title:
cloud-init status --wait never returns if datasource not found
To
** Also affects: cloud-init (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Jammy)
Importance: High
Status: Triaged
** Also affects: cloud-init (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: cloud-init
Ec2 SRU tests of 22.1 from jenkins (bionic/focal/jammy) asserting success with
the proposed package
manual tests for ec2 impish proposed attached as well. Two flaky tests which
succeeded on supplemental run.
** Attachment added: "ec2-22.1-sru.tar"
** Changed in: cloud-init (Ubuntu)
Status: In Progress => 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/1859725
Title:
sru cloud-init (19.3.41 to 19.4.33) Xenial, Bionic and
This looks to also have an existing issue over in firewalld too
https://github.com/firewalld/firewalld/issues/414
** Bug watch added: github.com/firewalld/firewalld/issues #414
https://github.com/firewalld/firewalld/issues/414
--
You received this bug notification because you are a member of
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu Bionic)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu Focal)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu Impish)
Status: New => In Progress
upstream commits landed which should resolve this issue on the next
published release of cloud-init v. 22.1. Expectation is within the next
3 weeks this fix will be in daily Ubuntu images.
- upstream commit reordering LXD datasource detecting priority to after
OpenStack:
Marking subiquity project for reference tracking and information as we
better define what supported use-cases cloud-init/subiquity we need to
cover in the future. It may very will be a WON'T FIX from suquitity
point of view at the moment as this bug doesn't yet represent an
actionable feature
TLDR: generally for individuals looking to create custom Ubuntu Server
golden images, we suggest they start from a stock Ubuntu Server cloud
image instead[1] of the subiquity-based Ubuntu Server Live installer
images[2].
[1] Ubuntu Server cloud images for
Thank you for filing a bug and making Ubuntu better.
I can confirm that your procedure to reproduce on Ubuntu jammy. This does in
fact represent a bug in how the firewalld systemd unit is being setup. My first
guess here is the DefaultDependencies being injected by firewalld's systemd
service
** Changed in: cloud-init (Ubuntu)
Status: In Progress => 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/1881018
Title:
sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan
I would suggest that the Ubuntu Server Live installer ISO is not the image a
customer would want to be cloning on VMWare as the live installers isn't
currently intended for that type of use-case.
That said I think we can come to a couple of short-term solutions that "work
around" this case:
cloud-init is involved in converstations with subiquity devs this cycle
for 22.04 and will try to iron out how this should work on both Server
Live installer ISOs vs Ubuntu 22.04 (Jammy) Desktop installer ISOs. But,
at the moment it's going to be the manual process you have already
captured, plus
I was going through testing of desktop live cd images here as well and
noticed the same symptoms (which I think generally make sense for
Desktop images). But, I wanted to reflect this to subiquity project as
well as the use-case may not be captured as a user-story that is
considered "supported".
Public bug reported:
./softwareproperties/gtk/utils.py relies on presence of ua command
delivered by ubuntu-advantage-tools. This deb should probably express at
least a Recommends on ubuntu-advantage-tools.
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Also affects: subiquity
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/1871975
Title:
network configuration is disabled by default in cloud-init for
# Success testing on Bionic Desktop installer
1. Validate current behavior from bionic-updates
csmith@downtown:~$ IP=`uvt-kvm ip ubuntu18.04`
csmith@downtown:~$ ssh csmith@$IP
Welcome to Ubuntu 18.04.6 LTS (GNU/Linux 5.4.0-84-generic x86_64)
* Documentation: https://help.ubuntu.com
*
# Success testing on Bionic Desktop installer
1. Validate current behavior from bionic-updates
csmith@downtown:~$ IP=`uvt-kvm ip ubuntu18.04`
csmith@downtown:~$ ssh csmith@$IP
Welcome to Ubuntu 18.04.6 LTS (GNU/Linux 5.4.0-84-generic x86_64)
* Documentation: https://help.ubuntu.com
*
Marking this bug as closed as the fix has now published in version
27.4.1 to Xenial, Bionic, Focal, Hirsute and Impish -updates pockets on
Nov 17th.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-advantage-tools (Ubuntu Xenial)
Upstream commit landed to avoid this network egress on unattached
machines. https://github.com/canonical/ubuntu-advantage-
client/commit/ab01ce2f68b32fd2702f947a408c58d2435f1c47
Already undergoing SRU release verification and queued as version
27.4.1. The fixed version is currently in
Public bug reported:
Version 27.3 introduced a new systemd timer which runs a job named
update_status_timer every 12 hours to update the status of supported UA
services on machines which are attached to an Ubuntu Advantage licese.
This job should not be run on machines without an active Ubuntu
** Changed in: software-properties (Ubuntu Bionic)
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/1939732
Title:
report availability of Ubuntu Advantage ESM
** Also affects: software-properties (Ubuntu Bionic)
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/1939732
Title:
report availability of Ubuntu Advantage
** Also affects: cloud-init (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: cloud-init
I think there was an omission on the latest bionic upload it doesn't
contain the fixes that were added for focal, hirsute and impish.
I've put up a PR that cherry-picks those fixes into the bionic branch
that would need review and upload before I can validate and set
verification-done-bionic on
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
** This bug has been marked a duplicate of bug 1930121
package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No
module named 'uaclient'
--
You received this bug notification because you
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
Closing this bug as it appears a duplicate of LP:# 1930121. Please
reopen if this is an error.
** This bug has been marked a duplicate of bug 1930121
package ubuntu-advantage-tools 27.0.2~18.04.1 -
# Hirsute desktop results: SUCCESS non-LTS has neither ESM-Infra nor ESM-Apps
support or availability.
# so 1. it will not expose "Extend..." links to provide ESM information in
Updates tab
# and 2. When attached no ESM information will be represented in Updates tab
1. # install proposed
$ cat
1 - 100 of 916 matches
Mail list logo
