waagent2.0 stacktraces when invoked

Bug #1640859 reported by Ryan Harper on 2016-11-10
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
walinuxagent (Ubuntu)
Undecided
Łukasz Zemczak

Bug Description

ubuntu@xenial-161110-1527:~$ sudo apt-cache policy walinuxagent
walinuxagent:
  Installed: 2.1.3-0ubuntu4.2
  Candidate: 2.1.3-0ubuntu4.2
  Version table:
 *** 2.1.3-0ubuntu4.2 500
        500 http://azure.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.1.3-0ubuntu4 500
        500 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

ubuntu@xenial-161110-1527:~$ waagent2.0
  File "/usr/sbin/waagent2.0", line 191
    self.shadow_file_mode=0600
                             ^
SyntaxError: invalid token
ubuntu@xenial-161110-1527:~$ dpkg -S `which waagent2.0`
walinuxagent: /usr/sbin/waagent2.0

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: walinuxagent 2.1.3-0ubuntu4.2
ProcVersionSignature: User Name 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Nov 10 16:29:54 2016
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: walinuxagent
UpgradeStatus: No upgrade log present (probably fresh install)

Ryan Harper (raharper) 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?

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?

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: nobody → Łukasz Zemczak (sil2100)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers