Ubuntu
corosync package

/usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found

Bug #1677684 reported by Jorge Niedbalski
22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
corosync (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Won't Fix
Undecided
Unassigned
Xenial
Won't Fix
Undecided
Unassigned
Zesty
Won't Fix
Undecided
Unassigned
Bionic
Fix Released
Undecided
Miriam España Acebal
Disco
Won't Fix
Undecided
Unassigned
Eoan
Won't Fix
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned

Bug Description

[SRU]

[Impact]

 The command corosync-blackbox can't be used in Bionic.

[Test Plan]

 1) sudo apt-get install corosync
 2) sudo corosync-blackbox.

 root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep black
 /usr/bin/corosync-blackbox

 Expected results: corosync-blackbox runs OK:

 ubuntu@bionic:~/tmp$ sudo corosync-blackbox
 Dumping the contents of /var/lib/corosync/fdata
 [debug] shm size:8392704; real_size:8392704; rb->word_size:2098176
 [debug] read total of: 8392724
 Ringbuffer:
  ->NORMAL
  ->write_pt [2866]
  ->read_pt [0]
  ->size [2098176 words]
  =>free [8381236 bytes]
  =>used [11464 bytes]
 debug Sep 28 20:21:50 totempg_waiting_trans_ack_cb(286):14: waiting_trans_ack changed to 1
 debug Sep 28 20:21:50 totemsrp_initialize(900):14: Token Timeout (3000 ms) retransmit timeout (294 ms)
 debug Sep 28 20:21:50 totemsrp_initialize(903):14: token hold (225 ms) retransmits before loss (10 retrans)
 debug Sep 28 20:21:50 totemsrp_initialize(910):14: join (50 ms) send_join (0 ms) consensus (3600 ms) merge (200 ms)
 debug Sep 28 20:21:50 totemsrp_initialize(913):14: downcheck (1000 ms) fail to recv const (2500 msgs)
 debug Sep 28 20:21:50 totemsrp_initialize(915):14: seqno unchanged const (30 rotations) Maximum network MTU 1401
 debug Sep 28 20:21:50 totemsrp_initialize(919):14: window size per rotation (50 messages) maximum messages per rotation (17 messages)
 debug Sep 28 20:21:50 totemsrp_initialize(923):14: missed count const (5 messages)
 debug Sep 28 20:21:50 totemsrp_initialize(926):14: send threads (0 threads)
 debug Sep 28 20:21:50 totemsrp_initialize(929):14: RRP token expired timeout (294 ms)
 debug Sep 28 20:21:50 totemsrp_initialize(932):14: RRP token problem counter (2000 ms)
 debug Sep 28 20:21:50 totemsrp_initialize(935):14: RRP threshold (10 problem count)
 debug Sep 28 20:21:50 totemsrp_initialize(938):14: RRP multicast threshold (100 problem count)
 debug Sep 28 20:21:50 totemsrp_initialize(941):14: RRP automatic recovery check timeout (1000 ms)
 debug Sep 28 20:21:50 totemsrp_initialize(943):14: RRP mode set to none.
 debug Sep 28 20:21:50 totemsrp_initialize(946):14: heartbeat_failures_allowed (0)
 debug Sep 28 20:21:50 totemsrp_initialize(948):14: max_network_delay (50 ms)
 debug Sep 28 20:21:50 totemsrp_initialize(971):14: HeartBeat is Disabled. To enable set heartbeat_failures_allowed > 0
 notice Sep 28 20:21:50 totemnet_instance_initialize(248):14: Initializing transport (UDP/IP Multicast).
 notice Sep 28 20:21:50 init_nss(688):14: Initializing transmit/receive security (NSS) crypto: none hash: none
 debug Sep 28 20:21:50 totemudp_build_sockets_ip(923):14: Receive multicast socket recv buffer size (320000 bytes).
 debug Sep 28 20:21:50 totemudp_build_sockets_ip(929):14: Transmit multicast socket send buffer size (320000 bytes).
 debug Sep 28 20:21:50 totemudp_build_sockets_ip(935):14: Local receive multicast loop socket recv buffer size (320000 bytes).
 debug Sep 28 20:21:50 totemudp_build_sockets_ip(941):14: Local transmit multicast loop socket send buffer size (320000 bytes).
 trace Sep 28 20:21:50 qb_loop_poll_add(368):9: grown poll array to 2 for FD 8
 trace Sep 28 20:21:50 qb_loop_poll_add(368):9: grown poll array to 3 for FD 9
 trace Sep 28 20:21:50 qb_loop_poll_add(368):9: grown poll array to 4 for FD 12
 notice Sep 28 20:21:50 timer_function_netif_check_timeout(669):14: The network interface [127.0.0.1] is now up.
 debug Sep 28 20:21:50 main_iface_change_fn(5101):14: Created or loaded sequence id 8.127.0.0.1 for this ring.
 info Sep 28 20:21:50 qb_ipcs_us_publish(537):9: server name: cmap
 trace Sep 28 20:21:50 qb_loop_poll_add(368):9: grown poll array to 5 for FD 13
 info Sep 28 20:21:50 qb_ipcs_us_publish(537):9: server name: cfg
 trace Sep 28 20:21:50 qb_loop_poll_add(368):9: grown poll array to 6 for FD 14
 info Sep 28 20:21:50 qb_ipcs_us_publish(537):9: server name: cpg
 trace Sep 28 20:21:50 qb_loop_poll_add(368):9: grown poll array to 7 for FD 15
 info Sep 28 20:21:50 qb_ipcs_us_publish(537):9: server name: votequorum
 trace Sep 28 20:21:50 qb_loop_poll_add(368):9: grown poll array to 8 for FD 16
 info Sep 28 20:21:50 qb_ipcs_us_publish(537):9: server name: quorum
 trace Sep 28 20:21:50 qb_loop_poll_add(368):9: grown poll array to 9 for FD 17
 debug Sep 28 20:21:50 memb_state_gather_enter(2222):14: entering GATHER state from 15(interface change).
 debug Sep 28 20:21:50 memb_state_commit_token_create(3274):14: Creating commit token because I am the rep.
 debug Sep 28 20:21:50 old_ring_state_save(1605):14: Saving state aru 0 high seq received 0
 debug Sep 28 20:21:50 memb_state_commit_enter(2271):14: entering COMMIT state.
 debug Sep 28 20:21:50 message_handler_memb_commit_token(4929):14: got commit token
 debug Sep 28 20:21:50 memb_state_recovery_enter(2308):14: entering RECOVERY state.
 debug Sep 28 20:21:50 memb_state_recovery_enter(2354):14: position [0] member 127.0.0.1:
 debug Sep 28 20:21:50 memb_state_recovery_enter(2358):14: previous ring seq 8 rep 127.0.0.1
 debug Sep 28 20:21:50 memb_state_recovery_enter(2364):14: aru 0 high delivered 0 received flag 1
 debug Sep 28 20:21:50 memb_state_recovery_enter(2462):14: Did not need to originate any messages in recovery.
 debug Sep 28 20:21:50 message_handler_memb_commit_token(4929):14: got commit token
 debug Sep 28 20:21:50 message_handler_memb_commit_token(4994):14: Sending initial ORF token
 trace Sep 28 20:21:50 totemsrp_mcast(2547):14: mcasted message added to pending queue
 debug Sep 28 20:21:50 message_handler_orf_token(4176):14: token retrans flag is 0 my set retrans flag0 retrans queue empty 1 count 0, aru 0
 debug Sep 28 20:21:50 message_handler_orf_token(4187):14: install seq 0 aru 0 high seq received 0
 debug Sep 28 20:21:50 message_handler_orf_token(4176):14: token retrans flag is 0 my set retrans flag0 retrans queue empty 1 count 1, aru 0
 debug Sep 28 20:21:50 message_handler_orf_token(4187):14: install seq 0 aru 0 high seq received 0
 debug Sep 28 20:21:50 message_handler_orf_token(4176):14: token retrans flag is 0 my set retrans flag0 retrans queue empty 1 count 2, aru 0
 debug Sep 28 20:21:50 message_handler_orf_token(4187):14: install seq 0 aru 0 high seq received 0
 debug Sep 28 20:21:50 message_handler_orf_token(4176):14: token retrans flag is 0 my set retrans flag0 retrans queue empty 1 count 3, aru 0
 debug Sep 28 20:21:50 message_handler_orf_token(4187):14: install seq 0 aru 0 high seq received 0
 debug Sep 28 20:21:50 message_handler_orf_token(4206):14: retrans flag count 4 token aru 0 install seq 0 aru 0 0
 debug Sep 28 20:21:50 old_ring_state_reset(1621):14: Resetting old ring state
 debug Sep 28 20:21:50 deliver_messages_from_recovery_to_regular(1852):14: recovery to regular 1-0
 trace Sep 28 20:21:50 memb_state_operational_enter(1943):14: Delivering to app 1 to 0
 debug Sep 28 20:21:50 totempg_waiting_trans_ack_cb(286):14: waiting_trans_ack changed to 1
 debug Sep 28 20:21:50 memb_state_operational_enter(2128):14: entering OPERATIONAL state.
 notice Sep 28 20:21:50 memb_state_operational_enter(2134):14: A new membership (127.0.0.1:12) was formed. Members joined: 2130706433
 trace Sep 28 20:21:50 totemsrp_mcast(2547):14: mcasted message added to pending queue
 trace Sep 28 20:21:50 messages_deliver_to_app(4278):14: Delivering 0 to 2
 trace Sep 28 20:21:50 messages_deliver_to_app(4347):14: Delivering MCAST message with seq 1 to pending delivery queue
 trace Sep 28 20:21:50 messages_deliver_to_app(4347):14: Delivering MCAST message with seq 2 to pending delivery queue
 trace Sep 28 20:21:50 totemsrp_mcast(2547):14: mcasted message added to pending queue
 trace Sep 28 20:21:50 messages_deliver_to_app(4278):14: Delivering 2 to 3
 trace Sep 28 20:21:50 messages_deliver_to_app(4347):14: Delivering MCAST message with seq 3 to pending delivery queue
 trace Sep 28 20:21:50 totemsrp_mcast(2547):14: mcasted message added to pending queue
 trace Sep 28 20:21:50 totemsrp_mcast(2547):14: mcasted message added to pending queue
 trace Sep 28 20:21:50 messages_free(2676):14: releasing messages up to and including 2
 trace Sep 28 20:21:50 messages_deliver_to_app(4278):14: Delivering 3 to 5
 trace Sep 28 20:21:50 messages_deliver_to_app(4347):14: Delivering MCAST message with seq 4 to pending delivery queue
 trace Sep 28 20:21:50 messages_deliver_to_app(4347):14: Delivering MCAST message with seq 5 to pending delivery queue
 trace Sep 28 20:21:50 totemsrp_mcast(2547):14: mcasted message added to pending queue
 trace Sep 28 20:21:50 messages_free(2676):14: releasing messages up to and including 3
 trace Sep 28 20:21:50 messages_deliver_to_app(4278):14: Delivering 5 to 6
 trace Sep 28 20:21:50 messages_deliver_to_app(4347):14: Delivering MCAST message with seq 6 to pending delivery queue
 debug Sep 28 20:21:50 totempg_waiting_trans_ack_cb(286):14: waiting_trans_ack changed to 0
 trace Sep 28 20:21:50 messages_free(2676):14: releasing messages up to and including 5
 trace Sep 28 20:21:50 messages_free(2676):14: releasing messages up to and including 6
 trace Sep 28 20:22:03 qb_loop_poll_add(368):9: grown poll array to 10 for FD 18
 debug Sep 28 20:22:03 handle_new_connection(647):9: IPC credentials authenticated (3202-3255-18)
 debug Sep 28 20:22:03 qb_ipcs_shm_connect(285):9: connecting to client [3255]
 debug Sep 28 20:22:03 qb_rb_open_2(238):9: shm size:1048589; real_size:1052672; rb->word_size:263168
 debug Sep 28 20:22:03 qb_rb_open_2(238):9: shm size:1048589; real_size:1052672; rb->word_size:263168
 debug Sep 28 20:22:03 qb_rb_open_2(238):9: shm size:1048589; real_size:1052672; rb->word_size:263168
 trace Sep 28 20:22:03 qb_loop_poll_add(368):9: grown poll array to 11 for FD 18
 debug Sep 28 20:22:03 qb_ipcs_dispatch_connection_request(759):9: HUP conn (3202-3255-18)
 debug Sep 28 20:22:03 qb_ipcs_disconnect(606):9: qb_ipcs_disconnect(3202-3255-18) state:2
 trace Sep 28 20:22:03 qb_rb_close(290):9: ENTERING qb_rb_close()
 debug Sep 28 20:22:03 qb_rb_close_helper(337):9: Free'ing ringbuffer: /dev/shm/qb-cmap-response-3202-3255-18-header
 trace Sep 28 20:22:03 my_posix_sem_destroy(91):9: ENTERING my_posix_sem_destroy()
 trace Sep 28 20:22:03 qb_rb_close(290):9: ENTERING qb_rb_close()
 debug Sep 28 20:22:03 qb_rb_close_helper(337):9: Free'ing ringbuffer: /dev/shm/qb-cmap-event-3202-3255-18-header
 trace Sep 28 20:22:03 my_posix_sem_destroy(91):9: ENTERING my_posix_sem_destroy()
 trace Sep 28 20:22:03 qb_rb_close(290):9: ENTERING qb_rb_close()
 debug Sep 28 20:22:03 qb_rb_close_helper(337):9: Free'ing ringbuffer: /dev/shm/qb-cmap-request-3202-3255-18-header
 trace Sep 28 20:22:03 my_posix_sem_destroy(91):9: ENTERING my_posix_sem_destroy()
 debug Sep 28 20:22:03 handle_new_connection(647):9: IPC credentials authenticated (3202-3257-18)
 debug Sep 28 20:22:03 qb_ipcs_shm_connect(285):9: connecting to client [3257]
 debug Sep 28 20:22:03 qb_rb_open_2(238):9: shm size:1048589; real_size:1052672; rb->word_size:263168
 debug Sep 28 20:22:03 qb_rb_open_2(238):9: shm size:1048589; real_size:1052672; rb->word_size:263168
 debug Sep 28 20:22:03 qb_rb_open_2(238):9: shm size:1048589; real_size:1052672; rb->word_size:263168
 ERROR: qb_rb_chunk_read failed: Connection timed out
 [trace] ENTERING qb_rb_close()
 [debug] Free'ing ringbuffer: /dev/shm/qb-create_from_file-header

 Current results:

 $ sudo corosync-blackbox
 /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found

[Where problems could occur]

 The reverse dependencies of the B-D introduced has been analized:

 - It only affects to corosync source:

  $ apt rdepends libqb-dev
  libqb-dev
  Reverse Depends:
    Depends: libcorosync-common-dev
    Depends: libcorosync-common-dev
    Depends: libcorosync-common-dev

 - It's present in Bionic:

  ubuntu@bionic-corosync-sysv:/etc/init.d$ apt-cache policy libqb-dev
  libqb-dev:
  Installed: 1.0.1-1ubuntu1
  Candidate: 1.0.1-1ubuntu1
  Version table:
  *** 1.0.1-1ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

  ubuntu@bionic-corosync-sysv:/etc/init.d$ apt depends libqb-dev
  libqb-dev
  PreDepends: dpkg (>= 1.17.14)
  Depends: libqb0 (= 1.0.1-1ubuntu1)
  Depends: libc6 (>= 2.3.4)
  Suggests: libqb-doc

  No other packages will be affected by this if a libqb-dev removal occurs.

[Other Info]

  This solution follows the example of the same bug fixed in Focal at https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622 .

[Original Description]
-----------------------------------

[Environment]

Ubuntu Xenial 16.04
Amd64

[Test Case]

1) sudo apt-get install corosync
2) sudo corosync-blackbox.

