| 2015-03-27 14:23:04 |
Bogdan Dobrelya |
bug |
|
|
added bug |
| 2015-03-27 14:26:02 |
Bogdan Dobrelya |
bug |
|
|
added subscriber Thomas Goirand |
| 2015-03-27 14:26:53 |
Bogdan Dobrelya |
description |
A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE:
> PIDFILE=/var/run/$NAME.pid
> SCRIPTNAME=/etc/init.d/$NAME
> PIDFILE=/var/run/corosync.pid
The first one is correct and the second one is wrong as it refers to the corosync service's pidfile instead |
A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE:
> PIDFILE=/var/run/$NAME.pid
> SCRIPTNAME=/etc/init.d/$NAME
> PIDFILE=/var/run/corosync.pid
The first one is correct and the second one is wrong as it refers to the corosync service's pidfile instead
The corosync package version is 2.3.3-1ubuntu1 |
|
| 2019-07-04 03:24:53 |
Rafael David Tinoco |
corosync (Ubuntu): status |
New |
Triaged |
|
| 2019-07-04 03:24:58 |
Rafael David Tinoco |
corosync (Ubuntu): assignee |
|
Rafael David Tinoco (rafaeldtinoco) |
|
| 2019-07-04 03:25:04 |
Rafael David Tinoco |
tags |
trusty |
trusty ubuntu-ha |
|
| 2019-10-30 13:15:11 |
Rafael David Tinoco |
bug |
|
|
added subscriber Ubuntu Server High Availability |
| 2020-03-19 21:13:13 |
Rafael David Tinoco |
bug |
|
|
added subscriber Ubuntu Server |
| 2020-03-19 21:14:25 |
Rafael David Tinoco |
nominated for series |
|
Ubuntu Disco |
|
| 2020-03-19 21:14:25 |
Rafael David Tinoco |
bug task added |
|
corosync (Ubuntu Disco) |
|
| 2020-03-19 21:14:25 |
Rafael David Tinoco |
nominated for series |
|
Ubuntu Focal |
|
| 2020-03-19 21:14:25 |
Rafael David Tinoco |
bug task added |
|
corosync (Ubuntu Focal) |
|
| 2020-03-19 21:14:25 |
Rafael David Tinoco |
nominated for series |
|
Ubuntu Trusty |
|
| 2020-03-19 21:14:25 |
Rafael David Tinoco |
bug task added |
|
corosync (Ubuntu Trusty) |
|
| 2020-03-19 21:14:25 |
Rafael David Tinoco |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-03-19 21:14:25 |
Rafael David Tinoco |
bug task added |
|
corosync (Ubuntu Bionic) |
|
| 2020-03-19 21:14:25 |
Rafael David Tinoco |
nominated for series |
|
Ubuntu Xenial |
|
| 2020-03-19 21:14:25 |
Rafael David Tinoco |
bug task added |
|
corosync (Ubuntu Xenial) |
|
| 2020-03-19 21:14:25 |
Rafael David Tinoco |
nominated for series |
|
Ubuntu Eoan |
|
| 2020-03-19 21:14:25 |
Rafael David Tinoco |
bug task added |
|
corosync (Ubuntu Eoan) |
|
| 2020-03-19 21:14:37 |
Rafael David Tinoco |
corosync (Ubuntu Focal): assignee |
Rafael David Tinoco (rafaeldtinoco) |
|
|
| 2020-03-19 21:14:50 |
Rafael David Tinoco |
corosync (Ubuntu Disco): status |
New |
Won't Fix |
|
| 2020-03-19 21:14:53 |
Rafael David Tinoco |
corosync (Ubuntu Trusty): status |
New |
Won't Fix |
|
| 2020-03-19 21:15:00 |
Rafael David Tinoco |
corosync (Ubuntu Eoan): status |
New |
Triaged |
|
| 2020-03-19 21:15:03 |
Rafael David Tinoco |
corosync (Ubuntu Xenial): status |
New |
Triaged |
|
| 2020-03-19 21:15:06 |
Rafael David Tinoco |
corosync (Ubuntu Bionic): status |
New |
Triaged |
|
| 2020-03-19 21:21:22 |
Rafael David Tinoco |
corosync (Ubuntu Focal): status |
Triaged |
In Progress |
|
| 2020-03-19 21:21:56 |
Rafael David Tinoco |
corosync (Ubuntu Xenial): status |
Triaged |
In Progress |
|
| 2020-03-19 21:22:00 |
Rafael David Tinoco |
corosync (Ubuntu Xenial): status |
In Progress |
Triaged |
|
| 2020-03-23 16:20:01 |
Rafael David Tinoco |
tags |
trusty ubuntu-ha |
server-triage-discuss trusty ubuntu-ha |
|
| 2020-03-30 01:13:14 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/corosync/+git/corosync/+merge/381355 |
|
| 2020-04-09 14:50:27 |
Launchpad Janitor |
corosync (Ubuntu Focal): status |
In Progress |
Fix Released |
|
| 2020-06-17 15:28:39 |
Robie Basak |
tags |
server-triage-discuss trusty ubuntu-ha |
trusty ubuntu-ha |
|
| 2020-08-18 17:02:22 |
Brian Murray |
corosync (Ubuntu Eoan): status |
Triaged |
Won't Fix |
|
| 2021-01-20 21:52:12 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/corosync/+git/corosync/+merge/396608 |
|
| 2021-01-21 12:40:57 |
Launchpad Janitor |
merge proposal unlinked |
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/corosync/+git/corosync/+merge/396608 |
|
|
| 2021-07-20 18:14:01 |
Lucas Kanashiro |
corosync (Ubuntu Bionic): importance |
Undecided |
Low |
|
| 2021-09-28 16:09:35 |
Miriam España Acebal |
corosync (Ubuntu Bionic): assignee |
|
Miriam España Acebal (mirespace) |
|
| 2021-09-28 16:09:39 |
Miriam España Acebal |
corosync (Ubuntu Bionic): status |
Triaged |
In Progress |
|
| 2021-09-28 20:30:50 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~mirespace/ubuntu/+source/corosync/+git/corosync/+merge/409319 |
|
| 2021-09-29 10:40:30 |
Miriam España Acebal |
corosync (Ubuntu Xenial): status |
Triaged |
Won't Fix |
|
| 2021-09-29 20:36:08 |
Miriam España Acebal |
description |
A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE:
> PIDFILE=/var/run/$NAME.pid
> SCRIPTNAME=/etc/init.d/$NAME
> PIDFILE=/var/run/corosync.pid
The first one is correct and the second one is wrong as it refers to the corosync service's pidfile instead
The corosync package version is 2.3.3-1ubuntu1 |
[Impact]
Users that use the sysv services provided by corosync-notifyd and corosync packages
may find a corosync-notifyd service's misfunction because it uses the pid file
created by corosync service.
[Test Plan]
In a new VM with bionic (specifically for this testing):
#Disabling systemd (this will lead you to a non-usable system at the end for other things, but
this is only for testing purposes of this bug -systemctl disable <service> didn't work-):
sudo apt remove --purge systemd
#Install corosync and corosync-notifyd:
sudo apt install corosync corosync-notifyd
#check versions (optional):
ubuntu@bionic-corosync-sysv:~/Builds$ dpkg -l | grep coro
ii corosync 2.4.3-0ubuntu1.2 amd64 cluster engine daemon and utilities
ii corosync-notifyd 2.4.3-0ubuntu1.2 amd64 cluster engine notification daemon
ii libcorosync-common4:amd64 2.4.3-0ubuntu1.2 amd64 cluster engine common library
#Start notifyd service:
ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo ./corosync-notifyd start
* Starting corosync notifying daemon corosync-notifyd [ OK ]
#Check that pid filename is not correct:
ubuntu@bionic-corosync-sysv:/etc/init.d$ l /var/run/coro*
/var/run/corosync.pid
#stop de service, check pid file is gone and install new version:
ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo ./corosync-notifyd stop
* Stopping corosync notifying daemon corosync-notifyd [ OK ]
ubuntu@bionic-corosync-sysv:/etc/init.d$ l /var/run/coro*
ls: cannot access '/var/run/coro*': No such file or directory
ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo dpkg -i /home/ubuntu/Builds/corosync-notifyd_2.4.3-0ubuntu1.3_amd64.deb
(Reading database ... 59514 files and directories currently installed.)
Preparing to unpack .../corosync-notifyd_2.4.3-0ubuntu1.3_amd64.deb ...
Unpacking corosync-notifyd (2.4.3-0ubuntu1.3) over (2.4.3-0ubuntu1.2) ...
/var/lib/dpkg/info/corosync-notifyd.postrm: 12: /var/lib/dpkg/info/corosync-notifyd.postrm: systemctl: not found
Setting up corosync-notifyd (2.4.3-0ubuntu1.3) ...
Installing new version of config file /etc/init.d/corosync-notifyd ...
Can't exec "systemctl": No such file or directory at /usr/sbin/update-rc.d line 93.
/usr/sbin/invoke-rc.d: 282: /usr/sbin/invoke-rc.d: systemctl: not found
invoke-rc.d: could not determine current runlevel
invoke-rc.d: WARNING: No init system and policy-rc.d missing! Defaulting to block.
Processing triggers for dbus (1.12.2-1ubuntu1.2) ...
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
#Start notifyd service
ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo ./corosync-notifyd start
* Starting corosync notifying daemon corosync-notifyd [ OK ]
#Check pid-filename is now the same as daemon's name (corosync-notifyd):
ubuntu@bionic-corosync-sysv:/etc/init.d$ l /var/run/coro*
/var/run/corosync-notifyd.pid
[Where problems could occur]
The fix is cherrypicked from the Focal's solution, only affects corosync-notifyd and
corosync services. No other services depend on this pid files. No systemd services affected.
[Other Info]
This solution follows the example of the same bug fixed in Focal at https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622 ,
alongside bug https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 (in progress to be SRU processed also for Bionic).
Although the number of users affected by this is a minority, I decided to fix this
in concordance with that this issue is fixed in Focal and it's a copy/paste error
easy to understand and without impact in any other application or system.
--------------------------
[Original Description]
A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE:
> PIDFILE=/var/run/$NAME.pid
> SCRIPTNAME=/etc/init.d/$NAME
> PIDFILE=/var/run/corosync.pid
The first one is correct and the second one is wrong as it refers to the corosync service's pidfile instead
The corosync package version is 2.3.3-1ubuntu1 |
|
| 2021-09-29 20:36:20 |
Miriam España Acebal |
description |
[Impact]
Users that use the sysv services provided by corosync-notifyd and corosync packages
may find a corosync-notifyd service's misfunction because it uses the pid file
created by corosync service.
[Test Plan]
In a new VM with bionic (specifically for this testing):
#Disabling systemd (this will lead you to a non-usable system at the end for other things, but
this is only for testing purposes of this bug -systemctl disable <service> didn't work-):
sudo apt remove --purge systemd
#Install corosync and corosync-notifyd:
sudo apt install corosync corosync-notifyd
#check versions (optional):
ubuntu@bionic-corosync-sysv:~/Builds$ dpkg -l | grep coro
ii corosync 2.4.3-0ubuntu1.2 amd64 cluster engine daemon and utilities
ii corosync-notifyd 2.4.3-0ubuntu1.2 amd64 cluster engine notification daemon
ii libcorosync-common4:amd64 2.4.3-0ubuntu1.2 amd64 cluster engine common library
#Start notifyd service:
ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo ./corosync-notifyd start
* Starting corosync notifying daemon corosync-notifyd [ OK ]
#Check that pid filename is not correct:
ubuntu@bionic-corosync-sysv:/etc/init.d$ l /var/run/coro*
/var/run/corosync.pid
#stop de service, check pid file is gone and install new version:
ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo ./corosync-notifyd stop
* Stopping corosync notifying daemon corosync-notifyd [ OK ]
ubuntu@bionic-corosync-sysv:/etc/init.d$ l /var/run/coro*
ls: cannot access '/var/run/coro*': No such file or directory
ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo dpkg -i /home/ubuntu/Builds/corosync-notifyd_2.4.3-0ubuntu1.3_amd64.deb
(Reading database ... 59514 files and directories currently installed.)
Preparing to unpack .../corosync-notifyd_2.4.3-0ubuntu1.3_amd64.deb ...
Unpacking corosync-notifyd (2.4.3-0ubuntu1.3) over (2.4.3-0ubuntu1.2) ...
/var/lib/dpkg/info/corosync-notifyd.postrm: 12: /var/lib/dpkg/info/corosync-notifyd.postrm: systemctl: not found
Setting up corosync-notifyd (2.4.3-0ubuntu1.3) ...
Installing new version of config file /etc/init.d/corosync-notifyd ...
Can't exec "systemctl": No such file or directory at /usr/sbin/update-rc.d line 93.
/usr/sbin/invoke-rc.d: 282: /usr/sbin/invoke-rc.d: systemctl: not found
invoke-rc.d: could not determine current runlevel
invoke-rc.d: WARNING: No init system and policy-rc.d missing! Defaulting to block.
Processing triggers for dbus (1.12.2-1ubuntu1.2) ...
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
#Start notifyd service
ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo ./corosync-notifyd start
* Starting corosync notifying daemon corosync-notifyd [ OK ]
#Check pid-filename is now the same as daemon's name (corosync-notifyd):
ubuntu@bionic-corosync-sysv:/etc/init.d$ l /var/run/coro*
/var/run/corosync-notifyd.pid
[Where problems could occur]
The fix is cherrypicked from the Focal's solution, only affects corosync-notifyd and
corosync services. No other services depend on this pid files. No systemd services affected.
[Other Info]
This solution follows the example of the same bug fixed in Focal at https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622 ,
alongside bug https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 (in progress to be SRU processed also for Bionic).
Although the number of users affected by this is a minority, I decided to fix this
in concordance with that this issue is fixed in Focal and it's a copy/paste error
easy to understand and without impact in any other application or system.
--------------------------
[Original Description]
A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE:
> PIDFILE=/var/run/$NAME.pid
> SCRIPTNAME=/etc/init.d/$NAME
> PIDFILE=/var/run/corosync.pid
The first one is correct and the second one is wrong as it refers to the corosync service's pidfile instead
The corosync package version is 2.3.3-1ubuntu1 |
[SRU]
[Impact]
Users that use the sysv services provided by corosync-notifyd and corosync packages
may find a corosync-notifyd service's misfunction because it uses the pid file
created by corosync service.
[Test Plan]
In a new VM with bionic (specifically for this testing):
#Disabling systemd (this will lead you to a non-usable system at the end for other things, but
this is only for testing purposes of this bug -systemctl disable <service> didn't work-):
sudo apt remove --purge systemd
#Install corosync and corosync-notifyd:
sudo apt install corosync corosync-notifyd
#check versions (optional):
ubuntu@bionic-corosync-sysv:~/Builds$ dpkg -l | grep coro
ii corosync 2.4.3-0ubuntu1.2 amd64 cluster engine daemon and utilities
ii corosync-notifyd 2.4.3-0ubuntu1.2 amd64 cluster engine notification daemon
ii libcorosync-common4:amd64 2.4.3-0ubuntu1.2 amd64 cluster engine common library
#Start notifyd service:
ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo ./corosync-notifyd start
* Starting corosync notifying daemon corosync-notifyd [ OK ]
#Check that pid filename is not correct:
ubuntu@bionic-corosync-sysv:/etc/init.d$ l /var/run/coro*
/var/run/corosync.pid
#stop de service, check pid file is gone and install new version:
ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo ./corosync-notifyd stop
* Stopping corosync notifying daemon corosync-notifyd [ OK ]
ubuntu@bionic-corosync-sysv:/etc/init.d$ l /var/run/coro*
ls: cannot access '/var/run/coro*': No such file or directory
ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo dpkg -i /home/ubuntu/Builds/corosync-notifyd_2.4.3-0ubuntu1.3_amd64.deb
(Reading database ... 59514 files and directories currently installed.)
Preparing to unpack .../corosync-notifyd_2.4.3-0ubuntu1.3_amd64.deb ...
Unpacking corosync-notifyd (2.4.3-0ubuntu1.3) over (2.4.3-0ubuntu1.2) ...
/var/lib/dpkg/info/corosync-notifyd.postrm: 12: /var/lib/dpkg/info/corosync-notifyd.postrm: systemctl: not found
Setting up corosync-notifyd (2.4.3-0ubuntu1.3) ...
Installing new version of config file /etc/init.d/corosync-notifyd ...
Can't exec "systemctl": No such file or directory at /usr/sbin/update-rc.d line 93.
/usr/sbin/invoke-rc.d: 282: /usr/sbin/invoke-rc.d: systemctl: not found
invoke-rc.d: could not determine current runlevel
invoke-rc.d: WARNING: No init system and policy-rc.d missing! Defaulting to block.
Processing triggers for dbus (1.12.2-1ubuntu1.2) ...
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
#Start notifyd service
ubuntu@bionic-corosync-sysv:/etc/init.d$ sudo ./corosync-notifyd start
* Starting corosync notifying daemon corosync-notifyd [ OK ]
#Check pid-filename is now the same as daemon's name (corosync-notifyd):
ubuntu@bionic-corosync-sysv:/etc/init.d$ l /var/run/coro*
/var/run/corosync-notifyd.pid
[Where problems could occur]
The fix is cherrypicked from the Focal's solution, only affects corosync-notifyd and
corosync services. No other services depend on this pid files. No systemd services affected.
[Other Info]
This solution follows the example of the same bug fixed in Focal at https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622 ,
alongside bug https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684 (in progress to be SRU processed also for Bionic).
Although the number of users affected by this is a minority, I decided to fix this
in concordance with that this issue is fixed in Focal and it's a copy/paste error
easy to understand and without impact in any other application or system.
--------------------------
[Original Description]
A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE:
> PIDFILE=/var/run/$NAME.pid
> SCRIPTNAME=/etc/init.d/$NAME
> PIDFILE=/var/run/corosync.pid
The first one is correct and the second one is wrong as it refers to the corosync service's pidfile instead
The corosync package version is 2.3.3-1ubuntu1 |
|
| 2021-10-13 21:03:58 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2021-10-18 16:57:46 |
Launchpad Janitor |
merge proposal unlinked |
https://code.launchpad.net/~mirespace/ubuntu/+source/corosync/+git/corosync/+merge/409319 |
|
|
| 2021-10-22 08:48:34 |
Miriam España Acebal |
corosync (Ubuntu Bionic): status |
In Progress |
Won't Fix |
|
| 2021-10-22 08:48:37 |
Miriam España Acebal |
corosync (Ubuntu Bionic): importance |
Low |
Wishlist |
|
| 2021-10-22 08:48:45 |
Miriam España Acebal |
removed subscriber Ubuntu Server |
|
|
|
