On Wed, Jun 07, 2017 at 06:00:32PM -0000, ChristianEhrhardt wrote:
> I just checked this happens up to artful but I wonder.
> Is anybody using the 2.0 at all?
> I mean it fails right away.
>
> There is also the non 2.0 agent in /usr/sbin/waagent
> Is that what people use?
>
> Do they use the packaged version at all or something that is bundled in
> the image build process?
waagent is used at boot; it may use Python's internal import mechanism
to pull in waagent2.0, but I don't believe it ever does that (else we'd
see this during normal operation, which we don't).
> There are too many uncertainties that at least I don't understand.
> I'm subscribing Dan for his experience around the cloud and cloud image
> handling.
>
> @Dan - do you know how this is supposed to work and who maintains it
> usually - I saw some uploads from foundations, but thought you'd be the
> best start to sort it out?
I think the problem is that waagent2.0 is installed with a shebang that
points at Python 3; it is written only to work with Python 2.
** Changed in: walinuxagent (Ubuntu)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640859
Title:
waagent2.0 stacktraces when invoked
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1640859/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