root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep black
/usr/bin/corosync-blackbox

Expected results: corosync-blackbox runs OK.

Current results:

$ sudo corosync-blackbox
/usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found

[Impact]

 * Cannot run corosync-blackbox

[Regression Potential]

* None identified.

[Fix]
Make the package dependant of libqb-dev

root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L libqb-dev | grep qb-bl
/usr/sbin/qb-blackbox

See original description

Related branches

~mirespace/ubuntu/+source/corosync:sru-corosync-bionic-lp1677684-lp1437359
Utkarsh Gupta (community): Approve
Athos Ribeiro: Pending requested
Diff: 47 lines (+16/-1)
3 files modified
debian/changelog (+12/-0)
debian/control (+3/-1)
debian/libtotem-pg5.symbols (+1/-0)
~mirespace/ubuntu/+source/corosync:sru-corosync-bionic-lp1677684-lp1437359
Athos Ribeiro (community): Approve
Ubuntu Core Development Team: Pending requested
Diff: 47 lines (+16/-1)
3 files modified
debian/changelog (+12/-0)
debian/control (+3/-1)
debian/libtotem-pg5.symbols (+1/-0)
~rafaeldtinoco/ubuntu/+source/corosync:lp1869622-focal
Christian Ehrhardt  (community): Approve
Canonical Server Core Reviewers: Pending requested
Canonical Server: Pending requested
Diff: 971 lines (+823/-2)
22 files modified
debian/changelog (+30/-0)
debian/control (+3/-1)
debian/corosync-notifyd.init (+0/-1)
debian/patches/series (+19/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-09f6d34a-logconfig-Remove-double-free-of-value.patch (+25/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-0c118d8f-totemknet-Check-result-of-fcntl-O_NONBLOCK-call.patch (+32/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-0c16442f-votequorum-Change-check-of-expected_votes.patch (+51/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-1fb095b0-notifyd-Check-cmap_track_add-result.patch (+50/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-29109683-totemknet-Assert-strcpy-length.patch (+44/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-35c312f8-votequorum-Assert-copied-strings-length.patch (+38/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-380b744e-totemknet-Don-t-mix-corosync-and-knet-error-codes.patch (+52/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-56ee8503-quorumtool-Assert-copied-string-length.patch (+25/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-5f543465-quorumtool-exit-on-invalid-expected-votes.patch (+33/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-624b6a47-stats-Assert-value_len-when-value-is-needed.patch (+26/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-74eed54a-sync-Assert-sync_callbacks.name-length.patch (+27/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-89b0d62f-stats-Check-return-code-of-stats_map_get.patch (+26/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-8ce65bf9-votequorum-Reflect-runtime-change-of-2Node-to-WFA.patch (+80/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-8ff7760c-cmapctl-Free-bin_value-on-error.patch (+30/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-a24cbad5-totemconfig-Initialize-warnings-variable.patch (+26/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-c631951e-icmap-icmap_init_r-leaks-if-trie_create-fails.patch (+32/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-ca320bea-votequorum-set-wfa-status-only-on-startup.patch (+67/-0)
debian/patches/ubuntu-v3.0.3-fixes/lp1869622-efe48120-totemconfig-Free-leaks-found-by-coverity.patch (+107/-0)
Jorge Niedbalski (niedbalski)
tags: added: sts
description: updated
Jorge Niedbalski (niedbalski)
tags: added: sts-sponsor
removed: sts
Changed in corosync (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Jorge Niedbalski (niedbalski)
Changed in corosync (Ubuntu Trusty):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Jorge Niedbalski (niedbalski)
Changed in corosync (Ubuntu Xenial):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Jorge Niedbalski (niedbalski)
Jorge Niedbalski (niedbalski)
description: updated
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

This is a bit too much "nobody cares on yakkety" as after the fix it will appear as regression X->Y upgrades. Yet the fix should be just the same, but sponsors should mind that.
Jorge would you ack that the same should go to Yakkety or are there reasons not to be seen too obviously that speaks against that?

Also I see that >=Xenial changes depend on libqb-dev >=0.12, but Trusty not.
Trusty would have 0.16.0.real-1ubuntu5 so it could have the >=0.12 as well which makes me wonder even more why >=0.12 actually?

The issue is simple enough I don't see other reasons to not sponsor, but those two points should be clarified/fixed before one is doing so.

Changed in corosync (Ubuntu Yakkety):
assignee: nobody → Jorge Niedbalski (niedbalski)
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Just checked that it applies to Yakkety as I assumed, nominating for that as well.

Changed in corosync (Ubuntu Yakkety):
status: New → Confirmed
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Checked that libqb-dev is in main back to Trusty and it is, so it would not be an unexpected component mismatch.

Jorge Niedbalski (niedbalski)
Changed in corosync (Ubuntu Yakkety):
status: Confirmed → In Progress
importance: Undecided → Medium
Revision history for this message
Jorge Niedbalski (niedbalski) wrote :

Hello Christian,

I've attached the updated debdiff for trusty (checking for libqb-dev >= 0.12) as well as the requested Yakkety debdiff.

Thanks for looking into this.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thanks already Jorge,
still would you mind explaining why it is (>= 0.12) ?

Especially since:
$ rmadison libqb-dev
 libqb-dev | 0.16.0.real-1ubuntu3 | trusty | amd64, arm64, armhf, i386, powerpc, ppc64el
 libqb-dev | 0.16.0.real-1ubuntu5 | trusty-updates | amd64, arm64, armhf, i386, powerpc, ppc64el
 libqb-dev | 0.17.0-2ubuntu1 | vivid | amd64, arm64, armhf, i386, powerpc, ppc64el
 libqb-dev | 0.17.2.real-6ubuntu1 | xenial | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 libqb-dev | 1.0-1ubuntu1 | yakkety | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 libqb-dev | 1.0.1-1ubuntu1 | zesty | amd64, arm64, armhf, i386, ppc64el, s390x

Once that is settled it can either be dropped (I'm sure you had a reason, but if not then why not without the version qualifier), or more likely be sponsored then.

Also we are rather low (or in Y even without) Delta, would you mind filing a bug against Debian and link it up here as well so that somewhen in the future (best would be next merge) we can drop this as a delta?

Revision history for this message
Jorge Niedbalski (niedbalski) wrote :

Hello Christian,

Thanks for looking into this, I just followed what the build dependency suggested
(>= 0.12) there is no strict dependency on it.

Do you want me to just leave it as libqb-dev or this is something you can
fix when merging?

Let me know how to proceed.

Thanks.

Revision history for this message
Jorge Niedbalski (niedbalski) wrote :
Revision history for this message
Jorge Niedbalski (niedbalski) wrote :
Revision history for this message
Jorge Niedbalski (niedbalski) wrote :
Revision history for this message
Jorge Niedbalski (niedbalski) wrote :
Eric Desrochers (slashd)
no longer affects: corosync (Ubuntu Yakkety)
Changed in corosync (Ubuntu Zesty):
assignee: nobody → Jorge Niedbalski (niedbalski)
importance: Undecided → Medium
Revision history for this message
Eric Desrochers (slashd) wrote :

Hi Jorge,

Is this also impacting corosyn in Debian upstream ?

If yes, before uploading the change to Artful and then Stable Release ...

Could you report the bug and submit the proposal patch to Debian upstream ?
or share the debian link (if already done)

Regards,
Eric

Revision history for this message
Simon Quigley (tsimonq2) wrote :

Reflecting Eric's comment in #16, there is nothing left to do for ~ubuntu-sponsors (a follow-up is needed) so I am unsubscribing ~ubuntu-sponsors. If this was done in error, please feel free to resubscribe ~ubuntu-sponsors.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Clearing dormant bugs and efforts on this seem to have died, I'm setting incomplete to all tasks for now.

Changed in corosync (Ubuntu):
status: In Progress → Incomplete
Changed in corosync (Ubuntu Trusty):
status: In Progress → Incomplete
Changed in corosync (Ubuntu Xenial):
status: In Progress → Incomplete
Changed in corosync (Ubuntu Zesty):
status: New → Incomplete
Dan Streetman (ddstreet)
tags: removed: sts-sponsor
Rafael David Tinoco (rafaeldtinoco)
Changed in corosync (Ubuntu Trusty):
assignee: Jorge Niedbalski (niedbalski) → nobody
Changed in corosync (Ubuntu):
assignee: Jorge Niedbalski (niedbalski) → nobody
Changed in corosync (Ubuntu Zesty):
assignee: Jorge Niedbalski (niedbalski) → nobody
Changed in corosync (Ubuntu Xenial):
assignee: Jorge Niedbalski (niedbalski) → nobody
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
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
Revision history for this message
Rafael David Tinoco (rafaeldtinoco) wrote :

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.

Revision history for this message
Rafael David Tinoco (rafaeldtinoco) wrote :

BUG: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622
PPA: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging

Changed in corosync (Ubuntu Focal):
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package corosync - 3.0.3-2ubuntu2

---------------
corosync (3.0.3-2ubuntu2) focal; urgency=medium

  [Jorge Niedbalski]
  * d/control: corosync binary depends on libqb-dev (LP: #1677684)

  [Rafael David Tinoco]
  * debian/corosync-notifyd.init: fix for 2 PIDFILEs declared (LP: #1437359)
  * Post v3.0.3 release fixes backported to Ubuntu (LP: #1869622)
    debian/patches/ubuntu-v3.0.3-fixes/:
    - lp1869622-09f6d34a-logconfig-Remove-double-free-of-value.patch
    - lp1869622-0c118d8f-totemknet-Check-result-of-fcntl-O_NONBLOCK-call.patch
    - lp1869622-0c16442f-votequorum-Change-check-of-expected_votes.patch
    - lp1869622-1fb095b0-notifyd-Check-cmap_track_add-result.patch
    - lp1869622-29109683-totemknet-Assert-strcpy-length.patch
    - lp1869622-35c312f8-votequorum-Assert-copied-strings-length.patch
    - lp1869622-380b744e-totemknet-Don-t-mix-corosync-and-knet-error-codes.patch
    - lp1869622-56ee8503-quorumtool-Assert-copied-string-length.patch
    - lp1869622-5f543465-quorumtool-exit-on-invalid-expected-votes.patch
    - lp1869622-624b6a47-stats-Assert-value_len-when-value-is-needed.patch
    - lp1869622-74eed54a-sync-Assert-sync_callbacks.name-length.patch
    - lp1869622-89b0d62f-stats-Check-return-code-of-stats_map_get.patch
    - lp1869622-8ce65bf9-votequorum-Reflect-runtime-change-of-2Node-to-WFA.patch
    - lp1869622-8ff7760c-cmapctl-Free-bin_value-on-error.patch
    - lp1869622-a24cbad5-totemconfig-Initialize-warnings-variable.patch
    - lp1869622-c631951e-icmap-icmap_init_r-leaks-if-trie_create-fails.patch
    - lp1869622-ca320bea-votequorum-set-wfa-status-only-on-startup.patch
    - lp1869622-efe48120-totemconfig-Free-leaks-found-by-coverity.patch

 -- Rafael David Tinoco <email address hidden> Sun, 29 Mar 2020 21:50:35 +0000

Changed in corosync (Ubuntu Focal):
status: In Progress → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote :

The Eoan Ermine has reached end of life, so this bug will not be fixed for that release

Changed in corosync (Ubuntu Eoan):
status: Confirmed → Won't Fix
Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote :

This is still impacting corosync version 2.4.3-0ubuntu1.2 present in Bionic.

Miriam España Acebal (mirespace)
Changed in corosync (Ubuntu Bionic):
assignee: nobody → Miriam España Acebal (mirespace)
status: Confirmed → In Progress
Revision history for this message
Miriam España Acebal (mirespace) wrote :

Xenial is now in Extended Security Maintenance (ESM) and this bug doesn't qualify for it, so this bug will not be fixed for that release.

Changed in corosync (Ubuntu Xenial):
status: Confirmed → Won't Fix
Miriam España Acebal (mirespace)
description: updated
Revision history for this message
Robie Basak (racb) wrote :

This upload seems to drop a Breaks but this isn't mentioned anywhere. Is this intentional?

Revision history for this message
Miriam España Acebal (mirespace) wrote (last edit ):

Not intentional at all... It seems derived from the not existence of that Breaks since Focal and removed when applied the same fix.

Searching where the Breaks was added (as it isn't present in Debian's versions), I found it added due to LP #1740892 for Xenial (2.3.5-3*),Artful and Bionic (same debian version for both, 2.4.2-3*), i.e :

corosync (2.4.2-3ubuntu1) bionic; urgency=medium

  * Properly restart corosync and pacemaker together (LP: #1740892)
    - d/rules: pass --restart-after-upgrade to dh_installinit
    - d/control: indicate this version breaks all older pacemaker, to
      force an upgrade of pacemaker.
    - d/corosync.postinst: if flagged to do so by pacemaker, start
      pacemaker on upgrade.
      + This can be dropped after bionic releases as long as the other
        changes are maintained.

 -- Nishanth Aravamudan <email address hidden> Tue, 30 Jan 2018 16:40:31 -0800
Available diffs

It seems that the right thing would be to recover the Breaks.

Revision history for this message
Robie Basak (racb) wrote : Please test proposed package

Hello Jorge, or anyone else affected,

Accepted corosync into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/corosync/2.4.3-0ubuntu1.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in corosync (Ubuntu Bionic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-bionic
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (corosync/2.4.3-0ubuntu1.3)

All autopkgtests for the newly accepted corosync (2.4.3-0ubuntu1.3) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

sbd/1.3.1-2 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#corosync

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote :
Download full text (11.2 KiB)

The package in bionic-proposed indeed fix the issue:

root@corosync-verification:~# dpkg -l | grep corosync
ii corosync 2.4.3-0ubuntu1.3 amd64 cluster engine daemon and utilities
ii libcorosync-common4:amd64 2.4.3-0ubuntu1.3 amd64 cluster engine common library
root@corosync-verification:~# corosync-blackbox
Dumping the contents of /var/lib/corosync/fdata
[debug] shm size:8392704; real_size:8392704; rb->word_size:2098176
[debug] read total of: 8392724
Ringbuffer:
 ->NORMAL
 ->write_pt [2866]
 ->read_pt [0]
 ->size [2098176 words]
 =>free [8381236 bytes]
 =>used [11464 bytes]
debug Nov 10 15:51:24 totempg_waiting_trans_ack_cb(286):14: waiting_trans_ack changed to 1
debug Nov 10 15:51:24 totemsrp_initialize(900):14: Token Timeout (3000 ms) retransmit timeout (294 ms)
debug Nov 10 15:51:24 totemsrp_initialize(903):14: token hold (225 ms) retransmits before loss (10 retrans)
debug Nov 10 15:51:24 totemsrp_initialize(910):14: join (50 ms) send_join (0 ms) consensus (3600 ms) merge (200 ms)
debug Nov 10 15:51:24 totemsrp_initialize(913):14: downcheck (1000 ms) fail to recv const (2500 msgs)
debug Nov 10 15:51:24 totemsrp_initialize(915):14: seqno unchanged const (30 rotations) Maximum network MTU 1401
debug Nov 10 15:51:24 totemsrp_initialize(919):14: window size per rotation (50 messages) maximum messages per rotation (17 messages)
debug Nov 10 15:51:24 totemsrp_initialize(923):14: missed count const (5 messages)
debug Nov 10 15:51:24 totemsrp_initialize(926):14: send threads (0 threads)
debug Nov 10 15:51:24 totemsrp_initialize(929):14: RRP token expired timeout (294 ms)
debug Nov 10 15:51:24 totemsrp_initialize(932):14: RRP token problem counter (2000 ms)
debug Nov 10 15:51:24 totemsrp_initialize(935):14: RRP threshold (10 problem count)
debug Nov 10 15:51:24 totemsrp_initialize(938):14: RRP multicast threshold (100 problem count)
debug Nov 10 15:51:24 totemsrp_initialize(941):14: RRP automatic recovery check timeout (1000 ms)
debug Nov 10 15:51:24 totemsrp_initialize(943):14: RRP mode set to none.
debug Nov 10 15:51:24 totemsrp_initialize(946):14: heartbeat_failures_allowed (0)
debug Nov 10 15:51:24 totemsrp_initialize(948):14: max_network_delay (50 ms)
debug Nov 10 15:51:24 totemsrp_initialize(971):14: HeartBeat is Disabled. To enable set heartbeat_failures_allowed > 0
notice Nov 10 15:51:24 totemnet_instance_initialize(248):14: Initializing transport (UDP/IP Multicast).
notice Nov 10 15:51:24 init_nss(688):14: Initializing transmit/receive security (NSS) crypto: none hash: none
debug Nov 10 15:51:24 totemudp_build_sockets_ip(923):14: Receive multicast socket recv buffer size (320000 bytes).
debug Nov 10 15:51:24 totemudp_build_sockets_ip(929):14: Transmit multicast socket send buffer size (320000 bytes).
debug Nov 10 15:51:24 totemudp_build_sockets_ip(935):14: Local receive multicast loop socket recv buffer size (320000 bytes).
debug Nov 10 15:51:24 totemudp_build_sockets_ip(941):14: Local transmit multicast loop socket send buffer size (320000 bytes).
trace Nov 10 15:51:24 qb_loop_poll_add(368):9: grown poll array ...

tags: added: verification-done verification-done-bionic
removed: verification-needed verification-needed-bionic
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package corosync - 2.4.3-0ubuntu1.3

---------------
corosync (2.4.3-0ubuntu1.3) bionic; urgency=medium

  [ Miriam España Acebal ]
  * d/libtotem-pg5.symbols: add a postfixed missing symbol,
    crypto_get_current_sec_header_size.

  [ Jorge Niedbalski ]
  * d/control: corosync binary depends on libqb-dev.
    (LP: #1677684)

 -- Miriam España Acebal <email address hidden> Tue, 28 Sep 2021 20:00:07 +0200

Changed in corosync (Ubuntu Bionic):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for corosync has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.