Opened 7 years ago

Closed 5 years ago

#2455 closed defect (wontfix)

bind10 parent should not exit if b10-auth exits with fatal

Reported by: jreed Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: ~Boss of BIND (obsolete) Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: discuss Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description (last modified by jreed)

This is similar to #2393.

I reproduced by "execute init_authoritative_server" and "config commit". Due to bug #2457, b10-auth crashed. (It should not have. That is #2393.)

This ticket is so bind10 boss should not exit either.

Subtickets

Change History (8)

comment:1 Changed 7 years ago by jreed

  • Description modified (diff)

comment:2 follow-up: Changed 7 years ago by jinmei

I don't fully understand the "execute" magic, but isn't it the
expected behavior that the bind10 process dies if a "needed" component
fails to start? Or are you suggesting we should change this behavior?

comment:3 in reply to: ↑ 2 Changed 7 years ago by jreed

Replying to jinmei:

I don't fully understand the "execute" magic, but isn't it the
expected behavior that the bind10 process dies if a "needed" component
fails to start? Or are you suggesting we should change this behavior?

kind is set to "needed".

The guide documentation says: If it is set to “needed” and it fails at startup, the whole bind10 shuts down and exits with an error exit code. But if it fails some time later, it is just started again. If you set it to “core”, you indicate that the system is not usable without the component and if such component fails, the system shuts down no matter when the failure happened.

In my case, the system already was started and running (that is how I had access to cmdctl and cfgmgr). To shutdown after startup, it would set kind to "core".

comment:4 Changed 7 years ago by jreed

This is same as #1703 (nine months old).

comment:5 follow-up: Changed 7 years ago by shane

  • Milestone New Tasks deleted

Just to be clear, b10-auth crashed and the boss decided to exit for some reason?

comment:6 in reply to: ↑ 5 Changed 7 years ago by jreed

Replying to shane:

Just to be clear, b10-auth crashed and the boss decided to exit for some reason?

It is not about b10-auth crashing specifically. It is about a "needed" component failing so bind10 boss shuts down. It should not shut down (as documented).

comment:7 Changed 5 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:8 Changed 5 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check http://bundy-dns.de.

Closing ticket.

Note: See TracTickets for help on using tickets.