** Changed in: charm-ceph-osd
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/2064717
Title:
ceph-volume needs "packaging" module
To manage notifications
** Changed in: charm-ceph-osd/reef
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064717
Title:
ceph-volume needs "packaging" modu
** Also affects: charm-ceph-osd
Importance: Undecided
Status: New
** Also affects: charm-ceph-osd/reef
Importance: Undecided
Status: New
** Changed in: charm-ceph-osd
Status: New => Fix Committed
** Changed in: charm-ceph-osd
Assignee: (unassigned) => Peter
** Changed in: cloud-archive/victoria
Status: New => Won't Fix
** Changed in: cloud-archive/wallaby
Status: New => 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/2064190
mportance: Undecided
Status: New
** Affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Affects: cloud-archive/wallaby
Importance: Undecided
Status: New
** Affects: magnum (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects:
Hi, I can confirm that linux 5.15.0.106.106 (package version
5.15.0-106.116) from -proposed works, without the issue.
Thanks!
FF
PS: To clarify: the previous versions I had were 5.15.0-101.111 and
-105.115, not -102.112.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Dear Ubuntu maintainers, I think I found a regression in linux
5.15.0-105.
In the past few days, my keyboard stopped working after waking up from
suspend (sleep), so I couldn't unlock my laptop. Various workarounds
found on the internet helped, but I wanted to investigate if
Hi @ajkavanagh, this affects focal-hwe, jammy and will affect any new
releases unless this sysctl is set to 1.
** No longer affects: charm-nova-compute
** Also affects: qemu
Importance: Undecided
Status: New
** No longer affects: qemu
** Also affects: charm-nova-compute
juju config live-migration-permit-post-copy on the nova-compute charm,
could auto enable vm.unprivileged_userfaultfd=1, or at least state this
requirement on it's description.
** Also affects: charm-nova-compute
Importance: Undecided
Status: New
--
You received this bug notification
** Also affects: charm-nova-compute/zed
Importance: Undecided
Status: New
** Also affects: charm-nova-compute/2023.2
Importance: Undecided
Status: New
** Also affects: charm-nova-compute/yoga
Importance: Undecided
Status: New
** Also affects:
Marking magnum-ui (upstream) as invalid since this is an issue found in
the ubuntu focal archive.
** Changed in: magnum-ui
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: magnum-ui (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/205
Title:
Cluster Resize is failing in UI
To manage notifications
> > this context as we'd like to get the issues the point releases resolve
> > fixed in Ubuntu.
>
> Yes, please update https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates to
> include magnum.
>
> I will review the current SRUs in accordance with the exception.
T
in our regression testing and is
validated via Tempest smoke
tests[0].
Best,
[0] https://github.com/openstack-charmers/charmed-openstack-tester/pull/98
--
Felipe Reyes
Software Engineer @ Canonical
felipe.re...@canonical.com (GPG:0x9B1FFF39)
Launchpad: ~freyes | IRC: freyes
--
Ubuntu-release
neutron-19.3.0 from cloud-archive:xena-proposed fixed LP#1947127 in our
environments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975634
Title:
[SRU] Xena stable releases
To manage
On Horizon I was able to launch an instance with a floating ip and
navigate across the different panels with no problem.
ubuntu@freyes-bastion:~$ juju ssh openstack-dashboard/0 apt policy
openstack-dashboard
openstack-dashboard:
Installed: 4:20.1.2-0ubuntu1~cloud0
Candidate:
I was able to run successfully charmed-openstack-tester (tox -e func-
target -- focal-xena) for the Xena UCA, here it's the list of packages
used by the testing bed.
ubuntu@freyes-bastion:~$ juju ssh neutron-api/0 apt policy neutron-common
neutron-common:
Installed: 2:19.2.0-0ubuntu1~cloud0
On Wed, 2022-05-11 at 19:13 +, Lucas Kanashiro wrote:
> Thanks for working with upstream to fix this. Would you be willing to
> backport this fix to Jammy? Or do you prefer me to do it?
I can propose the SRU (via debdiff) if you can sponsor it :-)
>
> For Kinetic we will be moving to the
ppa with the fix proposed at
https://github.com/ClusterLabs/crmsh/pull/972 for testing purposes
available at https://launchpad.net/~freyes/+archive/ubuntu/lp1972730
** Changed in: charm-hacluster
Status: New => Invalid
--
You received this bug notification because you are a member of
The way this error is exposed in the hacluster is when running the
`stop` hook:
unit-hacluster-1: 16:53:41 DEBUG juju.worker.uniter.runner starting jujuc
server {unix @/var/lib/juju/agents/unit-hacluster-1/agent.socket }
unit-hacluster-1: 16:53:41 INFO unit.hacluster/1.juju-log Setting node
Public bug reported:
Pacemaker changed the output string of "crmadmin -S " in 2.1.0
with the commit
https://github.com/ClusterLabs/pacemaker/commit/c26c9951d863e83126f811ee5b91a174fe0cc991
, this is different from the ouput that wait4dc() expects
** Description changed:
[Impact]
This release comes with bug fixes that we would like to make available
to our users.
The following packages come in this set of point releases:
* neutron 19.2.0
* nova 24.1.0
+ * cinder 19.1.0
[Test Case]
The following SRU process was
** Merge proposal linked:
https://code.launchpad.net/~freyes/ubuntu/+source/neutron/+git/neutron/+merge/421764
** Merge proposal linked:
https://code.launchpad.net/~freyes/ubuntu/+source/neutron/+git/neutron/+merge/421763
--
You received this bug notification because you are a member of
Public bug reported:
[Impact]
This release comes with bug fixes that we would like to make available
to our users.
The following packages come in this set of point releases:
* neutron 19.2.0
* nova 24.1.0
[Test Case]
The following SRU process was followed:
Public bug reported:
In 20.04
When I run setup-ds.pl, it always errors out thus:
```
Could not open the script template file
'/etc/dirsrv/config/template-initconfig'. Error: No such file or directory
```
Going by this page:
https://manpages.ubuntu.com/manpages/focal/man5/template-
** Changed in: charm-mysql-router
Milestone: None => 22.04
** Changed in: charm-mysql-router
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
From a charm's perspective, I believe we should be setting
[DEFAULT].unknown_config_option to "warning", so (possible) future
changes in this area won't break a running cluster.
From the docs
worth to mention that the [DEFAULT].name key is set by "mysqlrouter
--bootstrap" and not by the charm, more details at
https://bugs.launchpad.net/charm-mysql-router/+bug/1907250/comments/10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm seeing this error:
2022-05-03 22:04:39 io INFO [7f91c2e53e00] starting 8 io-threads, using backend
'linux_epoll'
2022-05-03 22:04:39 main ERROR [7f91c2e53e00] Error: option 'DEFAULT.name' is
not supported
The error can be reproduced using this bundle
http://paste.ubuntu.com/p/mdY9dJhktH/ +
Public bug reported:
idk, when i started the computer this was the rror
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-driver-510 510.60.02-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
hello all,
I was able to validate successfully the packages available in the
-proposed pocket, specifically the following versions were installed in
the cloud deployed:
~/sources/ubuntu/lp1962582 $ grep ceilometer-common *.dpkg
machine-23.dpkg:ii ceilometer-common
in: nova (Ubuntu)
Assignee: Felipe Reyes (freyes) => (unassigned)
** Changed in: nova (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904580
** Also affects: heat (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/1952447
Title:
Server group creation fails on Xena
To manage notifications
** Changed in: charm-nova-compute
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/1904580
Title:
Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open
To manage
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904580
Title:
Permissions 0644 for '/var/lib/nova/.ssh/id_
*** This bug is a duplicate of bug 1904580 ***
https://bugs.launchpad.net/bugs/1904580
hello everyone, thanks for reporting this bug, I'm going to mark this
bug as duplicate of https://bugs.launchpad.net/charm-nova-
compute/+bug/1904580 since it tracked the analysis and workarounds.
** This
** Patch added: "lp1966512_jammy.patch"
https://bugs.launchpad.net/ubuntu/+source/python-magnumclient/+bug/1966512/+attachment/5573002/+files/lp1966512_jammy.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
n
is 60 minutes.\n' does not match /.*?^Optional arguments:/
** Affects: python-magnumclient (Ubuntu)
Importance: Undecided
Assignee: Felipe Reyes (freyes)
Status: New
** Changed in: python-magnumclient (Ubuntu)
Assignee: (unassigned) => Felipe Reye
** Patch added: "lp1966442_jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-os-win/+bug/1966442/+attachment/5572999/+files/lp1966442_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: python-os-win (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-os-win (Ubuntu)
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
[Impact]
Users will get the latest stable bug fixes for this release of
OpenStack. Point releases included in this SRU:
ceilometer 17.0.1,
heat 17.0.1
horizon 20.1.1
[Test Case]
Testing of point releases for OpenStack packages is covered by:
** Changed in: charm-ironic-conductor
Milestone: None => 22.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943765
Title:
ipmitool "timing" flags are not working as expected causing failure
Hi Frode,
I went through the captures I have and effectively, if we filter out the
packets where the srcport != 53 or dstport != 6081 , we end up only with
valid dns traffic.
I believe this explains what we are seeing, and the other findings you
did regards the missing flows, we can say with
I have a capture using `tshark -i bond0 port 53` and I have a couple of
streams that exhibit this issue, I would like to highlight this one in
particular:
$ tshark -x -r dns-port-machine-10.pcap "udp.stream eq 9" | pastebinit
https://paste.ubuntu.com/p/yS74KCG2bY/
$ tshark -Tfields -e udp.port -e
An older capture:
[...]
.?.V...#[...
8.0.27-0ubuntu0.20.04.1...%..D/D).1[.[g=WEU(.K_.caching_sha2_password..@eX...$..>M'...>.t...E.@.@.KG...f..t
.?.V...#[...
Something I saw in a new data capture was when I made wireshark to
display the conversation of the stream that was showing "Unknown
operation (12)" packets, it displayed this:
[...]
..O...p<...a_.q.U.
...@..J.[...
here is an example on how to reuse config.rendered flag
https://github.com/openstack/charm-manila/blob/b75e6ed3ce6b2c061105ac8226a778e1ec3685d4/src/reactive/manila_handlers.py#L178
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We discussed this issue with the team and the agreement is that the
charm should disable/mask the service until the configuration has been
rendered, this is a pattern already used in other charms. For the
reactive charms there is a handler for this -
https://github.com/openstack/charm-layer-
** Bug watch added: github.com/systemd/systemd/issues #12841
https://github.com/systemd/systemd/issues/12841
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959847
Title:
Unknown operation (12)
On Tue, 2022-02-08 at 15:11 +, Frode Nordahl wrote:
> Thank you for your bug report, I wonder if this proposed fix [0] could
> be related?
I don't believe so, IIUC this would affect how the replies are
assembled and passed to the guest. I was looking at a similar issue (RR
counters) on the
Checking designate/2.
~/Downloads/f1badd08-a9a6-405a-b0be-d7f49ece023c/designate_2 $ tail
var/log/designate/designate-mdns.log -n 2
2021-04-19 16:04:24.389 64928 ERROR designate
oslo_db.exception.CantStartEngineError: No sql_connection parameter is
established
2021-04-19 16:04:24.389 64928 ERROR
syslog from a VM where some dns queries failed with ETIMEDOUT, e.g.
Feb 2 15:56:08 juju-6c8a68-zaza-1e093df25cbd-7 systemd-resolved[1352]:
Transaction 55701 for on scope dns on ens3/*
now complete with from none (unsigned).
** Attachment added: "syslog"
Public bug reported:
There have been DNS issues while running CI jobs for the openstack
charms, when I captured the dns traffic in one of the nova-compute
units[0][1], it can be seen how certain queries are malformed:
~ $ tshark -r dns-port-53.pcap | grep -i malformed | tail -n 2
15403
The fix for this bug will be available in neutron-19.1.0 which at the
moment is available in the -proposed pockets for Impish and Xena, more
details on the progress of the point release can be found at
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1956991
--
You received this bug
Marking jammy as fix committed since package
neutron_19.0.0+git2022010514.7aba1bddab-0ubuntu1[0] contains the fix
that was merged in upstream[1]
[0]
https://launchpad.net/ubuntu/+source/neutron/2:19.0.0+git2022010514.7aba1bddab-0ubuntu1
[1]
** Patch added: "lp1951841_impish.debdiff"
https://bugs.launchpad.net/charm-ovn-chassis/+bug/1951841/+attachment/5552146/+files/lp1951841_impish.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
+ When the ovn-controller daemon elects a new leader is expected that
+ clients reconnect to that new instance, for the case of Xena the
+ reconnect attempt will also call register_metadata_agent()[0] and this
+ method enforces that OVS system-id is formatted
** Changed in: neutron (Ubuntu Impish)
Assignee: (unassigned) => Felipe Reyes (freyes)
** Changed in: neutron (Ubuntu Impish)
Status: New => Triaged
** Summary changed:
- ovn metadata agent randomly timing out
+ [SRU] ovn metadata agent randomly timing out
--
You received th
- Marking charm-ovn-chassis as invalid since the issue is in neutron itself and
not the charm or how it drives the workload.
- Adding tasks for Ubuntu/Impish and cloud-archive/xena.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This change[0] was merged in stable/xena, this relaxes the check that
ovs system-id must be a uuid formatted string, now when it can't parse
it as a uuid it will (re)generate a uuid using uuid.uuid5(), which will
use as input a hardcoded UUID (as namespace) and the chassis name
string.
[0]
** Also affects: charm-designate
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/1941988
Title:
Designate DNS – Secondary zone is failed to be created and
Public bug reported:
The summary says it all.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
Public bug reported:
According to this bug[0] and these patches[1][2][3] the support to emit
a ICMP "need to fragment" packet was added in ovn-21.09, Wallaby UCA
carries ovn-20.12
This limitation becomes a problem when the overlay network is configured
to use jumbo frames and the external
** Changed in: charm-neutron-gateway
Milestone: None => 21.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944424
Title:
AppArmor causing HA routers to be in backup state on wallaby-focal
To
** Also affects: ironic (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/1943765
Title:
ipmitool "timing" flags are not working as expected causing
Since the -16 version of the kernel was not available anymore, the bug
was back for me. I then downloaded and installed 5.11.1-051101-generic
with mainline and the bug is NOT happening with this kernel version.
Hope this info helps. Thanks.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1837437 ***
https://bugs.launchpad.net/bugs/1837437
I just got this error and there is no way to recover my data? It's lost?
Such a critical bug and no solution?!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The above command didn't make any difference. My computer doesn't even
have a light sensor.
I have tried this before but I just tried again to make sure. I will
have to keep holding the kernel version for now.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Hey thanks. If it's feature why it doesn't happen on this particular
kernel version?
Also my power settings does not show this option. I already tried
changing it with dconf-editor.
I still think it's a bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Hello guys!
The brightness of the screen on my laptop (Dell 7573 with touch ips 1080
panel) slightly changes randomly when using the laptop builtin display.
It feels the same as I changed the brightness one step using the
keyboard keys.
Here is a video:
Public bug reported:
Los siguientes paquetes tienen dependencias incumplidas:
libpq-dev : Depende: libpq5 (= 12.7-0ubuntu0.20.04.1) pero 13.3-1.pgdg20.04+1
va a ser instalado
E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos.
ProblemType: Package
DistroRelease: Ubuntu
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
Focal/Groovy deploy creates a 'node1' node
To manage notifications about this bug go to:
Same output in two Ubuntu server 20.04:
...
0: Trying to bind fd 46 to <127.0.0.1:3478>: errno=98
0: Cannot bind TLS/TCP listener socket to addr 127.0.0.1:3478
0: Trying to bind TLS/TCP listener socket to addr 127.0.0.1:3478, again...
etc..
I have tried AmbientCapabilities=CAP_NET_BIND_SERVICE
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219
Title:
context deadline exceeded: unknown in containerd with latest runc
version
To manage notifications about this bug
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783184
Title:
neutron-ovs-cleanup can have unintended side effects
To manage notifications about this bug go to:
Public bug reported:
i was in the installation when apeared the error saying about my cd/rom,
but he was unpluged and i donno what to do.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.10
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux
Public bug reported:
Every time I open audacity (this bugs come from old releases too) the main
sound of the ubuntu system comes muted.
I have to open sound properties and uncheck mute checkbox..
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: audacity 2.3.3-1build1
ProcVersionSignature:
Public bug reported:
Every update of ubuntu I have to maintain 5.3.0-18 on boot, because 5.4
and newer does not compile DKMS sucessfully making sound not working,
wifi not working and screen with bad resolution
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core
** Changed in: maas
Assignee: Felipe Reyes (freyes) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880495
Title:
Upgrade from 1.95 to 2.35 failure because col
I can confirm UX433F without extra symbols working properly turning On/Off
option from the numpad button is also working without issues.
Thanks, Mohamed!
El mié, 7 abr 2021 a las 16:00, Leesa (<1810...@bugs.launchpad.net>)
escribió:
> F8 was the first thing I commented out, I vote for removal
Hi,
This is a workaround you can use temporarily:
$ wget -O- http://ddebs.ubuntu.com/dbgsym-release-key.asc | sudo apt-
key add -
$ sudo apt update
The key was extended temporarily.
Best,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
The public key used by the debugging symbols repository
/usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu-
dbgsym-keyring expired.
$ apt policy ubuntu-dbgsym-keyring
ubuntu-dbgsym-keyring:
Installed: 2020.02.11.2
Candidate: 2020.02.11.2
Version
I really appreciate Daniel, thanks !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916243
Title:
Xorg unable to select nvidia
To manage notifications about this bug go to:
To test this I deployed a Focal based CDK environment, then launched a
machine running groovy and scp'ed /root from kubernetes-master/0 to that
new machine and executed sosreport, the verification executed correctly.
Here it's the evidence.
Before the patch:
root@juju-321ff4-k8s-11:~# cat
Flannel doesn't like to be installed in groovy, I will need to give some
extra cycles to this verification.
unit-flannel-2: 15:59:56 INFO unit.flannel/2.juju-log Invoking reactive
handler: reactive/flannel.py:228:set_flannel_version
unit-flannel-2: 15:59:56 ERROR unit.flannel/2.juju-log Hook
I tested the package available in focal-proposed, and it could capture
correctly information that before the patch couldn't, for example:
Before the patch:
root@juju-867473-k8s-4:~# cat
Public bug reported:
Xorg unable to select nvidia, always insisting in intel graphic card
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
.tmp.unity_support_test.0:
On Sat, 2021-02-06 at 16:01 +, Eric Desrochers wrote:
> @freyes,
>
> Can you please fill the SRU template ? And I'll proceed with the
> sponsoring along with all the other patches waiting for SRU.
done ;-)
** Description changed:
+ [Impact]
+
+ Running sosreport in a CDK deployed
Public bug reported:
I was trying to install Ubuntu in dual boot and it crashed at the end of
the installation with Grub fatal problem.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic
Funny I was having this problem, or at least similar, and I found out
the wifi was interfering. Moving the router away from the laptop
resolved the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1824559 ***
https://bugs.launchpad.net/bugs/1824559
Funny I was having this problem, or at least similar, and I found out
the wifi was interfering. Moving the router away from the laptop
resolved the issue.
--
You received this bug notification because you
Adding a task for libvirt at Ubuntu/focal since this patch[0] might need
to be backported.
[0]
https://github.com/libvirt/libvirt/commit/ae9e6c2a2b75d958995c661f7bb64ed4353a6404
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Focal)
Nevermind, this solved my problem:
sudo apt-get purge grub\*
sudo apt-get install grub-efi
sudo apt-get autoremove
sudo update-grub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872077
Title:
I'm having this same issue with 1.142.9+2.04-1ubuntu26.7.
Setting up grub-efi-amd64-signed (1.142.9+2.04-1ubuntu26.7) ...
Installing grub to /boot/efi.
Installing for x86_64-efi platform.
Installation finished. No error reported.
mount: /var/lib/grub/esp: mount point does not exist.
dpkg: error
Public bug reported:
It's not working.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libnvidia-common-450-server (not installed)
ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
Uname: Linux 5.4.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
Just some history, in the past we attempted to disable unattended-
upgrades (as a config option) in the hacluster charm, but it was decided
that it wasn't the right place to get this addressed.
Bug https://bugs.launchpad.net/charm-hacluster/+bug/1826898
** Tags added: sts
--
You received this
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899455
Title:
[SRU] openvswitch 2.12.1
To manage notifications about this bug go to:
Refiled this here, as Focal currently doesn't provide python3-os-ken >=
1.2 which includes the fix mentioned by @j-harbott
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898886
Title:
Can't
** Also affects: python-os-ken (Ubuntu)
Importance: Undecided
Status: New
** Also affects: charm-neutron-dynamic-routing
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 3452 matches
Mail list logo
