[Bug 1875231] Re: [SRU] [20.04] Update NGINX version string to 1.18.0

2020-04-27 Thread Rafael David Tinoco
$ 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 between 1.17.10 and 1.18.0.

Unsure about the change though.

nginx
  Reverse Depends: diaspora-common (0.7.6.1+debian1)
  Reverse Depends: fusiondirectory (1.3-2)
  Reverse Depends: kopano-webapp-nginx (3.5.14+dfsg1.orig-1)
  Reverse Depends: python3-certbot-nginx (0.39.0-1)
  Reverse Depends: rainloop (1.12.1-2)

as long as there are no hard dependencies on versioning (wonder if
you're thinking in changing deb version as well)... Ubuntu SRU team
would make the last call anyway.

Let me know if you're pursuing this, I'm flagging as a server team low
priority queue item for now.

Thanks @teward!

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1875231

Title:
  [SRU] [20.04] Update NGINX version string to 1.18.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1875231/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874730] Re: package apache2 2.4.41-4ubuntu3 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1

2020-04-27 Thread Rafael David Tinoco
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 configured yet. Will defer actions by package phppgadmin.
...
info: Executing deferred 'a2enconf phppgadmin' for package phppgadmin
ERROR: Conf phppgadmin does not exist!
dpkg: error processing package apache2 (--configure):
 installed apache2 package post-installation script subprocess returned error 
exit status 1

The module wasn't able to be enabled after apache2 (and the module) was
updated.

** Changed in: apache2 (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/1874730

Title:
  package apache2 2.4.41-4ubuntu3 failed to install/upgrade: installed
  apache2 package post-installation script subprocess returned error
  exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1874730/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874565] Re: freeradius fails to install in focal

2020-04-27 Thread Rafael David Tinoco
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
Apr 27 20:11:18 freeradius freeradius[1762]: Copyright (C) 1999-2019 The 
FreeRADIUS server project and contributors
Apr 27 20:11:18 freeradius freeradius[1762]: There is NO warranty; not even for 
MERCHANTABILITY or FITNESS FOR A
Apr 27 20:11:18 freeradius freeradius[1762]: PARTICULAR PURPOSE
Apr 27 20:11:18 freeradius freeradius[1762]: You may redistribute copies of 
FreeRADIUS under the terms of the
Apr 27 20:11:18 freeradius freeradius[1762]: GNU General Public License
Apr 27 20:11:18 freeradius freeradius[1762]: For more information about these 
matters, see the file named COPYRIGHT
Apr 27 20:11:18 freeradius freeradius[1762]: Starting - reading configuration 
files ...
Apr 27 20:11:18 freeradius freeradius[1762]: Debugger not attached
Apr 27 20:11:18 freeradius freeradius[1762]: Creating attribute Unix-Group
Apr 27 20:11:18 freeradius freeradius[1762]: Please use tls_min_version and 
tls_max_version instead of disable_tlsv1
Apr 27 20:11:18 freeradius freeradius[1762]: Please use tls_min_version and 
tls_max_version instead of disable_tlsv1_2
Apr 27 20:11:18 freeradius freeradius[1762]: tls: Using cached TLS 
configuration from previous invocation
Apr 27 20:11:18 freeradius freeradius[1762]: tls: Using cached TLS 
configuration from previous invocation
Apr 27 20:11:18 freeradius freeradius[1762]: rlm_cache (cache_eap): Driver 
rlm_cache_rbtree (module rlm_cache_rbtree) loaded and linked
Apr 27 20:11:18 freeradius freeradius[1762]: rlm_mschap (mschap): using 
internal authentication
Apr 27 20:11:18 freeradius freeradius[1762]: rlm_detail (auth_log): 
'User-Password' suppressed, will not appear in detail output
Apr 27 20:11:18 freeradius freeradius[1762]: Ignoring "sql" (see 
raddb/mods-available/README.rst)
Apr 27 20:11:18 freeradius freeradius[1762]: Ignoring "ldap" (see 
raddb/mods-available/README.rst)
Apr 27 20:11:18 freeradius freeradius[1762]:  # Skipping contents of 'if' as it 
is always 'false' -- /etc/freeradius/3.0/sites-enabled/inner-tunnel:336
Apr 27 20:11:18 freeradius freeradius[1762]: radiusd:  Skipping IP 
addresses and Ports 
Apr 27 20:11:18 freeradius freeradius[1762]: Configuration appears to be OK



(c)rafaeldtinoco@freeradius:~$ systemctl status freeradius.service
● freeradius.service - FreeRADIUS multi-protocol policy server
 Loaded: loaded (/lib/systemd/system/freeradius.service; disabled; vendor 
preset: enabled)
 Active: active (running) since Mon 2020-04-27 20:11:18 UTC; 3min 6s ago
   Docs: man:radiusd(8)
 man:radiusd.conf(5)
 http://wiki.freeradius.org/
 http://networkradius.com/doc/
   Main PID: 1764 (freeradius)
 Status: "Processing requests"
  Tasks: 6 (limit: 1128)
 Memory: 78.1M
 CGroup: /system.slice/freeradius.service
 └─1764 /usr/sbin/freeradius -f



Perhaps you missed to install the following package: "freeradius-config"
?

It contains: https://paste.ubuntu.com/p/QTRpjpSPQB/

The files you seem to be looking for.

Let me know if there is any other issue, OR you found a better way to
reproduce the issue you're facing, by re-opening this bug setting its
state back to New.

Thank you

Rafael


** Changed in: freeradius (Ubuntu)
   Status: New => Invalid

-- 
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/1874565

Title:
  freeradius fails to install in focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1874565/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875594] Re: multipathd failed to get udev uid, add missing path

2020-04-28 Thread Rafael David Tinoco
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 output files into this bug so I can check it.

-- 
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/1875594

Title:
  multipathd  failed to get udev uid, add missing path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1875594/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875594] Re: multipathd failed to get udev uid, add missing path

2020-04-28 Thread Rafael David Tinoco
I have found some upstream patches I'd like to bring to multipath-tools
for Focal:

5abeb33afedc013fb9996555ac79c4c711612fea (HEAD -> focal) libmultipath: fix 
sgio_get_vpd looping
d5cb76dc185ec5fd6822d9c8acc8b5a1218f2666 libmultipath: _init_foreign(): fix 
possible memory leak
c007a54882e45787f9e7c098d23c8d336b871406 libmultipath: remove_wwids(): fix 
possible leaks
8b15c32fb2bdb8ff2c086292da242badc1432248 libmultipath: replace_wwids(): fix 
possible fd leak
b2ed2805ffda32ffa8cdd5cb3a661632553c906f libmultipath: uevent_listen(): fix 
poll() retval check
2ccbc0072e5415b7acb0b36b33c180ef988a9f3a libmultipath: path_discovery: handle 
libudev errors
0069fcc68bf0d6e5169c5a57f7b2926c9b3988f0 libmultipath: lookup_binding(): don't 
rely on int overflow
f42f37f82fb4baf20934215b56e4c8591545f49e libmultipath: scan_devname: fix int 
overflow detection
1ae17e570b11e5361e1fa310481bc6f369918b30 libmultipath: format_devname: avoid 
buffer overflow

So I'd like to provide you a PPA with a new package containing those
fixes. For your particular case, the patch:

2ccbc0072e5415b7acb0b36b33c180ef988a9f3a libmultipath: path_discovery:
handle libudev errors

will likely accuse the error for the device but it won't make multipath
to repeat them as the device won't be monitored. (output from previous
comment is needed as well).

I'll add here a PPA and ask you to test packages from it if that is ok
for you.

Thanks in advance

-- 
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/1875594

Title:
  multipathd  failed to get udev uid, add missing path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1875594/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875594] Re: multipathd failed to get udev uid, add missing path

2020-04-28 Thread Rafael David Tinoco
Could you use the following PPA:

https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1875594

together with the output of the commands provided in comment #3 as the
feedback ?

I'd like to hear that the errors either appeared just once or they did
not appear with the PPA version (you can even compare before and after).
PPA contains multipath-tools package with several fixes BUT it still
might be the case that I need to add something else for your particular
case.

Thanks a lot for reporting this.

-rafaeldtinoco

-- 
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/1875594

Title:
  multipathd  failed to get udev uid, add missing path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1875594/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875594] Re: multipathd failed to get udev uid, add missing path

2020-04-28 Thread Rafael David Tinoco
** 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 subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1875594

Title:
  multipathd  failed to get udev uid, add missing path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1875594/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875594] Re: multipathd failed to get udev uid, add missing path

2020-04-28 Thread Rafael David Tinoco
** Tags added: block-proposed-focal

-- 
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/1875594

Title:
  multipathd  failed to get udev uid, add missing path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1875594/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874719] Re: Focal deploy creates a 'node1' node

2020-04-24 Thread Rafael David Tinoco
** 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 notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1874719/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874719] Re: Focal deploy creates a 'node1' node

2020-04-24 Thread Rafael David Tinoco
** 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 creates a 'node1' node

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1874719/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874719] Re: Focal deploy creates a 'node1' node

2020-04-24 Thread Rafael David Tinoco
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: Fri Apr 17 22:55:34 2020
  * Last change:  Fri Apr 17 22:55:22 2020 by hacluster via crmd on node1
  * 1 node configured
  * 0 resource instances configured

Node List:
  * Online: [ node1 ]

Active Resources:
  * No active resources

pacemakerPASS
pacemakerPASS

So, for some reason, this localhost corosync installation made the
service to be unavailable in your cause. I wonder if you have more logs
so we can check what happened for it not to be online.

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1874719/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1873447] Re: [bionic][autopkgtest] ipset failing autopkgtest after kmod sru

2020-04-22 Thread Rafael David Tinoco
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

