Public bug reported:
[ Impact ]
Cloud-init recently added policy-based routing for netplan-only systems
on EC2. In order to gate the netplan-specific code, it checked to see in
the netplan activator was being used. However, if the datasource is
fetched in init-local timeframe (such as on EC2),
** Description changed:
[ Impact ]
Cloud-init recently added policy based routing for multi-nic setups in
EC2. The added code assumed that "subnet-ipv4-cidr-block" would be
present in the metadata obtained from EC2's IMDS. However, on ipv6-only
instances, this is not true. The
** Also affects: cloud-init (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
[ Impact ]
Cloud-init recently added policy based routing for multi-nic setups in
EC2. The added code assumed that "subnet-ipv4-cidr-block" would be
present in the metadata obtained from EC2's IMDS. However, on ipv6-only
instances, this is not true. The assumption leads to a
The version of Python that is shipped with Ubuntu is what is supported
for the system. In the case of Focal, that is 3.8. It is fine to install
and use Python 3.9 for user applications, but when you run `update-
alternatives` to replace the default version of Python, you are now
forcing packages
"when we install python3.9, we point /usr/bin/python to 3.9, but not
/usr/bin/python3"
cloud-init does use `python3` and not `python`, though I'm not sure that
would change anything.
$ head -1 /usr/bin/cloud-init
#!/usr/bin/python3
Since we can launch the AMI and cloud-init works ok out of the
"We can test to see if installing python3-jinja2 moved us forward.
Standby."
That's good if that works, but I'm still not sure how this situation
happened. If I run `apt depends cloud-init`, I see `Depends:
python3-jinja2` as one of the dependencies. That means that even if
python3-jinja2 wasn't
How are you running Python 3.9 in Focal? Are you using the cloud-init
package provided by Apt? Your error shows a crash due to the jinja2
library not existing, but jinja2 is a dependency of cloud-init. The
python3-jinja2 package should have been installed when you installed
cloud-init. Up until
** Changed in: cloud-init (Ubuntu)
Importance: Critical => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066066
Title:
cloud-init startup failure with Python 3.9.5, Ubuntu Focal
To
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066066
Title:
** Description changed:
[ Impact ]
- * Environments or scripts which directly call cloud-init subcommands and
-provide an optional -f or --file argument to inject supplemental
-configuration after first boot will receive usage errors on the command
-line which will break any
** Also affects: subiquity (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/2063813
Title:
cloud-init schema validation failure for: 'broadcast'
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-needed-mantic
** Tags added: verification-done verification-done-focal
verification-done-jammy verification-done-mantic
--
You received this bug notification because you are a member of Ubuntu
Attached are the integration test runs for Focal, Jammy, and Mantic on
EC2, GCE, Azure, LXD containers, and LXD VMs. Curtin-cloud-init-sru
results are also attached.
Any failures are described in failures.txt along with "-rerun.txt"
containing reruns due to transient failures.
** Summary
We intend this bug to be included in the SRU covered by
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056100 . Any
testing related to this bug will be included there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Timo,
"test results are missing"
We don't attach test results until after the package has landed in
proposed.
"Also, the .changes file has a ref to #1946003, which is probably not
intended.."
Fixed in the latest uploads.
** Changed in: cloud-init (Ubuntu Focal)
Status: Incomplete =>
Due to cache invalidation happening every boot
(https://github.com/canonical/cloud-
init/blob/main/cloudinit/sources/__init__.py#L925), we also wind up
fetching metadata every boot. That has some rough edges to be addressed
separately, but it is currently giving us the behavior we desire, so I'm
Public bug reported:
This FFe would cause EC2 instance to fetch networking information every
boot and is implemented in https://github.com/canonical/cloud-
init/pull/5110 . Currently, EC2 only fetches that information first boot
and uses that cached information on subsequent boots.
In cloud-init 23.4, we added network config schema checking[1] to ensure
that any network config provided adheres to network configuration v1
format[2]. The cloud-init code to translate Oracle's networking
information into network v1[3] incorrectly includes a broadcast address
in the rendered
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056460
Title:
** Description changed:
BACKGROUND:
cloud-init-local.service runs before networking has started. On non-
Oracle platforms, before networking has come up, cloud-init will create
an ephemeral connection to the cloud's IMDS using DHCP to retrieve
instance metadata. On Oracle, this
@bdrung , I realize that initramfs-tools may not be the culprit, but
given how Oracle uses iSCSI along with the recent dhcpcd changes, I
added it here too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
BACKGROUND:
cloud-init-local.service runs before networking has started. On non-
Oracle platforms, before networking has come up, cloud-init will create
an ephemeral connection to the cloud's IMDS using DHCP to retrieve
instance metadata. On Oracle, this normally isn't
** Description changed:
[ Impact ]
In cloud-init 23.4, specifying a datasource via the SMBIOS is broken.
This is due to a commit that fixed another bug of cloud-init assuming a
datasource list consisting of one datasource and 'None' doesn't need to
check for the existence of that
This includes the 23.4.4 integration test run results. All failures are
expected and explained in a file named "failures.txt".
The test described in this bug's test plan is included in these runs. It
can be found by searching for
** Description changed:
[ Impact ]
In cloud-init 23.4, specifying a datasource via the SMBIOS is broken.
This is due to a commit that fixed another bug of cloud-init assuming a
datasource list consisting of one datasource and 'None' doesn't need to
check for the existence of that
Public bug reported:
[ Impact ]
In cloud-init 23.4, specifying a datasource via the SMBIOS is broken.
This is due to a commit that fixed another bug of cloud-init assuming a
datasource list consisting of one datasource and 'None' doesn't need to
check for the existence of that datasource. The
I believe that cloud-init is working as intended here. I'm unfamiliar
with the Ubuntu Image tool, but it looks like there is overlap between
the user-creation from that tool and cloud-init.
When cloud-init runs, it will by default create a distro-default user with no
password and password login
Also got confirmation via IRC from Christopher Patterson that Azure testing is
complete. Partial log:
cjp256: Anyhow, fwiw we haven't had unexpected issues with SRU.
falcojr: Is there more testing to be done, or are you done at this point?
cjp256: we're good with it
** Tags removed:
Regression testing attached. This includes:
* Cloud-init integration tests on EC2, GCE, Azure, LXD containers, LXD VMs, and
openstack for bionic, focal, impish, and jammy
* The MAAS SRU regression job
* The curtin cloud-init SRU job
* failures.txt which describes all non-transient failures and
** Description changed:
[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:
- TODO
+ - Add schema definition for all modules and add to schema store
+ - Promote
** Description changed:
[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:
TODO
[Test Case]
The following development and SRU process was followed:
Public bug reported:
[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:
TODO
[Test Case]
The following development and SRU process was followed:
Public bug reported:
Gnome-shell slowly grows in memory over time. The mouse will start to
stutter and keyboard input repeats the same character many times. After
a day or two, I have to reboot or my desktop environment crashes.
I have disabled all extensions except for the Ubuntu default ones.
** Changed in: cloud-init (Ubuntu)
Status: Triaged => 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/1906187
Title:
Top-level 'network' key results in error using v2 config
To
See https://github.com/canonical/cloud-init/pull/1349
** Changed in: cloud-init (Ubuntu)
Status: Triaged => 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/1965275
Title:
status
Fix committed at https://github.com/canonical/cloud-init/pull/1417
** Changed in: cloud-init
Status: Triaged => 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/1906187
Title:
This was fixed in upstream cloud-utils version 0.32. It is available in
Ubuntu 21.10 and later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967428
Title:
cloud-init package: write-mime-multipart
** Changed in: cloud-utils
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/1967428
Title:
cloud-init package: write-mime-multipart with SyntaxWarning
To manage
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => Invalid
** Summary changed:
- Version tag is not respected when put last
+ Top-level 'network' key results in error using v2 config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Also affects: netplan
Importance: Undecided
Status: New
** Also affects: cloud-init
Importance: Undecided
Status: New
** No longer affects: netplan
** Changed in: cloud-init
Status: New => Triaged
** Changed in: cloud-init
Importance: Undecided => High
--
You
** Changed in: cloud-init (Ubuntu)
Status: Triaged => 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/1473527
Title:
module ssh-authkey-fingerprints fails Input/output error:
write-mime-multipart hasn't been part of cloud-init since 0.5.15, which
is no longer supported anywhere. It was since moved to the cloud-utils
package where it has already been fixed upstream but has not been SRUed
to supported Ubuntu releases.
--
You received this bug notification because you
** Also affects: cloud-utils
Importance: Undecided
Status: New
** 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/1967428
Verification on Impish
** Attachment added: "lp_1966085_impish.txt"
https://bugs.launchpad.net/bugs/1966085/+attachment/5572696/+files/lp_1966085_impish.txt
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-impish
** Tags added:
Verification on Focal
** Attachment added: "lp_1966085_focal.txt"
https://bugs.launchpad.net/bugs/1966085/+attachment/5572695/+files/lp_1966085_focal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verification on Bionic
** Attachment added: "lp_1966085_bionic.txt"
https://bugs.launchpad.net/bugs/1966085/+attachment/5572694/+files/lp_1966085_bionic.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Calling "cloud-init status --wait" never returns if ds-identify cannot
find a datasource.
+ In https://github.com/canonical/cloud-init/pull/1162, we modified status
+ checks to wait until we get an "enabled" or "disabled" file from ds-
+ identiy. ds-identify never
We got confirmation from Azure in an email on Mar 16 that "we have seen
no significant issues with the SRU."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961446
Title:
sru cloud-init (22.1
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965275
Title:
Jan, the fix is available upstream but not yet rolled out to existing
Ubuntu series. They're expected to roll out next week assuming no
additional issues are found.
The version number is 22.1-14-g2e17a0d6-0ubuntu1~YY.MM.2 and is
currently available from the -proposed pockets.
--
You received
This tarball includes Oracle cloud test results, which ran as expected.
** Attachment added: "oci_tests.tar.gz"
https://bugs.launchpad.net/bugs/1961446/+attachment/5570064/+files/oci_tests.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Andrew, yes, I think that's a reasonable solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473527
Title:
module ssh-authkey-fingerprints fails Input/output error: /dev/console
To manage
Attach file azure_tests.tar.gz.
Integration tests for Azure. The one rerun is due to a transient failure
and passed upon rerun.
** Attachment added: "azure_tests.tar.gz"
https://bugs.launchpad.net/bugs/1961446/+attachment/5568083/+files/azure_tests.tar.gz
--
You received this bug
** Changed in: cloud-init
Status: Confirmed => 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/1569974
Title:
networking fallback should ignore bridges
To manage notifications
*** This bug is a duplicate of bug 1940791 ***
https://bugs.launchpad.net/bugs/1940791
Chad Smith was able to reproduce this while investigating #1940791, and
this appears to be the same root cause as #1940791, so I'm going to mark
this one as a duplicate.
** This bug has been marked a
By default, server images don't set a default user/password. Cloud-init
will create the ubuntu user, but expects SSH auth by default and so will
lock the password for the ubuntu user. Did you use an installer with the
image? Was any userdata included on the SD card that you know of?
If you can
Thanks for the detailed bug report.
I used your reproducer steps, but I got a slightly different result. I'm
still not getting the NoCloud identification, but in my case, I can't
force ds-identify to identify it. In order for ds-identify to identify
NoCloud, it needs to see a "cidata" filesystem
** 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/1959343
Title:
deprecation of the Canonical partner archive
To manage
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959118
Title:
The intent was not to change LTS behavior, so yes, we will modify the
behavior accordingly.
Can you help me understand your use case so we know what needs to
change? Previous to this LXD Datasource, we expected LXD containers to
be identified to cloud-init using the NoCloud datasource. It sounds
Sorry, I should have been more clear in my comment.
In your bug report, you mentioned:
root@ubuntutemplate:~# cat /mnt/tmp/meta-data
instance-id: 61a74c24a0b88039cc7ee3e0560d6ffe0a91f956
root@ubuntutemplate:~# cat /mnt/tmp/user-data
#cloud-config
hostname: ubuntutemplate
manage_etc_hosts: true
Looking at the cloud-init.log, it appears that network is intentionally
disabled.
2022-01-17 15:13:47,267 - stages.py[DEBUG]: network config disabled by
system_cfg
2022-01-17 15:13:47,267 - stages.py[INFO]: network config is disabled by
system_cfg
which means network is disabled via the "cloud
Not sure if this helps, but we recently added behavior to wait for an
apt lock when doing apt commands. This will be included in our next
release: https://github.com/canonical/cloud-init/pull/1034
If there are still remaining issues, please open a new bug rather than
commenting here. This bug
This change intentionally won't change the permissions of already
existing files. As long as the file is root readable and writable,
manually updating the permissions for existing instances shouldn't cause
any problems.
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1946644 ***
https://bugs.launchpad.net/bugs/1946644
Thanks for the bug report. This is a duplicate of #1946644 and should be
fixed in cloud-init 21.4.
** This bug has been marked a duplicate of bug 1946644
After restart cloud-init reconfigured the
** Changed in: cloud-init
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899487
Title:
cloud-init hard codes MTU configuration at initial deploy time
To manage
** 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/1949521
Title:
sru cloud-init (21.3-1 to 21.4-0) Bionic, Focal, Hirsute and
Yes, the fix will be backported to -updates in Bionic, Focal, Hirsute,
and Impish. That could happen as soon as today or early next week. The
tracking bug for that is
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1949521
--
You received this bug notification because you are a member
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-hirsute verification-needed-impish
** Tags added: verification-done-bionic verification-done-focal
verification-done-hirsute verification-done-impish
--
You received this bug
Attach file 21.4-0-integration-tests.tar.gz. Contained are the
integration testing results from Azure, EC2, GCE, LXD containers, LXD
VMs, OCI, and Openstack.
** Attachment added: "21.4-0-integration-tests.tar.gz"
Attach file curtin-cloud-init-sru.txt.
** Attachment added: "curtin-cloud-init-sru.txt"
https://bugs.launchpad.net/bugs/1949521/+attachment/5540882/+files/curtin-cloud-init-sru.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attach file maas_sru_proposed_cloudinit-sru-manual.txt.
** Attachment added: "maas_sru_proposed_cloudinit-sru-manual.txt"
https://bugs.launchpad.net/bugs/1949521/+attachment/5540881/+files/maas_sru_proposed_cloudinit-sru-manual.txt
--
You received this bug notification because you are a
In an email from 'Yuhua Zou' on November 12, in regards to VMWare
testing:
It works well with cloud-init 21.4 from xxx-proposed repository.
Check items:
Install cloud-init 21.4 from -proposed repo
Uninstall cloud-init 21.4
Guest OS Customization with cloud-init 21.4
Check VMs
Ubuntu 21.10
In an email from 'Anh Vo' on Nov 11, in regards to Azure testing:
"I've put this through some manual validations and scale testing. It looks good
to go."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We have a traceback. No log exists because the traceback happens before
logging is initialized.
It appears this bug report is due to a version conflict in your snap
packaging, so not a cloud-init issue. If that is incorrect, please set
the status back to New and how the problem relates to
https://github.com/canonical/cloud-
init/blob/main/cloudinit/sources/helpers/vmware/imc/config_nic.py#L277
is the line that should be changed.
See https://github.com/TheRealFalcon/cloud-
init/commit/a6faf3acef02bd8cd4d46ac9efeebf24b3f21d81 . Stock Debian
installs use a regex that doesn't include
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot on impish for raspberry pi
to raw disk (#1017)
+ - HACKING.rst: change contact info to James Falcon (#1030)
+ - tox: bump the pinned flake8 and pylint version (#1029)
+ [Paride Legovini] (LP: #1944414)
+ - Add retries to DataSourceGCE.py when connecting to GCE (#1005)
+ [vteratipally]
+ - Set Azu
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:
- Initial hotplug support
- Datasource for VMware
- Add support for
This bug is believed to be fixed in cloud-init in version 21.4. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 21.4. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
** Changed in: cloud-init
Status: Confirmed => 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/1568637
Title:
network config of initramfs devices writes 'auto', breaking iscsi
** Changed in: cloud-init
Status: Triaged => 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/1946003
Title:
hotplug causing cloud-init to spike CPU usage
To manage notifications
** Summary changed:
- Cloud init ignores growpart off on impish for raspberry pi
+ Unexpected partition growth on impish for raspberry pi
** Summary changed:
- Unexpected partition growth on impish for raspberry pi
+ Unexpected partition growth on first boot on impish for raspberry pi
--
You
I'm shooting from the hip here, but you could try adding this to your
cloud-config:
bootcmd:
- touch /etc/growroot-disabled
If that doesn't work, you could try a bug targeting the
https://bugs.launchpad.net/ubuntu/+source/linux-raspi project.
--
You received this bug notification because you
There's a separate package called cloud-initramfs-growroot (separate
from cloud-init), that has a tool called growroot. It can be disabled by
touching /etc/growroot-disabled . If you have a "x-systemd.growfs" in
your /etc/fstab, that's probably what's initiating it.
--
You received this bug
According to the logs, growpart isn't doing any resizing:
2021-10-13 13:33:05,609 - stages.py[DEBUG]: Running module growpart () with
frequency always
2021-10-13 13:33:05,610 - handlers.py[DEBUG]: start:
init-network/config-growpart: running config-growpart with frequency always
2021-10-13
** Changed in: cloud-init (Ubuntu Trusty)
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/1311463
Title:
disk-setup unable to partition disks
To manage
** Description changed:
=== Begin SRU Template ===
[Impact]
In PR #919 (81299de), we refactored some of the code used to bring up
networks across distros. Previously, the call to bring up network interfaces
during 'init' stage unintentionally resulted in a no-op such that network
** Description changed:
=== Begin SRU Template ===
[Impact]
In PR #919 (81299de), we refactored some of the code used to bring up
networks across distros. Previously, the call to bring up network interfaces
during 'init' stage unintentionally resulted in a no-op such that network
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946773
Title:
"An error occurred. Press enter to start a shell"
To manage
Re cloud-init, in the log I see a 3 minute gap between when cloud-init's
init stage ends and the modules stage starts, and then I see modules-
final stage never starting. Something else in boot is preventing the
modules-final stage from starting, so cloud-init will never finish.
--
You received
cloud-init fix has been committed upstream via
https://github.com/canonical/cloud-init/pull/1061
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
--
You received this bug notification because you are a member
Attach file integration_test_results.tar.gz. These tests show the issue
fixed in B, F, and H
** Attachment added: "integration_test_results.tar.gz"
https://bugs.launchpad.net/bugs/1938299/+attachment/5531668/+files/integration_test_results.tar.gz
--
You received this bug notification
Please provide a brief description of the problem you're encountering
along with the tarball generated from 'cloud-init collect-logs'.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ In PR #919 (81299de), we refactored some of the code used to bring up
networks across distros. Previously, the call to bring up network interfaces
during 'init' stage unintentionally resulted in a no-op such that network
** Changed in: cloud-init (Ubuntu)
Status: Fix Committed => 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/1939603
Title:
Oracle DataSource Fails When Used With a Bionic Image
Also got confirmation from Azure via email that their testing is
complete.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-hirsute
** Tags added: verification-done verification-done-bionic
verification-done-focal
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-hirsute
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-hirsute
--
You received this bug notification because you are a member of
1 - 100 of 194 matches
Mail list logo
