xe-guest-utils
==
brought in as part of a partner image. These partners are an LTS cloud,
and have not taken a Focal image at this time. The company has also
produced a new generation of their cloud. Those images do not include
xe-guest-utils.
>From CPCs perspective, it is safe to dem
rcj and I had just been discussing this in relation to a new arm64
image.
We are currently re-enabling the file for EC2 arm64 in our EC2 specific
code. I took the workaround from our EC2 and implemented in our test
image. We agreed that we'll need to get 999-cpc-fixes worked out more.
The code th
Confirmed not just for arm64, but also latest amd64 groovy builds
amd64 ami: ubuntu/images-testing/hvm-ssd/ubuntu-groovy-daily-
amd64-server-20201104
~$ uname -a
Linux ip-172-31-92-148 5.8.0-1011-aws #11-Ubuntu SMP Thu Oct 22 10:15:49 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
~$ dpkg -S systemd-d
** Summary changed:
- systemd-detect-virt is missing on Groovy arm64 EC2 AMI
+ systemd-detect-virt is missing on Groovy EC2 AMI
** Changed in: cloud-images
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I've confirmed the Groovy change using the following test:
1. downloaded source for proposed package
2. used ubuntu-old-fashioned/scripts/ubuntu-bartender to run a build
3. used Virtualbox to load the ova and vmdk
4. ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with
no is
There is no specific need for this to be included in a seed. It's
required for the GKE images, and we maintain cloud specific install
lists, separate from the general seeds. Server or cloud-images would be
too inclusive (we'd need to script uninstalling it in the other images).
Is this where the "
Thanks! I also just learned about:
platform.$SUITE/supported-cloud
Based on the format, I'd say this package should be in that seed, in the
= Per-cloud-image packages = section with a comment:
# For GKE
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I've confirmed the Bionic change using the following test:
1. downloaded source for proposed package
2. used ubuntu-old-fashioned/scripts/ubuntu-bartender to run a build
3. used Virtualbox to load the ova and vmdk
4. ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with
no is
I've confirmed the Focal change using the following test:
1. downloaded source for proposed package
2. used ubuntu-old-fashioned/scripts/ubuntu-bartender to run a build
3. used Virtualbox to load the ova and vmdk
4. ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with
no iss
image builds are only built after the SRU process is complete and
livecd-rootfs is in the updates pocket. This wiki page will help explain
the SRU process in more detail:
https://wiki.ubuntu.com/StableReleaseUpdates
My verification is being done by building images against the livecd-
rootfs pr
I've confirmed that running on kernel 4.19.97-v7l, available on the
Raspbian image published on 2020-02-14 there are issues running `date`.
it returns the Linux epoch date. the following containers are affected:
ubuntu/focal
ubuntu/groovy
debian/bullseye
there was not an issue with debian/buster,
latest Groovy vagrant image has removed virtualbox-guest-utils and now
mounts properly. Any version equal to or newer than v20201006.0.0 will
mount the guest folder.
I'm still going to do some testing with the vagrant guest-utils plugin
as well, just to see if it successfully pulls in a newer vers
I did a test utilizing the vagrant plugin for installing guest-additions
on the newly created Vagrant images (using the pre-installed guest-utils
kernel module)
`vagrant plugin install vagrant-vbguest`
This failed in the same fashion, however, I was able to get an install
log. It is attached as i
** Attachment added: "log from groovy VM attempting to install vbguest"
https://bugs.launchpad.net/cloud-images/+bug/1895862/+attachment/5418927/+files/vbox-install.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I've marked cloud-images as Fixed-Released based upon the updated
livecd-rootfs, and confirming that the latest Vagrant Box posted to
https://app.vagrantup.com/ubuntu/boxes/groovy64. We can leave this open
for the Virtualbox package and how we can deliver updates to virtualbox-
guest-utils. But the
I've confirmed that the latest Vagrant box published has the fix. I've
also confirmed that users can overwrite the default passing of the
serial console to a File::NULL and write to a different file.
For everyone affected, run a `vagrant box update` on Focal boxes. This
will grab the latest box. I
** Changed in: livecd-rootfs (Ubuntu)
Status: Confirmed => In Progress
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => John Chittum (jchittum)
** Changed in: cloud-images
Status: Confirmed => In Progress
** Changed in: cloud-images
Assignee: (u
@haggan-era, could you open a new bug on this issue? Please provide the
following information:
1. version of Windows, vagrant, virtualbox, and Ruby in use on the Windows
computer
2. the Vagrantfile used to create the new .box
3. any steps to reproduce the issue.
On first smell it seems like a R
focal and bionic builds with this fix were not completed prior to the
December holidays. Builds with the changes for focal and bionic should
happen soon in 2021.
Xenial is still awaiting a fix to be committed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Focal Daily serial 20210112 has the expected change and is available for
download:
http://cloud-images.ubuntu.com/daily/server/focal/20210112/
Bionic Daily serial 20120112 has the expected change, and is available
for download:
http://cloud-images.ubuntu.com/daily/server/bionic/20210112/
Xenial
I've verified a build on xenial using 2.408.65
1. downloaded source for proposed package
2. used ubuntu-old-fashioned/scripts/ubuntu-bartender to run a build
3. used Virtualbox to load the ova and vmdk
4. ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with
no issues, and ke
We've confirmed this request for upgrading hardware version for our
ova's. We have prioritized this on our backlog, and have it linked to
1895104
** Changed in: cloud-images
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Confirming this bug, as we've prioritized this work on our backlog. When
we work on lp: 1898871, we'll ensure that the ova sets a serial port.
** Changed in: cloud-images
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Description changed:
+ SRU
+
+ [IMPACT]
+
+ * Users are unable to boot a vagrant image, as the boot time without a serial
console connection exceeds the vagrant timeout
+ * bug is focal as well as latest devel devel release.
+ * Upload fixes the bug by creating a serial console connection to
** Description changed:
SRU
[IMPACT]
* Users are unable to boot a vagrant image, as the boot time without a serial
console connection exceeds the vagrant timeout
* bug is focal as well as latest devel devel release.
* Upload fixes the bug by creating a serial console connection to
I did a test build using a branch of livecd-rootfs where I removed the
code installing virtualbox-guest-utils. The vagrant box produced booted
fine and mounted guest folders. This works on groovy on the 5.8.0
kernel.
Looking at groovy, vboxsf, vboxguest, and vboxvideo are included as part
of the l
** Also affects: cloud-images/groovy
Importance: Undecided
Status: Confirmed
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-images/groovy
Assignee: (unassigned) => John Chittum (jchittum)
** Changed in: livecd-roo
SRU for Focal testing.
Created 2 Vagrant boxes to cover the 2 main build cases of CPC (produced
of the Vagrant image and user of the hook changed)
box A: Created via ubuntu-bartender(https://github.com/chrisglass
/ubuntu-old-fashioned/tree/master/scripts/ubuntu-bartender) utilizing
the source dow
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To m
I was unable to reproduce with Ubuntu Focal 64 bit as the host. Could
you provide the Host OS version. Focal is on a 5.4 kernel, and Bionic
should have rolled to a 5.x kernel as well.
my guess at this time is your host is a 32bit (from the armv7l listing
in the kernel). if you let me know the Host
I tested with Ubuntu Bionic 32bit and was unable to reproduce. Also
unable to reproduce with a Focal 32bit. Both of these are running the
5.4 kernel though, so it may just be affecting 4.X series kernels.
I'll flash a Raspbian Buster 32 bit and test on my Raspberry Pi 4
--
You received this bug
With the release of livecd-rootfs 2.408.65 in Xenial, cloud_images will
take the package and produce builds. I will update the ticket when our
next Xenial daily build goes out built with this version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
reinstall attempted today. CD image downloaded on 20210124 and USB
created via Rufus on Windows. Attempted install, indicated Install
Third-Party Drivers. Crashed at the very end, after updating packages.
hardware is a System 76 Gazelle (2019).
--
You received this bug notification because you ar
vmware-gos-Yuhua (yhzou) and cloud users:
The latest Xenial daily build has the required changes, serial 20210127
http://cloud-images.ubuntu.com/xenial/20210127/
The vmdk and ova were both validated in the following way:
1) downloaded vmdka and ova from http://cloud-images.ubuntu.com/xenial/202
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893898
Title:
open-vm-tools status is toolsNotInstalled after deploy cloud image
also affects other cloud-images beyond ec2. confirmed in GCE as well,
and may affect other clouds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902260
Title:
systemd-detect-virt is missing on Groo
Public bug reported:
[Availability]
Package is available in Universe. Builds are green for all arches
specified
[Rationale]
This is a request from Google as they utilize nvme-cli to manage nvme
drives in their cloud. The package offers tools for managing nvme
drives, including nvme over fabric
I've actually done some checks on latest versions, and it looks like we
can. I'll make a public bug to match the internal ticket I made to
remove the connection.
We've got a release tomorrow (20201022), so the change will go into the
next devel release first, then get SRU'd back.
--
You received
I've opened https://bugs.launchpad.net/cloud-images/+bug/1900852 related
to removing uart1 connections in the base Vagrantfile. We can move
discussion there related to the issue found for derivative images via
Packer, and generally removing it.
I, too, had been under the impression that due to the
m.provider "virtualbox" do
|vb|` stanza from the base Vagrantfile in Groovy and newer images, with
further testing needed for possible SRU.
** Affects: cloud-images
Importance: Undecided
Assignee: John Chittum (jchittum)
Status: New
** Affects: livecd-rootfs (Ubu
Also confirmed that this affects Xenial images.
MP is up, will make revisions shortly based on feedback. Due to the
release Thursday, this won't be included in the Groovy Gorilla day 1.
We'll have this in shortly after release, and work work the SRU process
from the H release to Groovy, Focal, Bio
disabling `uart1` leads to `cloud-init` failures when writing keys:
```
2020-10-26 18:37:30,888 - util.py[WARNING]: Running module keys-to-console
() failed
2020-10-26 18:37:30,889 - util.py[DEBUG]: Running module keys-to-console
() failed
Traceback (most recent call last):
File "/usr/lib/pyth
I can reproduce locally doing the following (fails on focal and groovy).
I did this using the cloud-images.ubuntu.com VMDK, Virtualbox, and a
simple cloud-init with ssh key and username/pw w/ ssh pw auth on. I got
the following error:
```
2020-10-28 13:32:33,680 - util.py[WARNING]: Running module
This can also be configured to pass by having virtualbox provide a
serial console connect:
1. select image on Left, right click and choose Settings, or hit ctrl+s
2. Choose Serial Ports
3. Enable Port 1 as follows:
a. Enable
b. COM1
c. IRQ: 4
d. I/O Port: 0x3F8
e. Port Mode: Raw File
f
This appears related to : https://bugs.launchpad.net/ubuntu/+source
/cloud-init/+bug/1473527
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900852
Title:
Remove uart1 connection from Vagrant boxes
initial fix has been merged into Hirsute, and is currently in proposed.
I did the following test using the deb src of release 2.697 from
proposed (now superseded by 2.698)
1. downloaded dev source
2. unpacked
3. used ubuntu-oldfashioned/scripts/ubuntu-bartender to run a hirsute build
```
./ubuntu
The latest hirsute cloud image ova and vmdk include this change. These
can be downloaded from:
http://cloud-images.ubuntu.com/hirsute/20201103/
My initial checks show correct headers and images boot fine using
Virtualbox. I'll await confirmation from vmware-gos-Yuhua before marking
complete and b
** Also affects: cloud-images
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/1895104
Title:
It hangs during booting after deploy cloud image(.ova) and upg
** Also affects: cloud-images
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/1898871
Title:
change the future OVA(s) to have default VM hardware version 13
Thank you for opening this ticket. I've added it to the cloud-images
project for prioritization.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895104
Title:
It hangs during booting after deploy clo
Thank you for opening this ticket. I've added it to the cloud-images
project for prioritization.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898871
Title:
change the future OVA(s) to have default
Public bug reported:
Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on
ubuntu:focal (20.04) produces a broken state. Debug of `apt-get install
virtualbox-guest-utils` below.
Steps to reproduce:
1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04
test-container)
** Changed in: cloud-images
Assignee: (unassigned) => John Chittum (jchittum)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873506
Title:
ubuntu/focal64 fails to mount Vagrant shared fold
Focal and Eoan boxes with the above kernels have been pushed to Vagrant
and verified. Please run a `vagrant box update` to get the latest
versions.
** Changed in: cloud-images
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Vagrant boxes with updated kernels have been pushed. My current tests
are showing boot times in the 30s range.
Could folks commenting on slow boot speeds in Focal and Eoan please run
a `vagrant box update` on their current setups?
https://app.vagrantup.com/ubuntu/boxes/eoan64/versions/20200522.0.
May 22nd was made available when I commented. Not sure why your update
didn't find it. Maybe there's lag with specific mirrors. Official
listings show them available:
https://app.vagrantup.com/ubuntu/boxes/focal64
https://app.vagrantup.com/ubuntu/boxes/eoan64
--
You received this bug notificat
apologies -- the 0518 Focal image has the fix as well. That may not have
been clear since the comments came on the 19th, and I updated on the
22nd. The eoan 22nd made it up on the 22nd, but there was lag with the
Focal 0522 serial syncing on our end. It's up there now.
--
You received this bug no
is this post updating the boxes? could you please post which boxes are
still kernel panicking, as that should have been fixed with
https://bugs.launchpad.net/cloud-images/+bug/1873506
I'm having a bear of a time trying to reproduce the slow boots. I'm
wondering if it's host specific to MacOS and V
I've set the kernel component to confirmed to move this ticket forward.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Titl
was passed a related issue:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1879290
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots on
Was able to recreate the slow boot. Put together a clean environment,
made a simple focal Vagrantfile only pulling the box, saw the same
things. Confirmed on a Focal host.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Confirmed fix. The main symptom was inability to SSH into a running
instance due to cloud-init not completing. Main test was to instantiate
an instance and SSH in. Test procedures:
1. checked daily CPC Oracle build to ensure build passed
2. Checked image manifest to ensure open-iscsi 2.0.874-7.1ub
** Also affects: linux (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/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To manage
Attached are some prints and logs. lshw shows that it's using a scsi
storage control with the mptspi driver. serial console logs show that
initramfsless boots using a a generic scsi driver which appears to fail
to load the root device. initramfs pulls in the mptspi driver properly,
and things boot.
*** This bug is a duplicate of bug 1874453 ***
https://bugs.launchpad.net/bugs/1874453
** This bug is no longer a duplicate of bug 1829625
Vagrant box startup timeout due to no serial port
** This bug has been marked a duplicate of bug 1874453
ubuntu/focal64 very slow to boot and reboots
*** This bug is a duplicate of bug 1874453 ***
https://bugs.launchpad.net/bugs/1874453
** This bug has been marked a duplicate of bug 1874453
ubuntu/focal64 very slow to boot and reboots once
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
*** This bug is a duplicate of bug 1874453 ***
https://bugs.launchpad.net/bugs/1874453
** This bug is no longer a duplicate of bug 1829625
Vagrant box startup timeout due to no serial port
** This bug has been marked a duplicate of bug 1874453
ubuntu/focal64 very slow to boot and reboots
** Package changed: linux (Ubuntu) => livecd-rootfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To manage notifications a
** Changed in: cloud-images
Assignee: (unassigned) => John Chittum (jchittum)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
Importance: Undecided
Status: New
** Also affects: cloud-images/groovy
Importance: Undecided
Assignee: John Chittum (jchittum)
Status: Confirmed
** Changed in: cloud-images/focal
Status: New => Confirmed
** Changed in: cloud-images/focal
Assignee: (unassigned) =&
fix in livecd-rootfs/master has been merged, built, and tested. Groovy
boxes with any serial with a date 20200917 or newer should have the fix
(we're working on getting this published now). I am also beginning the
SRU procedure to backport the change into Focal.
Thank you giner for the providing
Also, for anyone that has run a Focal or Groovy box, and had it hang
completely with it not showing up in Virtualbox GUI for stopping, the
following can get the image unlocked for future work (without a reboot)
vboxmanage startvm --type emergencystop
vboxmanage unregistervm
If you're unsure of
Updated Groovy Vagrant box has been pushed to Atlas, and tested. Steps
below, Vagrantfile at bottom:
1. create a minimal Vagrantfile for testing
2. `vagrant box update`
3. check box is at a serial 20200917 or newer (if done now, 20200917 should
download)
4. `vagrant up`
5. observe it now boots fa
** Changed in: cloud-images/groovy
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/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To manage
Public bug reported:
## Info
chromium 128.0.6613.119 2943 latest/stablecanonical✓
snapd 2.6321759 latest/stablecanonical✓
Ubuntu 24.04
kernel - 6.8.0-41-generic
## hardware
system76 gazelle 14" 2019 model
### GPU
NVIDIA GeForce GTX 1660 Ti
Driver Version: 535.183.01
nteodesio: just had the exact same crash, launching Chromium by clicking
the icon on the dock (without discreet graphics). I'm in meetings 5-6
hours a day, so I can try just about any fashion you'd like me to
launch.
i'm also confused about that commandline being unsupported -- that's
what clickin
I haven't come across this before. Our builds for the cloud images from
cloud-images.ubuntu.com have the following cleanup code run that should
be preventing this sort of thing:
https://git.launchpad.net/livecd-rootfs/tree/live-build/functions#n231
hard to read exact ramifications, but the gist i
Kinetic Vagrant image is available at :
https://app.vagrantup.com/ubuntu/boxes/kinetic64
for a fresh install quickly
vagrant init ubuntu/kinetic64
vagrant up
This image should work on all versions of Vagrant available in Ubuntu
archives. I'll spin some VMs and do more testing, but community hel
** Also affects: livecd-rootfs (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/2072929
Title:
Ubuntu cloud image partition numbering
To manage not
`gosu` is a universe package in Ubuntu, and from what i can see was
inherited from `side` at version 1.17.1
https://packages.debian.org/sid/gosu
I see no open bugs against `gosu` : https://bugs.debian.org/cgi-
bin/pkgreport.cgi?src=gosu , and it needs to be confirmed that it's
built against golan
** Changed in: cloud-images
Status: New => Confirmed
** Changed in: cloud-images/oracular
Status: New => Confirmed
** Changed in: cloud-images
Importance: Undecided => High
** Changed in: cloud-images/oracular
Importance: Undecided => High
** Changed in: cloud-images
As
** Changed in: cloud-images
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/2056442
Title:
Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod
`run/shm`:
** Changed in: cloud-images
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/2056065
Title:
cloud images slow to boot under kvm
To manage notifications about this bug
I've set this to incomplete for now. @air-awan, if you have time to give
an update related to vmware environments, let me know.
i double checked, and the addition of the serial port was requested by
the vmware team, so if it's breaking things now due to hypervisor level
issues, I'll have to sync w
** Changed in: livecd-rootfs (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: livecd-rootfs (Ubuntu Jammy)
Status: New => In Progress
** Changed in: livecd-rootfs (Ubuntu Focal)
Status: New => In Progress
** Changed in: cloud-images
Status: New => In Progres
adding cloud-images. if multiple artifacts are generated, the CPC
pipeline will need to ensure that we download and transport all the
livefs-build artifacts.
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member o
@DisasteR -- could you be more specific? Which images are you seeing
this in? which cloud, which download from `cloud-images.ubuntu.com`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049860
Title:
Tested working on the image from http://cloud-
images.ubuntu.com/releases/jammy/release-20240319/
$ ssh -o "UserKnownHostsFile=/dev/null -o CheckHostIP=no StrictHostKeyChecking
no" jchittum@0.0.0.0 -p
The authenticity of host '[0.0.0.0]: ([0.0.0.0]:)' can't be established.
ED25519 ke
Alternative idea, what about instead of writing a wrapper:
1. look at https://packages.ubuntu.com/noble/libnet-ssleay-perl
a. libnet-ssleay-perl is in main
2. add eddsa-25519 to the list of constants upstream
a. if i'm reading correctly, there's a mapping in a
helper_scripts/constants.txt t
@DisatesR : if you're not seeing a 50-cloud-init.conf file, it indicates
to me that cloud-init is failing to parse the cloud_init configuration
properly, and thus not adding the required configuration to
/etc/ssh/sshd_config.d/
could you provide your entire cloud config? you can also use cloud-ini
you can check any progress in Ubuntu by checking the issue tracker
https://ubuntu.com/security/CVE-2024-24790
https://ubuntu.com/security/CVE-2024-24791
it looks like 2024-24690 is fixed, so may be a false-positive.
24791 is still in needs-triage on the page.
--
You received this bug notifica
blech, sorry, misclicks trying to get things added properly
marking as affects cloud-images as producers of the lxd images.
** Also affects: systemd
Importance: Undecided
Status: New
** No longer affects: systemd
** Also affects: cloud-images
Importance: Undecided
Status: Ne
** Changed in: cloud-images
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/1895104
Title:
It hangs during booting after deploy cloud image(.ova) and upgrade
1. what versions of VMware ESXi is this applicable?
2. is this reproducible in other environments, such as Virtualbox?
3. is this error true of all ubuntu images for those versions then? This was
added in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1895104
at the request of vmw
Thank you for checking Aditya. I'll leave this open till you get some
guidance from VMware regarding any changes in Cloud Director that may be
affecting serial console connections.
I've also added this to our 24.04 release notes (to be published soon
for the clouds). Thank you a bunch for trying o
Virtualbox in focal and jammy (20.04 and 22.04) has migrated to
6.1.50-dfsg-1~ubuntu1.20.04.1
reminder that virtualbox is a multiverse package, meaning it relies on
community support at this time. Since we ar eon 6.1.x in 22.04 and
20.04, users can expect bugfixes and security fixes from the commu
Public bug reported:
related to a few other bug reports:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970168
Save File prompt disallows paste to filename. Attached is a screenshot
of what pops up. Tested in various directories.
Info:
lsb_release -a
No LSB modules are available.
Dist
Data points provided:
using an 18.04 Bionic FIPS cloud image, doing
```
apt-get update && apt-get install mysql-server mysql-client
```
successfully installs the server and client, and enables TLS properly
for the FIPS environment. There may be a difference in packaging scripts
between mysql-5.7
Public bug reported:
On Focal, in an automated environment (such as a launchpad builder), a
used can do the following workflow:
curl
"https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x${FINGERPRINT}";
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USER
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965180
Title:
apt-add-repository requires --login for private repos, breaking
automated workflows
To manage notificat
1 - 100 of 290 matches
Mail list logo