-- 
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:
  [bionic][autopkgtest] ipset failing autopkgtest after kmod sru

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipset/+bug/1873447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1868882] Re: [SRU] Put ipmctl into Bionic (and update necessary deps)

2020-04-22 Thread Rafael David Tinoco
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 nothing to be done here until
20.10. I will include you in the 20.10 ndctl/ipmctl merge public bugs
for your awareness.

Thank you

Rafael

** Changed in: ipmctl (Ubuntu)
   Status: Triaged => Opinion

-- 
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/1868882

Title:
  [SRU] Put ipmctl into Bionic (and update necessary deps)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipmctl/+bug/1868882/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1872021] Re: commissioning fails due to hung tasks setting up ipmitool

2020-04-22 Thread Rafael David Tinoco
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]  fsnotify_wait_marks_destroyed+0x15/0x20
[  363.776912]  fsnotify_destroy_group+0x48/0xd0
[  363.776917]  inotify_release+0x1e/0x50
[  363.776923]  __fput+0xea/0x220
[  363.776929]  fput+0xe/0x10
[  363.776935]  task_work_run+0x9d/0xc0
[  363.776942]  exit_to_usermode_loop+0xc0/0xd0
[  363.776947]  do_syscall_64+0x121/0x130
[  363.776954]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

and

[  364.050206]  wait_for_completion+0xba/0x140
[  364.050238]  __synchronize_srcu.part.13+0x85/0xb0
[  364.050248]  synchronize_srcu+0x66/0xe0
[  364.050256]  fsnotify_mark_destroy_workfn+0x7b/0xe0
[  364.050262]  process_one_work+0x1de/0x420
[  364.050267]  worker_thread+0x228/0x410
[  364.050272]  kthread+0x121/0x140

and

[  364.326985]  wait_for_completion+0xba/0x140
[  364.326988]  __synchronize_srcu.part.13+0x85/0xb0
[  364.326993]  synchronize_srcu+0x66/0xe0
[  364.326995]  ? synchronize_srcu+0x66/0xe0
[  364.326996]  fsnotify_connector_destroy_workfn+0x4a/0x80
[  364.326998]  process_one_work+0x1de/0x420
[  364.326999]  worker_thread+0x253/0x410
[  364.327001]  kthread+0x121/0x140

All stack traces seem to come from "fsnotify" subsystem and waiting on
delayed work (completion) for fsnotify marks destruction after a
inotify_release() was called. Completion did not happen for the past 2
minutes. Without a kernel dump it is hard to tell if completion was
still ok - due to kthread being overloaded doing scheduled work and/or
the marks group destruction - or there was a dead lock for the
completion due to a kernel bug.

If this is reproducible, I think that having a kernel dump would help
identifying the issue. I'm letting the kernel team to handle this and
marking all other issues as dealt per previous comments.


** No longer affects: ipmitool (Ubuntu)

** Changed in: maas
   Status: New => Invalid

** Summary changed:

- commissioning fails due to hung tasks setting up ipmitool
+ [Ubuntu][Bionic] systemd caused kernel to hang on fsnotify wait-on-completion

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu)

** Project changed: linux => linux (Ubuntu)

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Medium

-- 
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/1872021

Title:
  [Ubuntu][Bionic] systemd caused kernel to hang on fsnotify wait-on-
  completion

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1872021/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 1854362] Re: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid, targetcli-fb

2020-04-23 Thread Rafael David Tinoco
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 happy to change the NACK to an ACK
> for targetcli-fb.
> 
> ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10699

Alex, I left the targetcli-fb MIR attempt to be handled at 20.10. I'll
continue this shortly and will handle this. Thanks for the highlight.

-- 
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/1854362

Title:
  [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb,
  urwid, targetcli-fb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1854362/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875594] Re: multipathd failed to get udev uid, add missing path

2020-04-29 Thread Rafael David Tinoco
VMware SCSI emulated disks:

Apr 29 09:27:26 | sda: uid_attribute = ID_SERIAL (setting: multipath internal)
Apr 29 09:27:26 | sda: no ID_SERIAL attribute
Apr 29 09:27:26 | sda: failed to get udev uid: Invalid argument
Apr 29 09:27:26 | 32:0:0:0: attribute vpd_pg83 not found in sysfs
Apr 29 09:27:26 | failed to read sysfs vpd pg83
Apr 29 09:27:26 | sda: failed to get sysfs uid: Invalid argument
Apr 29 09:27:26 | failed to issue vpd inquiry for pg83
Apr 29 09:27:26 | sda: failed to get sgio uid: No such file or directory

don't provide VPD PG83 support as it seems. Multipath does not have a
blacklist rule for those, I'll work in providing it. For now you should
blacklist those disks by adding:

blacklist {
device {
vendor "VMware"
product "Virtual disk"
}
}

in your /etc/multipath.conf file AND restarting multipath-tools service:

$ sudo systemctl restart multipath-tools

Let me know if messages disappear please.

Thank you!

-- 
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/1875594

Title:
  multipathd  failed to get udev uid, add missing path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1875594/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874831] Re: libnginx-mod-nchan distributes old/incompatible module

2020-04-27 Thread Rafael David Tinoco
** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1874831/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874953] Re: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127

2020-04-27 Thread Rafael David Tinoco
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 options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** smartmontools (Y/I/N/O/D/Z) [default=N] ? d
sh: 1: pager: not found
diff: standard output: Broken pipe
dpkg: error processing package smartmontools (--configure):
 conffile difference visualizer subprocess returned error exit status 127

Due to missing /bin/pager:

(c)rafaeldtinoco@devel:~$ which pager
(c)rafaeldtinoco@devel:~$ ls -lah /bin/pager
lrwxrwxrwx 1 root root 23 Apr 24 21:39 /bin/pager -> /etc/alternatives/pager
(c)rafaeldtinoco@devel:~$ ls -lah /etc/alternatives/pager
lrwxrwxrwx 1 root root 13 Apr 24 21:39 /etc/alternatives/pager -> /usr/bin/less

Try checking your system for pager:

(c)rafaeldtinoco@devel:~$ sudo update-alternatives --query pager
Name: pager
Link: /usr/bin/pager
Slaves:
 pager.1.gz /usr/share/man/man1/pager.1.gz
Status: auto
Best: /usr/bin/less
Value: /usr/bin/less

Alternative: /bin/more
Priority: 50
Slaves:
 pager.1.gz /usr/share/man/man1/more.1.gz

Alternative: /usr/bin/less
Priority: 77
Slaves:
 pager.1.gz /usr/share/man/man1/less.1.gz

and fixing it!

** Changed in: smartmontools (Ubuntu)
   Status: New => Invalid

** Changed in: smartmontools (Ubuntu)
   Status: Invalid => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to smartmontools in Ubuntu.
https://bugs.launchpad.net/bugs/1874953

Title:
  package smartmontools 7.1-1build1 failed to install/upgrade: conffile
  difference visualizer subprocess returned error exit status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1874953/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874953] Re: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127

2020-04-27 Thread Rafael David Tinoco
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 of this.


** Also affects: dpkg (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: dpkg (Ubuntu)
   Status: New => Triaged

** Changed in: dpkg (Ubuntu)
   Importance: Undecided => High

-- 
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 failed to install/upgrade: conffile
  difference visualizer subprocess returned error exit status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1874953/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874953] Re: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127

2020-04-27 Thread Rafael David Tinoco
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 failed to install/upgrade: conffile
  difference visualizer subprocess returned error exit status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1874953/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875010] Re: package smartmontools 7.1-1build1 failed to install/upgrade: »Conffile-Unterschied-Darsteller«-Unterprozess gab den Fehlerwert 127 zurück

2020-04-27 Thread Rafael David Tinoco
*** 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 
difference visualizer subprocess returned error exit status 127

-- 
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/1875010

Title:
  package smartmontools 7.1-1build1 failed to install/upgrade:
  »Conffile-Unterschied-Darsteller«-Unterprozess gab den Fehlerwert 127
  zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1875010/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874831] Re: libnginx-mod-nchan distributes old/incompatible module

2020-04-27 Thread Rafael David Tinoco
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: salsa.debian.org/nginx-team/nginx/-/issues #2
   https://salsa.debian.org/nginx-team/nginx/-/issues/2

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1874831/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874730] Re: package apache2 2.4.41-4ubuntu3 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1

2020-04-27 Thread Rafael David Tinoco
** 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: Undecided => Low

** Changed in: apache2 (Ubuntu Groovy)
   Importance: Undecided => Low

-- 
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/1874730

Title:
  package apache2 2.4.41-4ubuntu3 failed to install/upgrade: installed
  apache2 package post-installation script subprocess returned error
  exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1874730/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874932] Re: Getting old buffer + header + correct response

2020-04-27 Thread Rafael David Tinoco
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 ?
3) Could you provide a specific step-by-step reproducer for your issue ?

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: apache2 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1874932

Title:
  Getting old buffer + header + correct response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1874932/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874831] Re: libnginx-mod-nchan distributes old/incompatible module

2020-04-27 Thread Rafael David Tinoco
** 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 => Medium

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1874831/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875012] Re: KVM internal error. Suberror: 1 -- emulation failure

2020-04-27 Thread Rafael David Tinoco
** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1875012/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875517] Re: check_http inefficient and sometimes times out

2020-04-30 Thread Rafael David Tinoco
@Haw,

I need some clarification here. You have applied a temporary mitigation
that improves check_http by not constantly freeing and allocating heap
memory. You have indicated upstream patches (2 of them) dealing with the
constant timeout for the checker.

monitoring-plugins 2.2 version check_http SEEMs to be close to nagios-
plugins 1.5 version.

The nagios-plugins you pointed out are backportable to release-2.2.0 of
NAGIOS-PLUGINS package and not monitoring-plugins. Have you tested those
? Do you need nagios-plugins backport (of those 2 patches) to test and
see if it mitigates your issue ?

Per SRU guidelines I can't simply backport those 2 without a testcase
and the guarantee they're addressing your issue with a successful
testcase being fixed.

Waiting a feedback here.

Thanks for reporting this.

** Also affects: nagios-plugins (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: monitoring-plugins (Ubuntu Bionic)

** No longer affects: monitoring-plugins (Ubuntu Eoan)

** No longer affects: monitoring-plugins (Ubuntu Focal)

** No longer affects: monitoring-plugins (Ubuntu Groovy)

** No longer affects: nagios-plugins (Ubuntu Groovy)

** No longer affects: nagios-plugins (Ubuntu Focal)

** No longer affects: nagios-plugins (Ubuntu Eoan)

** No longer affects: nagios-plugins (Ubuntu Bionic)

** No longer affects: nagios-plugins (Ubuntu)

** Also affects: nagios-plugins (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nagios-plugins (Ubuntu)
   Status: New => Triaged

** Changed in: nagios-plugins (Ubuntu)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

-- 
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/1875517

Title:
  check_http inefficient and sometimes times out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1875517/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875517] Re: check_http inefficient and sometimes times out

2020-05-01 Thread Rafael David Tinoco
Nice! Knowing that the patch is a a small subset of an upstream patch
makes our life easier! Since you provided the test, we can go ahead and
do the SRU with the testcase you provided. I'll sponsor the backport for
you.


** Changed in: nagios-plugins (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** No longer affects: nagios-plugins (Ubuntu)

** Changed in: monitoring-plugins (Ubuntu)
   Status: Triaged => In Progress

-- 
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/1875517

Title:
  check_http inefficient and sometimes times out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1875517/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875517] Re: check_http inefficient and sometimes times out

2020-05-04 Thread Rafael David Tinoco
** Description changed:

+ [Impact]
+ 
+  * check_http nagios plugin module faces timeouts multiple times when
+ checking for http health.
+ 
+ [Test Case]
+ 
+  * not specific clear one. to measure http health in a big environment.
+  * being tested by real user case.
+ 
+ [Regression Potential]
+ 
+  * check_http module might face a regression (only code touched).
+  * we are using realloc instead of a new free/malloc for the http buffer
+  * change is based in an upstream commit and proposed by end-user
+ 
+ [Other Info]
+ 
+  * Original Description:
+ 
  Hi,
  
  We're frequently seeing socket timeouts with some checks using the
  check_http plugin. It seems this is a known issue with some fixes
  upstream:
  
  | 
https://github.com/nagios-plugins/nagios-plugins/commit/2b38350d546ef9632ccd90e300eeaf6eda0ca32c
  | 
https://github.com/nagios-plugins/nagios-plugins/commit/fc1bf94655aaed32eeb6fb5c33b6d093f5564bad
  
  Think we can backport these fixes?

-- 
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/1875517

Title:
  check_http inefficient and sometimes times out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1875517/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875036] Re: bridge stops working on focal update

2020-04-27 Thread Rafael David Tinoco
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 + bridge-utils + net-tools but
do have in mind that those tools are being deprecated in favor of:
systemd-networkd, netplan.io, iproute2, etc.

Good examples on how to obtain the same result using netplan.io can be
found at:

https://netplan.io/examples

For now I'm marking this as a Invalid bug. If think there is anything
else on this topic I would suggest writing to Ubuntu Users mailing list,
a correct place for community-based technical support.

Best regards,

Rafael D. Tinoco



** Changed in: bridge-utils (Ubuntu)
   Status: New => Invalid

-- 
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/1875036

Title:
  bridge stops working on focal update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1875036/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875109] Re: regression: splitting panes does not cause a resize in backgrounded tmux

2020-04-27 Thread Rafael David Tinoco
** 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

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to tmux in Ubuntu.
https://bugs.launchpad.net/bugs/1875109

Title:
  regression: splitting panes does not cause a resize in backgrounded
  tmux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1875109/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1590799] Re: nfs-kernel-server does not start because of dependency failure

2020-04-29 Thread Rafael David Tinoco
** Changed in: nfs-utils (Ubuntu Zesty)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: nfs-utils (Ubuntu Yakkety)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: nfs-utils (Ubuntu Xenial)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: nfs-utils (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Also affects: nfs-utils (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Tags removed: sts-sru-needed verification-done-xenial verification-needed 
xenial
** Tags added: server-next

** Changed in: nfs-utils (Ubuntu Bionic)
   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/1590799

Title:
  nfs-kernel-server does not start because of dependency failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1874831] Re: libnginx-mod-nchan distributes old/incompatible module

2020-04-29 Thread Rafael David Tinoco
Thanks a lot for checking this @teward! Your call, I'd say only if you
think its worth the time (versus benefit). Up to you! This will be in
server's team queue until its incomplete/closed. Cheers!

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1874831/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1869074] Re: Please add appinfo plugin

2020-04-29 Thread Rafael David Tinoco
** Changed in: open-vm-tools (Ubuntu)
   Status: Confirmed => 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/1869074

Title:
  Please add appinfo plugin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1869074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875596] Re: Django Timefield(default=) gives unhelpful diagnostics

2020-04-29 Thread Rafael David Tinoco
Local Configuration Issue

Thank you for taking the time to file a bug report.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Invalid'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: python-django (Ubuntu)
   Status: New => Invalid

-- 
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/1875596

Title:
  Django Timefield(default=) gives unhelpful diagnostics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/1875596/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875594] Re: multipathd failed to get udev uid, add missing path

2020-04-29 Thread Rafael David Tinoco
@paelzer,

I really think the right place for a fix like this would be to have a
rule at:

/lib/udev/rules.d/99-vmware-scsi-udev.rules

from open-vm-tools package.

>From a previous fix I did to sg3-tools, I remember ignoring disks
without VPDs and providing them a SCSI_ID based on something else. We
could do the same here. Do you agree ? I can provide the patch.

** Also affects: open-vm-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: open-vm-tools (Ubuntu)
   Status: New => Triaged

** Changed in: multipath-tools (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/1875594

Title:
  multipathd  failed to get udev uid, add missing path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1875594/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1869074] Re: Please add appinfo plugin

2020-04-29 Thread Rafael David Tinoco
** Tags added: server-next

-- 
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/1869074

Title:
  Please add appinfo plugin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1869074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1663985] Re: Broken build with GCC 7

2020-04-29 Thread Rafael David Tinoco
Need more information

Thank you for taking the time to file a bug report.

Unfortunately it seems that you are trying to compile a source code that is not
present in our repositories, right ? I see you have marked the upstream project
AND the Ubuntu project, althought you haven't provided any information on what
you are exactly doing and how you are trying to build the source code, and which
version of the source code you're trying to build.

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: libmemcached (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to libmemcached in Ubuntu.
https://bugs.launchpad.net/bugs/1663985

Title:
  Broken build with GCC 7

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmemcached/+bug/1663985/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1393403] Re: dovecot unable to create files in /var/mail

2020-04-29 Thread Rafael David Tinoco
** Tags added: server-next

-- 
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/1393403

Title:
  dovecot unable to create files in /var/mail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1393403/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1590799] Re: nfs-kernel-server does not start because of dependency failure

2020-04-29 Thread Rafael David Tinoco
@gagarin, @rostislav,

If you can reproduce this at will, could you provide more information
about it ?

Executing something like this:

$ for _service in $(systemctl list-dependencies nfs-kernel-server
--plain | tail -n +2 | awk '{print $1}'); do systemctl cat --full --no-
pager $_service > $_service.cat | journalctl _SYSTEMD_UNIT=$_service >
$_service.log | awk '{print $1}'; done ; journalctl --no-pager > big.log

and providing me "*.cat *.log" in a .tar.gz file out be very helpful.

rafaeldtinoco -at- ubuntu.com <- if you don't want to expose your logs
file in this bug.

Thanks a lot!

** Changed in: nfs-utils (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: nfs-utils (Ubuntu Bionic)
   Status: Triaged => Confirmed

** Changed in: nfs-utils (Ubuntu)
   Importance: Medium => Undecided

** Changed in: nfs-utils (Ubuntu Yakkety)
   Importance: Medium => Undecided

** Changed in: nfs-utils (Ubuntu Zesty)
   Importance: Medium => Undecided

** Changed in: nfs-utils (Ubuntu Xenial)
   Importance: Medium => Undecided

-- 
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/1590799

Title:
  nfs-kernel-server does not start because of dependency failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875517] Re: check_http inefficient and sometimes times out

2020-04-29 Thread Rafael David Tinoco
$ git log -1 -p 2b38350d546ef9632ccd90e300eeaf6eda0ca32c | diffstat
 check_http.c |  127 
+
 1 file changed, 77 insertions(+), 50 deletions(-)

$ git describe --tags 2b38350d546ef9632ccd90e300eeaf6eda0ca32c
release-2.2.1-82-g2b38350d



$ git log -1 -p fc1bf94655aaed32eeb6fb5c33b6d093f5564bad | diffstat
 check_http.c |6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

$ git describe --tags fc1bf94655aaed32eeb6fb5c33b6d093f5564bad
release-2.2.1-135-gfc1bf946



$ rmadison monitoring-plugins
 monitoring-plugins | 2.1.2-2ubuntu2 | xenial  | source, all
 monitoring-plugins | 2.2-3ubuntu2   | bionic/universe | source, all
 monitoring-plugins | 2.2-5  | disco/universe  | source, all
 monitoring-plugins | 2.2-6build2| eoan/universe   | source, all
 monitoring-plugins | 2.2-6ubuntu1   | focal/universe  | source, all
 monitoring-plugins | 2.2-6ubuntu1   | groovy/universe | source, all

** Tags added: server-next

** Changed in: monitoring-plugins (Ubuntu Bionic)
   Status: Confirmed => Triaged

** Changed in: monitoring-plugins (Ubuntu Eoan)
   Status: New => Triaged

