Opened 7 years ago

Closed 6 years ago

#2241 closed enhancement (wontfix)

version components?

Reported by: jreed Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: Unclassified Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: need plan or info Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


I upgraded a running version (from June 21) but didn't restart all, just did a "Auth shutdown" to restart a single component:

2012-09-06 07:48:24.569 DEBUG [] CC_GROUP_SEND sending message '{ "co
mmand": [ "get_module_spec", { "module_name": "data_sources" } ] }' to group 'Co
2012-09-06 07:48:24.569 DEBUG [] CC_GROUP_RECEIVE trying to receive a
2012-09-06 07:48:24.570 DEBUG [] CC_GROUP_RECEIVED message arrived ('
{ "from": "", "group": "ConfigManager", "instance":
 "*", "reply": 10, "seq": 214121, "to": "", "type"
: "send" }', '{ "result": [ 0, {  } ] }')
2012-09-06 07:48:24.591 FATAL [b10-auth.auth] AUTH_SERVER_FAILED server failed: 
module_name missing in {  }

I know it is not safe behaviour to do this with a development version after a big upgrade, but maybe we should have the components identify themselves or otherwise have some way to know what they are compatible with. So instead of confusing fatal error message it could say it is an incompatible version?


Change History (5)

comment:1 Changed 7 years ago by vorner

This has a drawback. We either spend nontrivial effort on determining which
versions are and aren't compatible, or simply say the only compatible ones are
from the same build. But then, it could have just worked in some cases, which
wouldn't be possible if we disallow them all.

comment:2 Changed 7 years ago by jelte

FYI, we *do* have a version element in the global configuration, but not in module-specific ones. But I don't think anything actually uses it. We could add that everywhere (with all the dynamic weirdness on how to resolve it), but perhaps we should take a similar approach to the one we took in sqlite3 version; upon make install, run a script to validate the existing configuration. On error, fail and provide some way to upgrade it.

comment:3 Changed 7 years ago by shane

  • Milestone New Tasks deleted

comment:4 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:5 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to bind10-old
Note: See TracTickets for help on using tickets.