Hello Slawomir,
could you please provide the following information:
$ sudo multipath -v3 -ll
$ sudo multipath -t
$ sudo udevadm info -e
$ sudo multipathd show devices
$ sudo multipathd show paths
$ sudo multipathd show maps status
$ sudo multipathd show maps stats
Feel free to attach
Hello Slawomir,
could you please provide the following information:
$ sudo multipath -v3 -ll
$ sudo multipath -t
$ sudo udevadm info -e
$ sudo multipathd show devices
$ sudo multipathd show paths
$ sudo multipathd show maps status
$ sudo multipathd show maps stats
Feel free to attach
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subs
Hello Javier,
Actually the release notes for the version you were at:
https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes#netplan.io
already deprecated ifupdown in favor of netplan.io.
Upgrade path to 20.04 has likely uninstalled bridge-utils because of
that. You can keep using ifupdown + vlan +
Hello Javier,
Actually the release notes for the version you were at:
https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes#netplan.io
already deprecated ifupdown in favor of netplan.io.
Upgrade path to 20.04 has likely uninstalled bridge-utils because of
that. You can keep using ifupdown + vlan +
** Also affects: tmux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: tmux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: tmux (Ubuntu Focal)
Status: New => Triaged
** Changed in: tmux (Ubuntu Groovy)
Status: New => Triaged
** Also affects: tmux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: tmux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: tmux (Ubuntu Focal)
Status: New => Triaged
** Changed in: tmux (Ubuntu Groovy)
Status: New => Triaged
** Changed in: qemu (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1875012
Title:
KVM internal error. Suberror: 1 -- emulation failure
To manage
** Changed in: qemu (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875012
Title:
KVM internal error. Suberror: 1 -- emulation failure
To manage notifications
This really looks like an environment issue:
Setting up smartmontools (7.1-1build1) ...
Configuration file '/etc/default/smartmontools'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your
Hum,
This might be something else... chances for 2 bugs:
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1874953 (this)
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1875010 (similar)
not to have pager is lower than just 1.
I'm marking the other bug as a duplicate
Looks like "D" option is not working, two bugs with problems...
Need to double check.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1874953
Title:
package smartmontools 7.1-1build1
This really looks like an environment issue:
Setting up smartmontools (7.1-1build1) ...
Configuration file '/etc/default/smartmontools'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your
*** This bug is a duplicate of bug 1874953 ***
https://bugs.launchpad.net/bugs/1874953
** Changed in: smartmontools (Ubuntu)
Status: New => Triaged
** This bug has been marked a duplicate of bug 1874953
package smartmontools 7.1-1build1 failed to install/upgrade: conffile
*** This bug is a duplicate of bug 1874953 ***
https://bugs.launchpad.net/bugs/1874953
** Changed in: smartmontools (Ubuntu)
Status: New => Triaged
** This bug has been marked a duplicate of bug 1874953
package smartmontools 7.1-1build1 failed to install/upgrade: conffile
Looks like "D" option is not working, two bugs with problems...
Need to double check.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874953
Title:
package smartmontools 7.1-1build1 failed to
Hum,
This might be something else... chances for 2 bugs:
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1874953 (this)
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1875010 (similar)
not to have pager is lower than just 1.
I'm marking the other bug as a duplicate
** Also affects: nginx (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nginx (Ubuntu Groovy)
Importance: Medium
Status: Triaged
** Changed in: nginx (Ubuntu Focal)
Status: New => Triaged
** Changed in: nginx (Ubuntu Focal)
Importance: Undecided =>
Hello Sjef,
Thank you for taking the time to file a bug report.
Would you mind providing more information about your issue ?
1) Have you tried the same with a more recent apache/ubuntu combination ?
2) Have you tried the latest 20.04 LTS with the same configuration ? Does it
face this issue ?
** Also affects: apache2 (Ubuntu Groovy)
Importance: Undecided
Status: Triaged
** Also affects: apache2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: apache2 (Ubuntu Focal)
Status: New => Triaged
** Changed in: apache2 (Ubuntu Focal)
Importance:
Hello Sjef,
Thank you for taking the time to file a bug report.
Would you mind providing more information about your issue ?
1) Have you tried the same with a more recent apache/ubuntu combination ?
2) Have you tried the latest 20.04 LTS with the same configuration ? Does it
face this issue ?
** Also affects: nginx (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nginx (Ubuntu Groovy)
Importance: Medium
Status: Triaged
** Changed in: nginx (Ubuntu Focal)
Status: New => Triaged
** Changed in: nginx (Ubuntu Focal)
Importance: Undecided =>
** Also affects: apache2 (Ubuntu Groovy)
Importance: Undecided
Status: Triaged
** Also affects: apache2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: apache2 (Ubuntu Focal)
Status: New => Triaged
** Changed in: apache2 (Ubuntu Focal)
Importance:
Thanks for reporting this...
I have opened an issue upstream (Debian):
https://salsa.debian.org/nginx-team/nginx/-/issues/2
Let's see what maintainers say and then we check how to move further.
** Changed in: nginx (Ubuntu)
Importance: Undecided => Medium
** Bug watch added:
Thanks for reporting this...
I have opened an issue upstream (Debian):
https://salsa.debian.org/nginx-team/nginx/-/issues/2
Let's see what maintainers say and then we check how to move further.
** Changed in: nginx (Ubuntu)
Importance: Undecided => Medium
** Bug watch added:
** Changed in: nginx (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1874831
Title:
libnginx-mod-nchan distributes old/incompatible module
To manage
** Changed in: nginx (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874831
Title:
libnginx-mod-nchan distributes old/incompatible module
To manage
This is the error during upgrade:
Preparing to unpack .../840-phppgadmin_7.12.1+dfsg-1_all.deb ...
Unpacking phppgadmin (7.12.1+dfsg-1) over (5.1+ds-3) ...
...
Setting up phppgadmin (7.12.1+dfsg-1) ...
Installing new version of config file /etc/phppgadmin/config.inc.php ...
Package apache2 is not
This is the error during upgrade:
Preparing to unpack .../840-phppgadmin_7.12.1+dfsg-1_all.deb ...
Unpacking phppgadmin (7.12.1+dfsg-1) over (5.1+ds-3) ...
...
Setting up phppgadmin (7.12.1+dfsg-1) ...
Installing new version of config file /etc/phppgadmin/config.inc.php ...
Package apache2 is not
Ah nm, I see you subscribed the release team already, their call then!
Cheers o/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875231
Title:
[SRU] [20.04] Update NGINX version string to 1.18.0
To
Ah nm, I see you subscribed the release team already, their call then!
Cheers o/
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1875231
Title:
[SRU] [20.04] Update NGINX version string to
$ git log --pretty=oneline release-1.17.10..release-1.18.0
e6b3a11581a8040baf7aded3319b0dec433b2461 (tag: release-1.18.0)
nginx-1.18.0-RELEASE
6acdee5e3213fc6054f3bbb23a44ef2576278f63 Stable branch.
3ba88365b5acef17f01671cd969c909dee5e2cde release-1.17.10 tag
I agree there aren't any changes in
$ git log --pretty=oneline release-1.17.10..release-1.18.0
e6b3a11581a8040baf7aded3319b0dec433b2461 (tag: release-1.18.0)
nginx-1.18.0-RELEASE
6acdee5e3213fc6054f3bbb23a44ef2576278f63 Stable branch.
3ba88365b5acef17f01671cd969c909dee5e2cde release-1.17.10 tag
I agree there aren't any changes in
Hello Rolf,
I just tried to install it in a clean environment:
(c)rafaeldtinoco@freeradius:~$ journalctl _SYSTEMD_UNIT=freeradius.service
-- Logs begin at Mon 2020-04-20 01:53:09 UTC, end at Mon 2020-04-27 20:13:36
UTC. --
Apr 27 20:11:18 freeradius freeradius[1762]: FreeRADIUS Version 3.0.20
Hello Rolf,
I just tried to install it in a clean environment:
(c)rafaeldtinoco@freeradius:~$ journalctl _SYSTEMD_UNIT=freeradius.service
-- Logs begin at Mon 2020-04-20 01:53:09 UTC, end at Mon 2020-04-27 20:13:36
UTC. --
Apr 27 20:11:18 freeradius freeradius[1762]: FreeRADIUS Version 3.0.20
** Changed in: pacemaker (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
Focal deploy creates a 'node1' node
To manage
** Changed in: pacemaker (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/1874719
Title:
Focal deploy creates a 'node1' node
To manage notifications about this
Here you will find the autopkgtests for pacemaker:
http://autopkgtest.ubuntu.com/packages/p/pacemaker/focal/amd64
the installation ends with a corosync node online:
Cluster Summary:
* Stack: corosync
* Current DC: node1 (version 2.0.3-4b1f869f0f) - partition with quorum
* Last updated:
Here you will find the autopkgtests for pacemaker:
http://autopkgtest.ubuntu.com/packages/p/pacemaker/focal/amd64
the installation ends with a corosync node online:
Cluster Summary:
* Stack: corosync
* Current DC: node1 (version 2.0.3-4b1f869f0f) - partition with quorum
* Last updated:
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
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 deploy creates a 'node1' n
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
Focal deploy crea
https://bazaar.launchpad.net/~ubuntu-sru/britney/hints-ubuntu-
bionic/revision/3173
** Changed in: ipset (Ubuntu Bionic)
Status: Confirmed => Fix Released
** Changed in: ipset (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: ipset (
https://bazaar.launchpad.net/~ubuntu-sru/britney/hints-ubuntu-
bionic/revision/3173
** Changed in: ipset (Ubuntu Bionic)
Status: Confirmed => Fix Released
** Changed in: ipset (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: ipset (
On 02/04/2020 01:04, Alex Murray wrote:
> Upstream have merged in a fix for the world-writable targetcli-fb daemon
> socket - https://github.com/open-iscsi/targetcli-fb/issues/162 - and
> assigned CVE-2020-10699 for it - but there has been no official release.
> With this fix in place, I would be
On 02/04/2020 01:04, Alex Murray wrote:
> Upstream have merged in a fix for the world-writable targetcli-fb daemon
> socket - https://github.com/open-iscsi/targetcli-fb/issues/162 - and
> assigned CVE-2020-10699 for it - but there has been no official release.
> With this fix in place, I would be
Adding block-proposed-bionic so this fix can be added if there is any
SRU to ipset package.
Proposed forcing bad test here:
https://code.launchpad.net/~rafaeldtinoco/britney/lp1873447/+merge/382820
** Tags added: block-proposed-bionic
** Branch linked: lp:~rafaeldtinoco/britney/lp1873447
--
Adding block-proposed-bionic so this fix can be added if there is any
SRU to ipset package.
Proposed forcing bad test here:
https://code.launchpad.net/~rafaeldtinoco/britney/lp1873447/+merge/382820
** Tags added: block-proposed-bionic
** Branch linked: lp:~rafaeldtinoco/britney/lp1873447
--
Since this was supposed to be a SRU, but it is only a autopkgtest fix:
- patch: 2a66a0df03788d8a7e95972847545de0ade0dd8e fixes the issue
- the patch only touches the autopkgtests (not suitable for SRU)
- last time test ran was at the end of 2018 and it worked
- after that, kernel has included
Since this was supposed to be a SRU, but it is only a autopkgtest fix:
- patch: 2a66a0df03788d8a7e95972847545de0ade0dd8e fixes the issue
- the patch only touches the autopkgtests (not suitable for SRU)
- last time test ran was at the end of 2018 and it worked
- after that, kernel has included
Was able to reproduce:
hash:net6,port,net6: Range: Create a set: passed
hash:net6,port,net6: Range: Add zero valued element: FAILED
Failed test: /sbin/ipset 2>.foo.err -A test 2:0:0::1/24,0,0:0:0::0/0
autopkgtest [18:08:23]: test regression: ---]
autopkgtest [18:08:23]: test
Was able to reproduce:
hash:net6,port,net6: Range: Create a set: passed
hash:net6,port,net6: Range: Add zero valued element: FAILED
Failed test: /sbin/ipset 2>.foo.err -A test 2:0:0::1/24,0,0:0:0::0/0
autopkgtest [18:08:23]: test regression: ---]
autopkgtest [18:08:23]: test
$ git tag --contains 2a66a0df03788d8a7e95972847545de0ade0dd8e
v7.0
v7.1
v7.3
v7.4
v7.5
v7.6
Affects Bionic only.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1873447
Title:
$ git tag --contains 2a66a0df03788d8a7e95972847545de0ade0dd8e
v7.0
v7.1
v7.3
v7.4
v7.5
v7.6
Affects Bionic only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873447
Title:
[bionic][autopkgtest]
$ rmadison ipset
ipset | 6.11-2 | precise/universe |
ipset | 6.20.1-1 | trusty/universe |
ipset | 6.29-1 | xenial |
ipset | 6.34-1 | bionic |
ipset | 7.1-0ubuntu1 | disco|
ipset | 7.1-0ubuntu1 | eoan |
ipset | 7.5-1~exp1
$ rmadison ipset
ipset | 6.11-2 | precise/universe |
ipset | 6.20.1-1 | trusty/universe |
ipset | 6.29-1 | xenial |
ipset | 6.34-1 | bionic |
ipset | 7.1-0ubuntu1 | disco|
ipset | 7.1-0ubuntu1 | eoan |
ipset | 7.5-1~exp1
Summary...
For Ubuntu Bionic, dpkg triggers for systemd (237-3ubuntu10.39) might
have caused systemd to hang:
[ 363.776878] wait_for_completion+0xba/0x140
[ 363.776890] __flush_work+0x15b/0x210
[ 363.776901] flush_delayed_work+0x41/0x50
[ 363.776908]
Summary...
For Ubuntu Bionic, dpkg triggers for systemd (237-3ubuntu10.39) might
have caused systemd to hang:
[ 363.776878] wait_for_completion+0xba/0x140
[ 363.776890] __flush_work+0x15b/0x210
[ 363.776901] flush_delayed_work+0x41/0x50
[ 363.776908]
Hello Jeff,
I have opened a card to keep track of this work in 20.10. I'm not sure
that a MIR will be possible (for ndctl/ipmctl) based on previous denial
but we can take a look later after we MERGE latest upstream release
(02.00.00.3759) to 20.10.
For now I'm closing this bug as there is
Hello Jeff,
I have opened a card to keep track of this work in 20.10. I'm not sure
that a MIR will be possible (for ndctl/ipmctl) based on previous denial
but we can take a look later after we MERGE latest upstream release
(02.00.00.3759) to 20.10.
For now I'm closing this bug as there is
Failed test: /sbin/ipset 2>.foo.err -A test 2:0:0::1/24,0,0:0:0::0/0
** Affects: ipset (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: ipset (Ubuntu Bionic)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** A
Failed test: /sbin/ipset 2>.foo.err -A test 2:0:0::1/24,0,0:0:0::0/0
** Affects: ipset (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: ipset (Ubuntu Bionic)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** A
Okay, I had verified this from the day in it landed in -proposed. It is
working as expected (https://discourse.ubuntu.com/t/ubuntu-high-
availability-corosync-pacemaker-shared-disk-environments/). I'm marking
this as verification-done as it has stayed in -proposed for sometime now
and no bad
Okay, I had verified this from the day in it landed in -proposed. It is
working as expected (https://discourse.ubuntu.com/t/ubuntu-high-
availability-corosync-pacemaker-shared-disk-environments/). I'm marking
this as verification-done as it has stayed in -proposed for sometime now
and no bad
Okay, I had verified this from the day in it landed in -proposed. It is
working as expected (https://discourse.ubuntu.com/t/ubuntu-high-
availability-corosync-pacemaker-shared-disk-environments/). I'm marking
this as verification-done as it has stayed in -proposed for sometime now
and no bad
Okay, I had verified this from the day in it landed in -proposed. It is
working as expected (https://discourse.ubuntu.com/t/ubuntu-high-
availability-corosync-pacemaker-shared-disk-environments/). I'm marking
this as verification-done as it has stayed in -proposed for sometime now
and no bad
Based on case history, to fully address this to all still supported
Ubuntu releases:
autofs | 5.1.2-1ubuntu3 | bionic |
autofs | 5.1.2-1ubuntu3.1 | bionic-updates |
autofs | 5.1.2-4ubuntu2 | disco |
autofs | 5.1.5-1ubuntu1 | eoan|
autofs | 5.1.6-2
Based on case history, to fully address this to all still supported
Ubuntu releases:
autofs | 5.1.2-1ubuntu3 | bionic |
autofs | 5.1.2-1ubuntu3.1 | bionic-updates |
autofs | 5.1.2-4ubuntu2 | disco |
autofs | 5.1.5-1ubuntu1 | eoan|
autofs | 5.1.6-2
** Also affects: autofs (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: autofs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: autofs (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: autofs (Ubuntu Eoan)
Status: New =>
** Also affects: autofs (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: autofs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: autofs (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: autofs (Ubuntu Eoan)
Status: New =>
Simon,
Could you please help identifying the current status of this bug ? Your
original merge requests were postponed to the next SRU for rsyslog in
Bionic, Disco and Eoan, correct ?
During verification time you discovered the difference between "bin" and
"sbin" for the apparmor rule, is that it
Simon,
Could you please help identifying the current status of this bug ? Your
original merge requests were postponed to the next SRU for rsyslog in
Bionic, Disco and Eoan, correct ?
During verification time you discovered the difference between "bin" and
"sbin" for the apparmor rule, is that it
Marking as Fix Released for Disco:
+rsyslog (8.32.0-1ubuntu7.1) disco; urgency=medium
+
+ [ Simon Deziel ]
+ * d/usr.sbin.rsyslogd: allow reading/mmap'ing rsyslog binary
+This is required for usage inside containers (LP: #1827253)
+
+ -- Christian Ehrhardt Mon, 14 Oct 2019
08:53:03 +0200
Marking as Fix Released for Disco:
+rsyslog (8.32.0-1ubuntu7.1) disco; urgency=medium
+
+ [ Simon Deziel ]
+ * d/usr.sbin.rsyslogd: allow reading/mmap'ing rsyslog binary
+This is required for usage inside containers (LP: #1827253)
+
+ -- Christian Ehrhardt Mon, 14 Oct 2019
08:53:03 +0200
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
user@box:~$ date
Mon Apr 13 17:11:35 EDT 2020
"box" machine -> Apr 13 17:11 EDT
user@box:~$ ./reset-power-consumption-meter
+ sudo ipmi-oem dell reset-power-consumption-data
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
user@box:~$ date
Mon Apr 13 17:11:35 EDT 2020
"box" machine -> Apr 13 17:11 EDT
user@box:~$ ./reset-power-consumption-meter
+ sudo ipmi-oem dell reset-power-consumption-data
Unfortunately there is an issue with autopkgtest and uploaded version
won't migrate.
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1872877
will fix it. There will be a new upload tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Server, which
Unfortunately there is an issue with autopkgtest and uploaded version
won't migrate.
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1872877
will fix it. There will be a new upload tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
resource-agents has the following autopkgtest in control file:
...
# currently failing on Ubuntu autopkgtest setup for networking differences, so
skip there
# Working in Debci, but compared to badtest retains all the other tests coverage
Test-Command: [ "`lsb_release -is`" = "Ubuntu" ] ||
resource-agents has the following autopkgtest in control file:
...
# currently failing on Ubuntu autopkgtest setup for networking differences, so
skip there
# Working in Debci, but compared to badtest retains all the other tests coverage
Test-Command: [ "`lsb_release -is`" = "Ubuntu" ] ||
resource-agents has the following autopkgtest in control file:
...
# currently failing on Ubuntu autopkgtest setup for networking differences, so
skip there
# Working in Debci, but compared to badtest retains all the other tests coverage
Test-Command: [ "`lsb_release -is`" = "Ubuntu" ] ||
resource-agents has the following autopkgtest in control file:
...
# currently failing on Ubuntu autopkgtest setup for networking differences, so
skip there
# Working in Debci, but compared to badtest retains all the other tests coverage
Test-Command: [ "`lsb_release -is`" = "Ubuntu" ] ||
Public bug reported:
When doing the merge for v4.5.0 for resource-agents:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1866383
I missed an autopkgtest issue with bind9 dependency not being
satisfiable in Ubuntu (it only works in Debian).
** Affects: resource-agents (Ubuntu)
Public bug reported:
When doing the merge for v4.5.0 for resource-agents:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1866383
I missed an autopkgtest issue with bind9 dependency not being
satisfiable in Ubuntu (it only works in Debian).
** Affects: resource-agents (Ubuntu)
** Changed in: qemu (Ubuntu Eoan)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: qemu
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subs
** Changed in: sbd (Ubuntu)
Status: New => Confirmed
** Changed in: sbd (Ubuntu Bionic)
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/1787619
Title:
** Changed in: qemu (Ubuntu Eoan)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: qemu
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: corosync-qdevice (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1733889
Title:
wrong datatype
** Changed in: corosync-qdevice (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733889
Title:
wrong datatype key in c
** Changed in: sbd (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Also affects: sbd (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Hello Nicolay,
Thank you for taking the time to file a bug report.
Could you please describe your problem with more detailed information ?
mysql-server-8.0 default installation in 20.04 does NOT enable SSL by
default, in the server, nor in the client:
"""
mysql> status;
--
mysql
Hello Nicolay,
Thank you for taking the time to file a bug report.
Could you please describe your problem with more detailed information ?
mysql-server-8.0 default installation in 20.04 does NOT enable SSL by
default, in the server, nor in the client:
"""
mysql> status;
--
mysql
This looks like a genuine bug for apache upgrade path. Triaged.
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865218
Title:
mod_php gets disabled during
This looks like the discussion we had in the past about having already
used configuration files and the end user not choosing to use the new
configuration file. Should postinst script deal with existing
configuration files or keep them untouched ? To discuss in the triage
meeting.
** Tags added:
This looks like a genuine bug for apache upgrade path. Triaged.
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1865218
Title:
mod_php gets disabled
This looks like the discussion we had in the past about having already
used configuration files and the end user not choosing to use the new
configuration file. Should postinst script deal with existing
configuration files or keep them untouched ? To discuss in the triage
meeting.
** Tags added:
** Changed in: mysql-8.0 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872541
Title:
MySQL client fails to connect, seems to force SSL
To manage
Thank you for taking the time to file a bug report.
Could you please describe detailed steps in order to reproduce this
issue ?
Something like:
1) Configure smb.conf like this ""
2) Restart smb service
3) Try to access remote shared folder using smbfs:///
4) If it is authenticated or
** Changed in: mysql-8.0 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to mysql-8.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1872541
Title:
MySQL client fails to connect, seems to force SSL
To
Thank you for taking the time to file a bug report.
Could you please describe detailed steps in order to reproduce this
issue ?
Something like:
1) Configure smb.conf like this ""
2) Restart smb service
3) Try to access remote shared folder using smbfs:///
4) If it is authenticated or
601 - 700 of 3504 matches
Mail list logo