** Changed in: monitoring-plugins (Ubuntu Groovy)
   Status: Confirmed => Triaged

** Changed in: monitoring-plugins (Ubuntu Focal)
   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/1875517

Title:
  check_http inefficient and sometimes times out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1875517/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875708] Re: Truncated messages during shutdown

2020-04-29 Thread Rafael David Tinoco
** Changed in: libvirt (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/1875708

Title:
  Truncated messages during shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1875708/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1875697] Re: drop fix-ldap-distribution.patch?

2020-04-29 Thread Rafael David Tinoco
(c)rafaeldtinoco@devel:~$ rmadison openldap
 openldap | 2.4.28-1.1ubuntu4  | precise  | source
 openldap | 2.4.28-1.1ubuntu4.6| precise-security | source
 openldap | 2.4.28-1.1ubuntu4.6| precise-updates  | source
 openldap | 2.4.31-1+nmu2ubuntu8   | trusty   | source
 openldap | 2.4.31-1+nmu2ubuntu8.4 | trusty-security  | source
 openldap | 2.4.31-1+nmu2ubuntu8.5 | trusty-updates   | source
 openldap | 2.4.42+dfsg-2ubuntu3   | xenial   | source
 openldap | 2.4.42+dfsg-2ubuntu3.6 | xenial-security  | source
 openldap | 2.4.42+dfsg-2ubuntu3.7 | xenial-updates   | source
 openldap | 2.4.45+dfsg-1ubuntu1   | bionic   | source
 openldap | 2.4.45+dfsg-1ubuntu1.3 | bionic-security  | source
 openldap | 2.4.45+dfsg-1ubuntu1.4 | bionic-updates   | source
 openldap | 2.4.47+dfsg-3ubuntu2   | disco| source
 openldap | 2.4.47+dfsg-3ubuntu2.1 | disco-security   | source
 openldap | 2.4.47+dfsg-3ubuntu2.2 | disco-updates| source
 openldap | 2.4.48+dfsg-1ubuntu1   | eoan | source
 openldap | 2.4.49+dfsg-2ubuntu1   | focal| source
 openldap | 2.4.49+dfsg-2ubuntu1   | groovy   | source

Since we haven't synced with dfsg-3 for focal, I'm marking this as
server-next for groovy. For next merge, I would suggest this to be SRUed
for Focal as well, and leave for the SRU team to decide. Since its a
very small change, I'm flagging as blocking next SRU to focal, perhaps
one can add it to the next SRU.

** Tags added: server-next

** Tags added: block-proposed-focal

** Also affects: openldap (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: openldap (Ubuntu)
   Status: New => Triaged

** Changed in: openldap (Ubuntu Focal)
   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/1875697

Title:
  drop fix-ldap-distribution.patch?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1875697/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1873447] Re: [bionic][autopkgtest] ipset failing autopkgtest after kmod sru

2020-04-22 Thread Rafael David Tinoco
$ 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   | focal|

-- 
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:
  [bionic][autopkgtest] ipset failing autopkgtest after kmod sru

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipset/+bug/1873447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1873447] Re: [bionic][autopkgtest] ipset failing autopkgtest after kmod sru

2020-04-22 Thread Rafael David Tinoco
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 the following commit:

v4.19-4705-g886503f34d63 : netfilter: ipset: actually allow allowable
CIDR 0 in hash:net,port,net

and the test started failing.

- forcing bad test is the best to be done and this will unblock the kmod
fix:

https://launchpad.net/ubuntu/+source/kmod/24-1ubuntu3.3

-- 
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:
  [bionic][autopkgtest] ipset failing autopkgtest after kmod sru

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipset/+bug/1873447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1873447] Re: [bionic][autopkgtest] ipset failing autopkgtest after kmod sru

2020-04-23 Thread Rafael David Tinoco
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 (Ubuntu Bionic)
   Importance: Medium => Undecided

-- 
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:
  [bionic][autopkgtest] ipset failing autopkgtest after kmod sru

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipset/+bug/1873447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1873447] Re: [bionic][autopkgtest] ipset failing autopkgtest after kmod sru

2020-04-22 Thread Rafael David Tinoco
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 regression:  - - - - - - - - - - results - - - - - 
- - - - -
regression   FAIL non-zero exit status 1

and to fix it:

hash:net6,port,net6: Range: Create a set: passed
hash:net6,port,net6: Range: Add zero valued element: passed
hash:net6,port,net6: Range: Test zero valued element: passed
hash:net6,port,net6: Range: Delete zero valued element: passed

by cherry-picking the upstream fix:

commit 2a66a0df03788d8a7e95972847545de0ade0dd8e
Author: Jozsef Kadlecsik 
Date:   Fri Oct 19 19:41:26 2018 +0200

Correct to test null valued entry in hash:net6,port,net6 test

-- 
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:
  [bionic][autopkgtest] ipset failing autopkgtest after kmod sru

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipset/+bug/1873447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1873447] Re: [bionic][autopkgtest] ipset failing autopkgtest after kmod sru

2020-04-22 Thread Rafael David Tinoco
$ 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:
  [bionic][autopkgtest] ipset failing autopkgtest after kmod sru

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipset/+bug/1873447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1869643] Re: {fence, resource}-agents: PATH for all binaries called by all agents should be resolvable

2020-04-14 Thread Rafael David Tinoco
** Summary changed:

- check PATH for all binaries called by all agents
+ {fence,resource}-agents: PATH for all binaries called by all agents should be 
resolvable

-- 
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/1869643

Title:
  {fence,resource}-agents: PATH for all binaries called by all agents
  should be resolvable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1869643/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1850708] Re: focal - net-tools is is deprecated (remove from recommends)

2020-04-14 Thread Rafael David Tinoco
*** This bug is a duplicate of bug 1863677 ***
https://bugs.launchpad.net/bugs/1863677

** This bug has been marked a duplicate of bug 1863677
   {fence-resource}-agents: split supported/unsupported fence agents AND adjust 
depends/recommends

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to resource-agents in Ubuntu.
https://bugs.launchpad.net/bugs/1850708

Title:
  focal - net-tools is is deprecated (remove from recommends)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1850708/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1863677] Re: {fence-resource}-agents: split supported/unsupported fence agents AND adjust depends/recommends

2020-04-14 Thread Rafael David Tinoco
** Summary changed:

- fence_scsi needs lvm2 package so it should depend on it
+ {fence-resource}-agents: split supported/unsupported fence agents AND adjust 
depends/recommends

** Also affects: resource-agents (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: resource-agents (Ubuntu)
   Status: New => Confirmed

** Changed in: resource-agents (Ubuntu)
   Importance: Undecided => Medium

** Changed in: resource-agents (Ubuntu)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

-- 
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/1863677

Title:
  {fence-resource}-agents: split supported/unsupported fence agents AND
  adjust depends/recommends

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1863677/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1866412] Re: resource-agents should depend on psmisc (and probably others) for the resources to work

2020-04-14 Thread Rafael David Tinoco
*** This bug is a duplicate of bug 1863677 ***
https://bugs.launchpad.net/bugs/1863677

** This bug has been marked a duplicate of bug 1863677
   {fence-resource}-agents: split supported/unsupported fence agents AND adjust 
depends/recommends

-- 
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/1866412

Title:
  resource-agents should depend on psmisc (and probably others) for the
  resources to work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1866412/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1092330] Re: Ldirectord MySQL Service Check Fails

2020-04-14 Thread Rafael David Tinoco
*** This bug is a duplicate of bug 1863677 ***
https://bugs.launchpad.net/bugs/1863677

** This bug is no longer a duplicate of bug 1866412
   resource-agents should depend on psmisc (and probably others) for the 
resources to work
** This bug has been marked a duplicate of bug 1863677
   {fence-resource}-agents: split supported/unsupported fence agents AND adjust 
depends/recommends

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to resource-agents in Ubuntu.
https://bugs.launchpad.net/bugs/1092330

Title:
  Ldirectord MySQL Service Check Fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1092330/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1872589] Re: systemd-networkd is not honoring UseRoutes=false

2020-04-14 Thread Rafael David Tinoco
*** This bug is a duplicate of bug 1867375 ***
https://bugs.launchpad.net/bugs/1867375

Ahhh good to know, documentation in netplan.io doesn't reflect that
also, that is why I opened the bug. Funny because because of the
attribute name "UseRoutes" I was in doubt if it would get the default
gateway or just the published routes.. then the documentation said it
would get the default GW.

Thanks for letting me know Dan!

-> https://netplan.io/reference

Documenting it if anyone is confused by this as well:

"""
use-routes (bool)
Default: true. When true, the routes received from the DHCP server will be 
installed in the routing table normally. When set to false, routes from the 
DHCP server will be ignored: in this case, the user is responsible for adding 
static routes if necessary for correct network operation. This allows users to 
avoid installing a default gateway for interfaces configured via DHCP. 
Available for both the networkd and NetworkManager backends.
"""

-- 
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/1872589

Title:
  systemd-networkd is not honoring UseRoutes=false

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1872589/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1872589] Re: systemd-networkd is not honoring UseRoutes=false

2020-04-14 Thread Rafael David Tinoco
*** This bug is a duplicate of bug 1867375 ***
https://bugs.launchpad.net/bugs/1867375

I'm marking this as a duplicate of your bug then...

** This bug has been marked a duplicate of bug 1867375
   systemd-networkd: Setting UseRoutes to False results in DHCP default gateway 
not being installed

-- 
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/1872589

Title:
  systemd-networkd is not honoring UseRoutes=false

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1872589/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1871129] Re: htop is blank when using in focal in wsl1

2020-04-14 Thread Rafael David Tinoco
** Changed in: ubuntuwsl
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

-- 
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/1871129

Title:
  htop is blank when using in focal in wsl1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuwsl/+bug/1871129/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1872476] Re: Shared files are shown as folders

2020-04-14 Thread Rafael David Tinoco
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 not
5) The other side OS version and configuration


and/or any other information, that might help us reproducing the issue, would 
be great!

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: samba (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1872476

Title:
  Shared files are shown as folders

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1872476/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1872541] Re: MySQL client fails to connect, seems to force SSL

2020-04-14 Thread Rafael David Tinoco
** 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1872541/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1877617] Re: open-iscsi automatic scans disable AND groovy merge with upstream

2020-05-11 Thread Rafael David Tinoco
Sure Ben,

I have also suggested Debian maintainers:

https://salsa.debian.org/linux-blocks-team/open-iscsi/-/merge_requests/1
https://salsa.debian.org/linux-blocks-team/open-iscsi/-/merge_requests/2
https://salsa.debian.org/linux-blocks-team/open-iscsi/-/merge_requests/3

to sync with upstream. Will give them a while to provide answers so I
can merge/sync with Debian. If, by any chance, they don't sync with
upstream, I'll move Ubuntu forward to 2.1.1 and let them to catch up
eventually.

Cheers

-- 
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/1877617

Title:
  open-iscsi automatic scans disable AND groovy merge with upstream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1877617] Re: open-iscsi automatic scans disable AND groovy merge with upstream

2020-05-12 Thread Rafael David Tinoco
Well, yep, Ubuntu tries not to add deltas to Debian unless they're
*really* needed. This makes Debian and Ubuntu healthy. Upstream has
merged my request to experimental, I'll sync it back to Ubuntu as soon
as our importers have recognized the new version.

Cheers!

-- 
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/1877617

Title:
  open-iscsi automatic scans disable AND groovy merge with upstream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images

2020-05-06 Thread Rafael David Tinoco
FYIO, from now on all the "merge" work will be done in the merge
requests being linked to this BUG (at the top). @paelzer will be
verifying those.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1805256

Title:
  qemu-img hangs on rcu_call_ready_event logic in Aarch64 when
  converting images

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1805256/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images

2020-05-05 Thread Rafael David Tinoco
Hello Ike,

Please, let me know if you want me to go after the needed SRUs for this
fix or if you will.

I'll wait for the final feedback from tests with your PPA.

Cheers!

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1805256

Title:
  qemu-img hangs on rcu_call_ready_event logic in Aarch64 when
  converting images

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1805256/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1877617] Re: Automatic scans cause instability for cloud use cases

2020-05-10 Thread Rafael David Tinoco
Hello Ben,

Yes, those commits were added at:

rafaeldtinoco@workstation:~/.../sources/upstream/open-iscsi$ git describe 
--tags 5e32aea95741a07d53153c658a0572588eae494d
2.0.874-7-g5e32aea

rafaeldtinoco@workstation:~/.../sources/upstream/open-iscsi$ git describe 
--tags d5483b0df96bd2a1cf86039cf4c6822ec7d7f609
2.0.874-23-gd5483b0

Looks like we've been very cautious with open-iscsi package:

 open-iscsi | 2.0.871-0ubuntu9  | precise   | 
 open-iscsi | 2.0.871-0ubuntu9.12.04.2  | precise-updates   | 
 open-iscsi | 2.0.873-3ubuntu5~ubuntu12.04.1| precise-backports | 
 open-iscsi | 2.0.873-3ubuntu9  | trusty| 
 open-iscsi | 2.0.873+git0.3b4b4500-14ubuntu3   | xenial| 
 open-iscsi | 2.0.873+git0.3b4b4500-14ubuntu3.7 | xenial-updates| 
 open-iscsi | 2.0.874-5ubuntu2  | bionic| 
 open-iscsi | 2.0.874-5ubuntu2.7| bionic-updates| 
 open-iscsi | 2.0.874-5ubuntu2.9| bionic-proposed   | 
 open-iscsi | 2.0.874-5ubuntu15 | disco | 
 open-iscsi | 2.0.874-7.1ubuntu3| eoan  | 
 open-iscsi | 2.0.874-7.1ubuntu6| focal | 
 open-iscsi | 2.0.874-7.1ubuntu6| groovy|

I'm marking this for a merge for groovy and blocking -proposed for
groovy. Since this is behavior change I'll have to discuss this as being
a SRU with a broader audience (specially our openstack team).. but
marking as affecting all previous supported releases as well.

** Also affects: open-iscsi (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: open-iscsi (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: open-iscsi (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: open-iscsi (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: open-iscsi (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: open-iscsi (Ubuntu Eoan)
   Status: New => Confirmed

** Changed in: open-iscsi (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: open-iscsi (Ubuntu Groovy)
   Status: New => Confirmed

** Changed in: open-iscsi (Ubuntu Groovy)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

** Tags added: block-proposed-focal block-proposed-groovy

-- 
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/1877617

Title:
  Automatic scans cause instability for cloud use cases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1877617] Re: Automatic scans cause instability for cloud use cases

2020-05-10 Thread Rafael David Tinoco
BTW, it is very likely that I'll sponsor your changes and upload to
queue - letting the SRU team to decide - and merge open-iscsi to latest
upstream.

Thanks for the bug report!

-- 
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/1877617

Title:
  Automatic scans cause instability for cloud use cases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1877617] Re: Automatic scans cause instability for cloud use cases

2020-05-10 Thread Rafael David Tinoco
Alright, this *new feature* (which is actually fixing an unwanted
behavior) has the following section added to iscsid.conf:

# To prevent doing automatic scans that would add unwanted luns to the system
# we can disable them and have sessions only do manually requested scans.
# Automatic scans are performed on startup, on login, and on AEN/AER reception
# on devices supporting it.  For HW drivers all sessions will use the value
# defined in the configuration file.  This configuration option is independent
# of scsi_mod scan parameter. (The default behavior is auto):
node.session.scan = auto

And this makes it to have the exact same behavior as before this fix, so
this makes it suitable for SRU. I'm doing the merge requests and will
link to this bug. I'm doing the same change for groovy BUT it will be a
new merge with upstream.

-- 
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/1877617

Title:
  Automatic scans cause instability for cloud use cases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1877617] Re: Automatic scans cause instability for cloud use cases

2020-05-10 Thread Rafael David Tinoco
Alright,

waiting on ubuntu server team review for the SRUs: 
 - will upload as soon as I get +1.

for Groovy, will work with Debian to merge with upstream:
 - @Ritesh Raj Sarraf

rafaeldtinoco@workstation:~/.../sources/upstream/open-iscsi$ git tag
2.0.873
2.0.874
2.0.875
2.0.876
2.0.877
2.0.878
2.1.0
2.1.1

Will check if we can get it to 2.1.1:

https://github.com/open-iscsi/open-iscsi/blob/master/Changelog

** Changed in: open-iscsi (Ubuntu Groovy)
   Status: Confirmed => Triaged

** Changed in: open-iscsi (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: open-iscsi (Ubuntu Eoan)
   Status: Confirmed => In Progress

** Changed in: open-iscsi (Ubuntu Bionic)
   Status: Confirmed => In Progress

** Summary changed:

- Automatic scans cause instability for cloud use cases
+ open-iscsi automatic scans disable AND groovy merge with upstream

-- 
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/1877617

Title:
  open-iscsi automatic scans disable AND groovy merge with upstream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1877617] Re: open-iscsi automatic scans disable AND groovy merge with upstream

2020-05-10 Thread Rafael David Tinoco
I have also created the PPA:

https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1877617

just as proforma for the merge reviews.

Will get back to this (groovy) very soon.

-- 
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/1877617

Title:
  open-iscsi automatic scans disable AND groovy merge with upstream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1877617] Re: open-iscsi automatic scans disable AND groovy merge with upstream

2020-05-14 Thread Rafael David Tinoco
Yes, I'm working with upstream:

https://salsa.debian.org/linux-blocks-team/open-
iscsi/-/merge_requests/4/commits

I have basically reviewed all previous open-iscsi packages.

Let's see further discussions on how they see that.

For the SRUs (3 of them, in the merge requests). They were accepted by a
peer of mine, so I basically to test if behavior is kept as default for
all 3 of them and then I'll upload the fixes. I'll basically run your
test case on all 3 packages and upload the binaries after I'm done. Will
finish this soon, gave a better attention to upstream so we could bump
the version there.

-- 
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/1877617

Title:
  open-iscsi automatic scans disable AND groovy merge with upstream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1877617] Re: open-iscsi automatic scans disable AND groovy merge with upstream

2020-05-19 Thread Rafael David Tinoco
Okay so the 3 SRUs are uploaded waiting to be approved.

I have also proposed a merge request in salsa:

https://salsa.debian.org/linux-blocks-team/open-iscsi/-/merge_requests/4

refactoring a bit the package itself and solving the openssl linking
issue the upstream maintainer has observed. Haven't yet decided if
Ubuntu will keep the CHAP auth algs support from openssl or not (pending
ubuntu-devel@ mailing list discussion thread).

For now thats it, waiting on upstream and SRU.

-- 
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/1877617

Title:
  open-iscsi automatic scans disable AND groovy merge with upstream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1764044] Re: ssh-add asks about passphrases for keys already unlocked in the keychain

2020-05-19 Thread Rafael David Tinoco
Rolf,

Thank you for taking the time to file a bug report.

I have just used the following in my .bashrc (like keychain man page
says so):

"""
keychain id_rsa id_dsa id_ecdsa

[ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
[ -f $HOME/.keychain/$HOSTNAME-sh ] && . $HOME/.keychain/$HOSTNAME-sh
[ -f $HOME/.keychain/$HOSTNAME-sh-gpg ] && . $HOME/.keychain/$HOSTNAME-sh-gpg
"""

and I have all my keys already set:

"""
 * keychain 2.8.5 ~ http://www.funtoo.org
 * Found existing ssh-agent: 3684816
 * Known ssh key: /home/rafaeldtinoco/.ssh/id_rsa
 * Known ssh key: /home/rafaeldtinoco/.ssh/id_dsa
 * Known ssh key: /home/rafaeldtinoco/.ssh/id_ecdsa

rafaeldtinoco@workstation:~$ 
"""

for every new shell. Just needed to put my password once.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community


** Changed in: openssh (Ubuntu)
   Status: New => Incomplete

-- 
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/1764044

Title:
  ssh-add asks about passphrases for keys already unlocked in the
  keychain

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764044/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1877504] Re: new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-set, mythbackend and mythfrontend to segfault on exit.

2020-05-19 Thread Rafael David Tinoco
From:

bool init_compiled_charsets(myf flags MY_ATTRIBUTE((unused)))

there are charsets being added to "all_charsets" (global variable)
through:

void add_compiled_collation(CHARSET_INFO *cs) {
  DBUG_ASSERT(cs->number < array_elements(all_charsets));
  all_charsets[cs->number] = cs;
  map_coll_name_to_number(cs->name, cs->number);
  map_cs_name_to_number(cs->csname, cs->number, cs->state);
  cs->state |= MY_CS_AVAILABLE;
}

and that contain NO COLLATION, this way.. when uniting them:

void charset_uninit() {
  for (CHARSET_INFO *cs : all_charsets) {
if (cs && cs->coll->uninit) {
  cs->coll->uninit(cs);
}
  }

cs->coll is NULL. This is an upstream bug.. would you like to report ?
You can report upstream and link it here so we can backport a fix
whenever someone fixes it. Maybe @lars can tackle it.

-- 
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/1877504

Title:
  new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-
  set, mythbackend and mythfrontend to segfault on exit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1878945] Re: crash slapd after update

2020-05-19 Thread Rafael David Tinoco
It says that your ldap database cannot be opened... There is a debconf
option that says:

"Do you want the database to be removed when slapd is purged?"

I wonder if you had that enabled before the upgrade.

During slapd upgrade, it asks to create a backup of /var/lib/slapd:

(c)rafaeldtinoco@focal:/var/lib/ldap$ sudo dpkg-reconfigure -p low slapd 
  Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.49+dfsg-2ubuntu1.2... 
done.
  Moving old database directory to /var/backups:
  - directory unknown... done.
  Creating initial configuration... done.
  Creating LDAP directory... done.

