From muks@isc.org Fri May 26 10:38:26 2017 MIME-Version: 1.0 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 Content-Disposition: inline content-type: text/plain; charset="utf-8" Message-ID: <20170526103815.GA22789@jurassic> Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by bugs.isc.org (Postfix) with ESMTP id 7B33A71B5A8 for ; Fri, 26 May 2017 10:38:26 +0000 (UTC) Received: from mail.banu.com (mail.banu.com [46.4.129.225]) by mx.pao1.isc.org (Postfix) with ESMTP id 12E5B3493AC for ; Fri, 26 May 2017 10:38:24 +0000 (UTC) Received: from jurassic (unknown [115.118.50.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id E8EE756A02D7; Fri, 26 May 2017 10:38:20 +0000 (GMT) Delivered-To: bind9-bugs@bugs.isc.org Subject: mkeys system test fails User-Agent: Mutt/1.8.0 (2017-02-23) Return-Path: X-Original-To: bind9-bugs@bugs.isc.org Date: Fri, 26 May 2017 16:08:15 +0530 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx.pao1.isc.org To: bind9-bugs@isc.org From: "Mukund Sivaraman" X-RT-Original-Encoding: ascii X-RT-Interface: Email Content-Length: 2527 mkeys system test on master consistently fails for me: [muks@jurassic system]$ sh ./run.sh mkeys S:mkeys:Fri May 26 16:05:27 IST 2017 T:mkeys:1:A A:System test mkeys I: check for signed record (1) I: check positive validation with valid trust anchor (2) I: check positive validation using delv (3) I: check for failed validation due to wrong key in managed-keys (4) I: check new trust anchor can be added (5) I: ns2 refreshing managed keys for '_default' I: check new trust anchor can't be added with bad initial key (6) I: ns3 refreshing managed keys for '_default' I: remove untrusted standby key, check timer restarts (7) I: ns2 refreshing managed keys for '_default' I: restore untrusted standby key, revoke original key (8) I: ns2 refreshing managed keys for '_default' I:failed I: refresh managed-keys, ensure same result (9) I: ns2 refreshing managed keys for '_default' I: restore revoked key, ensure same result (10) I: ns2 refreshing managed keys for '_default' I: reinitialize trust anchors I: check that standby key is now trusted (11) I: revoke original key, add new standby (12) I: ns2 refreshing managed keys for '_default' I: revoke standby before it is trusted (13) I: ns2 refreshing managed keys for '_default' I: ns2 refreshing managed keys for '_default' I: wait 30 seconds for key add/remove holddowns to expire (14) I: ns2 refreshing managed keys for '_default' I: revoke all keys, confirm roll to insecure (15) I: ns2 refreshing managed keys for '_default' I: check for insecure response (16) I: reset the root server I: reinitialize trust anchors I: check positive validation (17) I: revoke key with bad signature, check revocation is ignored (18) I: ns1 zone reload queued I: ns2 refreshing managed keys for '_default' I: check validation fails with bad DNSKEY rrset (19) I: restore DNSKEY rrset, check validation succeeds again (20) I: ns1 zone reload queued I: ns2 refreshing managed keys for '_default' I: reset the root server with no keys, check for minimal update (21) I: ns2 refreshing managed keys for '_default' I: reset the root server with no signatures, check for minimal update (22) I: ns2 refreshing managed keys for '_default' I: restore root server, check validation succeeds again (23) I: ns1 zone reload successful I: ns2 refreshing managed keys for '_default' I: check that trust-anchor-telemetry queries are logged (24) I: check that trust-anchor-telemetry queries are received (25) I:exit status: 1 R:FAIL E:mkeys:Fri May 26 16:07:12 IST 2017 [muks@jurassic system]$ Mukund