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
lo
A bit more investigation on this and I think I found what the differece is
at least. waagent is using camcontrol periphlist 3:1:0 to find devices,
and this has chnaged from placing the discs before the pass
devices to afterwards. So on an earlier version I get this:
root@joanna-may:/home/w
> The agent has just been updated in the ports tree a few days ago, can you
> try the new version?
Just checked and the version in ports is 2.2.8, and I am running 2.2.11
-pete.
..
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/m
I'm not using the version from ports, I am using the latest oone
directly from the git repository as its the most recent there is.
That is version 2.2.11.1.
( The images supplied by Microsoft came with waagent isnatlled which was
more recent tahn ports, so I never used the prt (the one time I t
On Fri, May 26, 2017 at 01:26:46PM +0100, Pete French wrote:
> Have upgraded one of my Azure boxes to 11.1-PRERELEASE yesterday, and I
> now find the below backtrace from waagent when it tries to attach
> the resource disc. It looks as if it is finding 'pass1' as the device,
> when it should be fin
Have upgraded one of my Azure boxes to 11.1-PRERELEASE yesterday, and I
now find the below backtrace from waagent when it tries to attach
the resource disc. It looks as if it is finding 'pass1' as the device,
when it should be finding 'da1'. As the waagents hasnt changed I am
wondering what might h