Do you have anything under /var/backups/* named '*slapd*' ?

** Changed in: openldap (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1878945

Title:
  crash slapd after update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1878945/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user

2020-05-14 Thread Rafael David Tinoco
There is a very similar (to yours) problem described here:

https://dovecot.org/pipermail/dovecot/2014-May/095998.html

one of the developers tell end-user to move away from mbox,
and there seems to exist a correct answer stating that mbox
is a supported format and there is no current documentation
saying that mbox format is broken.

Unfortunately that thread did not have a better ending.

Several discussions, dated from before 2014, stating that 
from time to time the cache gets corrupted. There might be
more than 1 reason on why the cache gets corrupted - doing a
parallel to any other kind of journaling scheme - so...

without having an exact reproducer it would be very difficult
to check why the cache gets corrupted :\.

Moving this to confirmed as it seems to still exist.


** Changed in: dovecot (Ubuntu)
   Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/1876537

Title:
  dovecot eating mail indexes /var/dovecot-index/user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1876537/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade

2020-05-14 Thread Rafael David Tinoco
Moving back to incomplete as stated by @paelzer.

** Changed in: libseccomp (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1876486

Title:
  Kernel panic booting after 18.04 to 20.04 upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1878134] Re: Assertion failures in ati_reg_read_offs/ati_reg_write_offs

2020-05-14 Thread Rafael David Tinoco
Hello Alexander,

I believe your fuzz test result was meant to the upstream project so I
moved it.

o/

** Also affects: qemu
   Importance: Undecided
   Status: New

** No longer affects: qemu-kvm (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1878134

Title:
  Assertion failures in ati_reg_read_offs/ati_reg_write_offs

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1878134/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 907816] Re: libapache2-mod-php5 forgets timezone definition after some time

2020-05-14 Thread Rafael David Tinoco
@nagendra-d, it does not look like this is a software bug, but a
configuration issue that @skliarie has faced. Feel free to
talk to him through this bug (for documenting purposes) but 
I'm keeping the status here as Invalid so we can better track
things we actually have an action for.

Thank you for taking the time to file a bug report.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: apache2 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/907816

Title:
  libapache2-mod-php5 forgets timezone definition after some time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/907816/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

2020-05-14 Thread Rafael David Tinoco
TL;DR TODO SUMMARY:

- netplan change to support KeepConfiguration= for systemd-networkd backend 
(Groovy)
- backport this change: netplan for Ubuntu Focal  (SRU)
- backport this change: netplan for Ubuntu Eoan   (SRU, WontFix due to EOL ?)
- backport this change: netplan for Ubuntu Bionic (SRU)
- backport this change: netplan for Ubuntu Xenial (SRU, WontFix ?)

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1815101

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1815101/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

2020-05-14 Thread Rafael David Tinoco
@napsty: the "workaround" (from your blog) is actually to use:

- ifupdown/bridge-utils/vlan/resolvconf for network setup   OR
- use systemd-networkd DIRECTLY with the KeepConfiguration= option in .network 
file

Just highlighting it here.

@ddstreet, you said you would try to come up with the netplan change for
KeepConfiguration. Did you have time to check on this ? (just checking).

Cheers o/

** Changed in: keepalived (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: keepalived (Ubuntu Xenial)
     Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: keepalived (Ubuntu Bionic)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: keepalived (Ubuntu Disco)
     Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: keepalived (Ubuntu Eoan)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: systemd (Ubuntu)
     Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: systemd (Ubuntu Xenial)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: systemd (Ubuntu Bionic)
     Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: systemd (Ubuntu Disco)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: systemd (Ubuntu Eoan)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: netplan
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** No longer affects: keepalived (Ubuntu Eoan)

** No longer affects: keepalived (Ubuntu Disco)

** Also affects: heartbeat (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: keepalived (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: keepalived (Ubuntu Focal)
   Status: New => Confirmed

** No longer affects: heartbeat (Ubuntu Focal)

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1815101

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1815101/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1877617] Re: open-iscsi automatic scans disable AND groovy merge with upstream

2020-05-13 Thread Rafael David Tinoco
Not the entire version bump, no, per SRU guidelines
(https://wiki.ubuntu.com/StableReleaseUpdates). The auto_scan change,
yes.. I'm backporting it to bionic. Anything besides that would have to
be a backport, maintained *by someone* in -backports
(https://help.ubuntu.com/community/UbuntuBackports).

-- 
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/1877617

Title:
  open-iscsi automatic scans disable AND groovy merge with upstream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1877617/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1876852] Re: package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

2020-05-08 Thread Rafael David Tinoco
Need more information

Thank you for taking the time to file a bug report.

"""
mysql server could not be stopped:

mysqld is running as pid 4475
Error: Unable to shut down server with process id 4475

by the post install scripts. Unfortunately logs don't tell why this has 
happened, it could be because of many reasons. 
"""

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community



** Changed in: mysql-8.0 (Ubuntu)
   Status: New => Incomplete

-- 
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/1876852

Title:
  package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to
  install/upgrade: installed mysql-server-8.0 package post-installation
  script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1876852/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1876783] Re: package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

2020-05-08 Thread Rafael David Tinoco
Need more information

Thank you for taking the time to file a bug report.

"""
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 5424
Error: Unable to shut down server with process id 5424
"""

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: mysql-8.0 (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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/1876783

Title:
  package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to
  install/upgrade: installed mysql-server-8.0 package post-installation
  script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1876783/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1876900] Re: package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de

2020-05-08 Thread Rafael David Tinoco
Need more information

Thank you for taking the time to file a bug report.

"""
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 56734
Error: Unable to shut down server with process id 56734
"""

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

-- 
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/1876900

Title:
  package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to
  install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0,
  o script post-installation retornou erro do status de saída 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1876900/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1582899] Re: in-target: mkinitramfs: failed to determine device for /

2020-05-08 Thread Rafael David Tinoco
I'm marking this as incomplete for 18.04.2 and wont fix for xenial based
on @ahasenack's last input.

** Also affects: base-installer (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: live-installer (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: base-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: live-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: live-installer (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: live-installer (Ubuntu Bionic)
   Status: New => Incomplete

** Changed in: live-installer (Ubuntu Xenial)
   Status: New => Won't Fix

-- 
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/1582899

Title:
  in-target: mkinitramfs: failed to determine device for /

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1582899] Re: in-target: mkinitramfs: failed to determine device for /

2020-05-08 Thread Rafael David Tinoco
Thank you for taking the time to file a bug report.

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

-- 
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/1582899

Title:
  in-target: mkinitramfs: failed to determine device for /

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1866458] Re: drbd not working after kernel upgrade 5.0.x -> 5.3.x

2020-03-18 Thread Rafael David Tinoco
@rbasak,

## Before my package is installed:

$ dpkg -l drbd-utils | grep RAID
ii  drbd-utils 8.9.10-2 amd64RAID 1 over TCP/IP for Linux (user 
utilities)

$ sudo losetup --find --show /.loop
/dev/loop0

$ sudo drbdadm create-md r0
initializing activity log
NOT initializing bitmap
Writing meta data...
New drbd meta data block successfully created.

$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
drbdsetup-84 new-minor r0 0 0
drbdmeta 0 v08 /dev/loop0 internal apply-al
drbdsetup-84 attach 0 /dev/loop0 /dev/loop0 internal
drbdsetup-84 connect r0 ipv4:10.250.99.19:7788 ipv4:10.250.99.25:7788 
--protocol=C --cram-hmac-alg=sha1 --shared-secret=secret

$ uname -a
Linux drbdtest01 4.15.0-92-generic #93-Ubuntu SMP Mon Mar 16 19:44:23 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

$ ls /dev/drbd0
/dev/drbd0

## And after my package is installed:

(k)rafaeldtinoco@drbdtest01:~$ uname -a
Linux drbdtest01 4.15.0-92-generic #93-Ubuntu SMP Mon Mar 16 19:44:23 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

(k)rafaeldtinoco@drbdtest01:~$ sudo losetup --find --show /.loop
/dev/loop0

(k)rafaeldtinoco@drbdtest01:~$ sudo drbdadm create-md r0
initializing activity log
NOT initializing bitmap
Writing meta data...
New drbd meta data block successfully created.

(k)rafaeldtinoco@drbdtest01:~$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
drbdsetup-84 new-minor r0 0 0
drbdmeta 0 v08 /dev/loop0 internal apply-al
drbdsetup-84 attach 0 /dev/loop0 /dev/loop0 internal
drbdsetup-84 connect r0 ipv4:10.250.99.19:7788 ipv4:10.250.99.25:7788 
--protocol=C --cram-hmac-alg=sha1 --shared-secret=secret 

(k)rafaeldtinoco@drbdtest01:~$ dpkg -l drbd-utils | grep RAID
ii  drbd-utils 8.9.10-2ubuntu1~ppa1 amd64RAID 1 over TCP/IP for 
Linux (user utilities)

-- 
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/1866458

Title:
  drbd  not working after kernel upgrade 5.0.x -> 5.3.x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd-utils/+bug/1866458/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1868108] [NEW] [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure

2020-03-19 Thread Rafael David Tinoco
Public bug reported:

ruby-gnome/3.4.1-2* package fails with:


2020-03-19T13:29:50+00:00: Running test for 
/tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk

Loaded suite test
Started
(run-test.rb:9142): dbind-WARNING **: 13:29:51.769: AT-SPI: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.a11y.Bus was not provided by any .service files

..[2020-03-19 13:29:52] INFO  WEBrick 1.6.0
[2020-03-19 13:29:52] INFO  ruby 2.7.0 (2019-12-25) [powerpc64le-linux-gnu]
[2020-03-19 13:29:52] INFO  WEBrick::HTTPServer#start: pid=9142 port=37651

(WebKitWebProcess:9153): dbind-WARNING **: 13:29:52.607: AT-SPI: Error 
retrieving accessibility bus address: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not 
provided by any .service files
F
===
Failure: test: #load_uri(TestWebKit2GtkWebView::#load_uri):
   expected but was
  
/tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk/test/test-webkit2-gtk-web-view.rb:106:in
 `block (2 levels) in '
 103:   @view.load_uri(http_url)
 104:   loop.run
 105: 
  => 106:   assert_true(loaded)
 107: end
 108:   end
 109: end
===[2020-03-19
 13:30:22] INFO  going to shutdown ...
[2020-03-19 13:30:22] INFO  WEBrick::HTTPServer#start done.

..
Finished in 30.95292437 seconds.
---
9 tests, 9 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
88.8889% passed
---
0.29 tests/s, 0.29 assertions/s
Failed to run test: webkit2-gtk

Failed targets: webkit2-gtk
Gdk-Message: 13:30:22.622: WebKitWebProcess: Fatal IO error 2 (No such file or 
directory) on X server :99.

autopkgtest [13:30:22]: test run-test: ---]
run-test FAIL non-zero exit status 1
autopkgtest [13:30:23]: test run-test:  - - - - - - - - - - results - - - - - - 
- - - -
autopkgtest [13:30:23]:  summary
run-test FAIL non-zero exit status 1
Exit request sent.

When running in ppc64el. This is likely due a timeout in glib main loop
for that architecture but can't know for sure. I'm opening this bug so I
can blacklist that particular test.

** Affects: ruby-gnome (Ubuntu)
 Importance: Undecided
 Assignee: Lucas Kanashiro (lucaskanashiro)
 Status: Confirmed

** Affects: ruby-gnome (Ubuntu Focal)
 Importance: Undecided
 Assignee: Lucas Kanashiro (lucaskanashiro)
 Status: Confirmed

** Also affects: ruby-gnome (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: ruby-gnome (Ubuntu Focal)
 Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)

** Changed in: ruby-gnome (Ubuntu Focal)
   Status: New => Confirmed

** Bug watch added: github.com/ruby-gnome/ruby-gnome/issues #1389
   https://github.com/ruby-gnome/ruby-gnome/issues/1389

-- 
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/1868108

Title:
  [autopkgtest][focal] ruby-gnome/3.4.1-2build1
  class:TestWebKit2GtkWebView failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-gnome/+bug/1868108/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1868108] Re: [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure

2020-03-19 Thread Rafael David Tinoco
Upstream issue:

https://github.com/ruby-gnome/ruby-gnome/issues/1389

-- 
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/1868108

Title:
  [autopkgtest][focal] ruby-gnome/3.4.1-2build1
  class:TestWebKit2GtkWebView failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-gnome/+bug/1868108/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1868108] Re: [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure

2020-03-19 Thread Rafael David Tinoco
Trying to hint this as a force-badtest in britney. Whenever this is
solved, please remove force-badtest.

-- 
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/1868108

Title:
  [autopkgtest][focal] ruby-gnome/3.4.1-2build1
  class:TestWebKit2GtkWebView failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-gnome/+bug/1868108/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1413845] Re: booth.init says to modify /etc/default/boothd, which does not exist

2020-03-19 Thread Rafael David Tinoco
Currently we have:

if [ "$RUN_ARBITRATOR" != "yes" ]; then
log_warning_msg "To run $DESC, please set RUN_ARBITRATOR to 
'yes' in /etc/default/booth"
log_end_msg 0
exit 0
fi  

# in eoan:

rafaeldtinoco@workstation:~/.../debian/booth/debian$ apt-file search booth | 
grep default
booth: /etc/default/booth

so I'm marking this as Fix Released because of upstream (Debian) fixes.

** Changed in: booth (Ubuntu)
   Status: New => Fix Released

-- 
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/1413845

Title:
  booth.init says to modify /etc/default/boothd, which does not exist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/booth/+bug/1413845/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script

2020-03-19 Thread Rafael David Tinoco
(c)rafaeldtinoco@clusterdev:~/.../sources/ubuntu/corosync$ git diff HEAD
diff --git a/debian/corosync-notifyd.init b/debian/corosync-notifyd.init
index c908618..837e48a 100644
--- a/debian/corosync-notifyd.init
+++ b/debian/corosync-notifyd.init
@@ -21,7 +21,6 @@ NAME=corosync-notifyd
 DAEMON=/usr/sbin/$NAME
 PIDFILE=/var/run/$NAME.pid
 SCRIPTNAME=/etc/init.d/$NAME
-PIDFILE=/var/run/corosync.pid
 RARUNDIR=/var/run/resource-agents

 # Exit if the package is not installed

If anyone faces this issue, just remove the second PIDFILE as it appears
to be a leftover. I'll fix this and point this out to Debian as it also
faces the same issue. NEVERTHELESS, remember that this issue would only
exist if you are using the "sysv" scripts OR the sysv-generator (making
systemd to control the service through sysv scripts).

All others are probably relying in systemd to start/stop/monitor
corosync daemon (/lib/systemd/system/corosync.service).

-- 
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/1437359

Title:
  A PIDFILE is double-defined for the corosync-notifyd init script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1586876] Re: Corosync report "Started" itself too early

2020-03-19 Thread Rafael David Tinoco
** Also affects: corosync (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: corosync (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: corosync (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: corosync (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: corosync (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: corosync (Ubuntu Focal)
   Importance: Medium
 Assignee: guessi (guessi)
   Status: In Progress

** Changed in: corosync (Ubuntu Focal)
 Assignee: guessi (guessi) => (unassigned)

** Changed in: corosync (Ubuntu Focal)
   Importance: Medium => Undecided

** Changed in: corosync (Ubuntu Trusty)
   Status: New => Won't Fix

** Changed in: corosync (Ubuntu Disco)
   Status: New => Won't Fix

** Changed in: corosync (Ubuntu Focal)
   Status: In Progress => Triaged

** Changed in: corosync (Ubuntu Eoan)
   Status: New => Triaged

** Changed in: corosync (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: corosync (Ubuntu Bionic)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1586876

Title:
  Corosync report "Started" itself too early

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1586876/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1239734] Re: corosync sends first time users on a hunt, simple fix

2020-03-19 Thread Rafael David Tinoco
Currently corosync is started by default with a single node ring formed
with localhost:

(c)rafaeldtinoco@clusterdev:~/.../sources/ubuntu/corosync$ systemctl status 
corosync
● corosync.service - Corosync Cluster Engine
 Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Thu 2020-03-19 20:16:49 UTC; 2min 10s ago
   Docs: man:corosync
 man:corosync.conf
 man:corosync_overview
   Main PID: 851 (corosync)
  Tasks: 9 (limit: 23186)
 Memory: 125.7M
 CGroup: /system.slice/corosync.service
 └─851 /usr/sbin/corosync -f

(c)rafaeldtinoco@clusterdev:~/.../sources/ubuntu/corosync$ sudo 
corosync-quorumtool
Quorum information
--
Date: Thu Mar 19 20:19:37 2020
Quorum provider:  corosync_votequorum
Nodes:1
Node ID:  1
Ring ID:  1.5
Quorate:  Yes

Votequorum information
--
Expected votes:   1
Highest expected: 1
Total votes:  1
Quorum:   1
Flags:Quorate

Membership information
--
Nodeid  Votes Name
 1  1 node1 (local)

Because we try to make things "easier" (no failure on startups because
the lack of configuration files, for example). Of course having a HA
cluster is something beyond the scope of this bug and it might require
an experienced system administrator to be able to make corosync to work
in a meaningful way.

Nevertheless, for any future bug readers, may I recommend the following
reading:

https://discourse.ubuntu.com/t/ubuntu-high-availability-shared-scsi-
disk-environments/14874

in order to get a simple, yet supported, cluster configuration in a
shared scsi environment.

Thanks for reporting this.

** Changed in: corosync (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: corosync (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/1239734

Title:
  corosync sends first time users on a hunt, simple fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1239734/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script

2020-03-19 Thread Rafael David Tinoco
Okay, this is a very simple fix but it is tricky... mainly because ..
possibly 99% of the users of this package are using systemd and the
corosync service unit file... which does not face this issue. I'm not
entirely sure a SRU is the right thing to do on all affected Ubuntu
versions (Xenial, Bionic, Eoan). Will discuss this with the server team.

Meanwhile, fixing Focal seems appropriate just because its not released
yet ... :\ but I'll keep this "on the hand" until I have more fixes so I
do the SRU all at once.

** Changed in: corosync (Ubuntu Focal)
   Status: Triaged => In Progress

-- 
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/1437359

Title:
  A PIDFILE is double-defined for the corosync-notifyd init script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1677684] Re: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found

2020-03-19 Thread Rafael David Tinoco
This issue still exists and should be fixed. I'm putting together with
some other SRUs so all of them are done at once. Thanks @niedbalski for
bringing up this issue. I'll fix Ubuntu Focal for now and try to get
along with the needed SRUs.

** Changed in: corosync (Ubuntu Trusty)
 Assignee: Jorge Niedbalski (niedbalski) => (unassigned)

** Changed in: corosync (Ubuntu)
 Assignee: Jorge Niedbalski (niedbalski) => (unassigned)

** Changed in: corosync (Ubuntu Zesty)
 Assignee: Jorge Niedbalski (niedbalski) => (unassigned)

** Changed in: corosync (Ubuntu Xenial)
 Assignee: Jorge Niedbalski (niedbalski) => (unassigned)

** Changed in: corosync (Ubuntu)
   Importance: Medium => Undecided

** Changed in: corosync (Ubuntu Zesty)
   Importance: Medium => Undecided

** Changed in: corosync (Ubuntu Trusty)
   Importance: Medium => Undecided

** Changed in: corosync (Ubuntu Xenial)
   Importance: Medium => Undecided

** Also affects: corosync (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: corosync (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: corosync (Ubuntu Focal)
   Importance: Undecided
   Status: Incomplete

** Also affects: corosync (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: corosync (Ubuntu Focal)
   Status: Incomplete => Confirmed

** Changed in: corosync (Ubuntu Eoan)
   Status: New => Confirmed

** Changed in: corosync (Ubuntu Disco)
   Status: New => Won't Fix

** Changed in: corosync (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: corosync (Ubuntu Zesty)
   Status: Incomplete => Won't Fix

** Changed in: corosync (Ubuntu Xenial)
   Status: Incomplete => Confirmed

** Changed in: corosync (Ubuntu Trusty)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1677684

Title:
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-
  blackbox: not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 637127] Re: TTL is one - prevents multicast routing

2020-03-19 Thread Rafael David Tinoco
Correct flag for this bug is: Fix Released

per upstream fix:

commit d3b983953d43dd17162be04de405d223fb21cd26
Author: Angus Salkeld 
Date:   Wed Nov 24 14:35:56 2010 +1100

Add totem/interface/ttl config option.

This adds a per-interface config option to
adjust the TTL.

Signed-off-by: Angus Salkeld 
Reviewed-by: Steven Dake 

** Changed in: corosync (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/637127

Title:
  TTL is one - prevents multicast routing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/637127/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1019833] Re: problem wtih the configuration of the cluster.conf file. when

2020-03-19 Thread Rafael David Tinoco
** Also affects: corosync (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: corosync (Ubuntu Trusty)
   Status: New => Incomplete

** Changed in: corosync (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: corosync (Ubuntu)
 Assignee: Joao (nobrefr) => (unassigned)

** Changed in: corosync (Ubuntu)
   Importance: Medium => Undecided

** Changed in: corosync (Ubuntu)
   Status: Fix Released => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1019833

Title:
   problem wtih the configuration of the cluster.conf file. when

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1019833/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1586876] Re: Corosync report "Started" itself too early

2020-03-19 Thread Rafael David Tinoco
>From upstream documentation:

"""
Pacemaker used to obtain membership and quorum from a custom Corosync plugin. 
This plugin also had the capability to start Pacemaker automatically when 
Corosync was started. Neither behavior is possible with Corosync 2.0 and beyond 
as support for plugins was removed.

Instead, Pacemaker must be started as a separate job/initscript. Also, since 
Pacemaker made use of the plugin for message routing, a node using the plugin 
(Corosync prior to 2.0) cannot talk to one that isn’t (Corosync 2.0+).
Rolling upgrades between these versions are therefore not possible and an 
alternate strategy must be used.
"""

showing that since Ubuntu Trusty this detection behavior is not
supported any longer. Nowadays, we start both services separately and
using systemd.

Corosync starts with a simple one-node only (localhost) ring configured:

(c)rafaeldtinoco@clusterdev:~$ systemctl status corosync
● corosync.service - Corosync Cluster Engine
 Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Thu 2020-03-19 20:16:49 UTC; 45min ago
   Docs: man:corosync
 man:corosync.conf
 man:corosync_overview
   Main PID: 851 (corosync)
  Tasks: 9 (limit: 23186)
 Memory: 125.9M
 CGroup: /system.slice/corosync.service
 └─851 /usr/sbin/corosync -f

(c)rafaeldtinoco@clusterdev:~$ sudo corosync-quorumtool
Quorum information
--
Date: Thu Mar 19 21:02:21 2020
Quorum provider:  corosync_votequorum
Nodes:1
Node ID:  1
Ring ID:  1.5
Quorate:  Yes

Votequorum information
--
Expected votes:   1
Highest expected: 1
Total votes:  1
Quorum:   1
Flags:Quorate

Membership information
--
Nodeid  Votes Name
 1  1 node1 (local)

AND systemd is responsible to guarantee the synchronicity needed.



>From pacemaker service unit:

...
After=corosync.service
Requires=corosync.service

...

# If you want Corosync to stop whenever Pacemaker is stopped,
# uncomment the next line too:
#
# ExecStopPost=/bin/sh -c 'pidof pacemaker-controld || killall -TERM corosync'

...

# Pacemaker will restart along with Corosync if Corosync is stopped while
# Pacemaker is running.
# In this case, if you want to be fenced always (if you do not want to restart)
# uncomment ExecStopPost below.
#
# ExecStopPost=/bin/sh -c 'pidof corosync || \
#  /usr/bin/systemctl --no-block stop pacemaker' 

you have different options to control behavior for start/stop and
restart accordingly with corosync status.


** Changed in: corosync (Ubuntu Focal)
   Status: Triaged => Fix Released

** Changed in: corosync (Ubuntu Eoan)
   Status: Triaged => Fix Released

** Changed in: corosync (Ubuntu Bionic)
   Status: Triaged => Fix Released

** Changed in: corosync (Ubuntu Xenial)
   Status: Triaged => Won't Fix

-- 
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/1586876

Title:
  Corosync report "Started" itself too early

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1586876/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1654403] Re: Race condition in hacluster charm that leaves pacemaker down

2020-03-19 Thread Rafael David Tinoco
** Also affects: corosync (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: corosync (Ubuntu Xenial)
   Status: New => Incomplete

** Changed in: corosync (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1654403

Title:
  Race condition in hacluster charm that leaves pacemaker down

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1654403/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1340172] Re: [OSCI] Add mamange/unmanage blocks to corosync init scripts

2020-03-19 Thread Rafael David Tinoco
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.

Unfortunately this bug is old for us to consider having an sysv-compatible
option to put the cluster into maintenance mode. Corosync is also being managed,
for sometime now, by systemd so this particular change wouldn't make much sense.
IMHO this type of cluster change should be done by the cluster administrator in
specific tools like crmsh, pcs, and not in an init script.

It is unfortunate that we were unable to resolve this defect, however
there appears to be no further action possible at this time. I am
therefore moving the bug to 'Incomplete'. If you disagree or have
new information, we would be grateful if you could please add a comment 
stating why and then change the status of the bug to 'New'.


** Also affects: corosync (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: corosync (Ubuntu Precise)
   Status: New => Incomplete

** Changed in: corosync (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: corosync (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: corosync (Ubuntu Precise)
   Status: Incomplete => Won't Fix

** Changed in: corosync (Ubuntu)
   Importance: High => Undecided

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1340172

Title:
  [OSCI] Add mamange/unmanage blocks to corosync init scripts

To manage notifications about this bug go to:
https://bugs.launchpad.net/fuel/+bug/1340172/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1251298] Re: Failed to sign on to LRMd with Heartbeat/Pacemaker

2020-03-19 Thread Rafael David Tinoco
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.

Judging by the existing comments, and the pointed upstream discussion thread, it
appears that the wrong lrmd was being set after upgrade and that led existing
cluster to confusion when connecting to the local resource manager daemon.

It is unfortunate that we were unable to resolve this defect, however
there appears to be no further action possible at this time. I am
therefore moving the bug to 'Incomplete'. If you disagree or have
new information, we would be grateful if you could please add a comment
stating why and then change the status of the bug to 'New'.

** Changed in: cluster-glue (Ubuntu)
   Status: Confirmed => Incomplete

** Also affects: cluster-glue (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: cluster-glue (Ubuntu Trusty)
   Status: New => Incomplete

** Changed in: cluster-glue (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: cluster-glue (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to cluster-glue in Ubuntu.
https://bugs.launchpad.net/bugs/1251298

Title:
  Failed to sign on to LRMd with Heartbeat/Pacemaker

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/1251298/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


<    1   2   3   4   5   6   7   >