From owner-freebsd-stable@freebsd.org  Thu Jun  1 09:37:29 2017
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9502BF6E31
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Thu,  1 Jun 2017 09:37:29 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3])
 by mx1.freebsd.org (Postfix) with ESMTP id D63C671886
 for <freebsd-stable@freebsd.org>; Thu,  1 Jun 2017 09:37:29 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: by mailman.ysv.freebsd.org (Postfix)
 id D28B8BF6E30; Thu,  1 Jun 2017 09:37:29 +0000 (UTC)
Delivered-To: stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2223BF6E2F
 for <stable@mailman.ysv.freebsd.org>; Thu,  1 Jun 2017 09:37:29 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 7E69C71885;
 Thu,  1 Jun 2017 09:37:29 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from dilbert.ingresso.co.uk ([2a02:b90:3002:411::6])
 by constantine.ingresso.co.uk with esmtpsa
 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD))
 (envelope-from <petefrench@ingresso.co.uk>)
 id 1dGMXm-000HrK-NH; Thu, 01 Jun 2017 09:37:26 +0000
Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.89
 (FreeBSD)) (envelope-from <petefrench@ingresso.co.uk>)
 id 1dGMXm-000682-JX; Thu, 01 Jun 2017 10:37:26 +0100
To: bapt@FreeBSD.org, petefrench@ingresso.co.uk, 
	petefrench@ingresso.co.uk
Subject: Re: 11.1-PRERELEASE, waagent crashes attaching reosurce disc in Azure
Cc: stable@freebsd.org
Message-Id: <E1dGMXm-000682-JX@dilbert.ingresso.co.uk>
From: Pete French <petefrench@ingresso.co.uk>
Date: Thu, 01 Jun 2017 10:37:26 +0100
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jun 2017 09:37:30 -0000

Just been through the azure python code - my intiial impressin was wrong, its
not the chnage to the periphlist output which is the issue. Instead
its the fact that a simple 'devlist' now puts the pass devices first in
the list, and the azure waagent uses the first listed device when it initially
looks for the device. A simple fix for this is to reject what that call
returns and then to drop back to using periphlist, nd this is what I have done,
but it would be nice to fix it properly.

What was the reason behind the chnage of ordering anyway ? Any script
which naiively parses the output of camcontrol devlist will hit a similar
issue potentially ? It's not exactly a bug, but...

-pete.