Public bug reported:
The client machine is a Karmic koala that DOES ssh forwarding ok against
othe servers (mostly fedoras or Ubuntu Hardy desktops) [The problem IS
NOT ON THE client side, as it does the jobs correctly against other
servers]
The failing (ssh) server machine is a Ubuntu Hardy LTS
Ah, something a forgot to mention.
I compared a ssh -vvv session against a working fedora server and could
not see any difference except for that in the hardy server, once the ssh
connection is established, when I do gedit (or xhost +) I just get the
error 'can't open display' and no debug info
X11Forwarding is ON:
...
X11Forwarding yes
X11DisplayOffset 10
...
And xauth is installed, when I connect (the first time or after removing
.Xauthority) I get:
/usr/bin/X11/xauth: creating new authority file /home/admin/.Xauthority
The Display variable is OK:
$ echo $DISPLAY
localhost:10.0
# Package generated configuration file
# See the sshd(8) manpage for details
# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
Openssh forwards X sessions correctly after the /etc/hosts is fixed with
a correct localhost IP (127.0.0.1 instead of 127.0.1.1)
** Changed in: openssh (Ubuntu)
Status: Incomplete = Invalid
--
Hardy 8.04.3 openssh does not forward X11 always cannot open display
Public bug reported:
I had set up in Ubuntu 9.04 a network config fixed at
/etc/netwrking/interfaces in a PC acting as a home printer server SO
that users just have to switch ON the machine to access the server
printer and shared folders but do not need to log in as any user.
All WAS working
Public bug reported:
After some karmic update (I guess) my eee 901 won't start on its own, as
it waits (for ever) for the user to select some boot option.This is
quite annoying as it was working ok before.
It could not be solved by touching the /etc/default/grub options.
Maybe pushing GRUB2 on
Openssh forwards X sessions correctly after the /etc/hosts is fixed with
a correct localhost IP (127.0.0.1 instead of 127.0.1.1)
** Changed in: openssh (Ubuntu)
Status: Incomplete = Invalid
--
Hardy 8.04.3 openssh does not forward X11 always cannot open display
Confirmed. There is some kind of regression at NetworkManager on Karmic
that prevents it from releasing an interface configured at:
/etc/network/interfaces
The workarround for now is to remove the package network-manager (plus
its companions network-manager-gnome, ...-kde, etc) and configure
Apart from the bug itself I would like to ask why on earth is Network
Manager (NM) NOT DESIGNED to ALSO enable system-wide fixed networks
settings per interface?
NM is ok for most laptops, but when on a workstation or any other system
providing services to other machines NO becomes completely
Public bug reported:
The client machine is a Karmic koala that DOES ssh forwarding ok against
othe servers (mostly fedoras or Ubuntu Hardy desktops) [The problem IS
NOT ON THE client side, as it does the jobs correctly against other
servers]
The failing (ssh) server machine is a Ubuntu Hardy LTS
Ah, something a forgot to mention.
I compared a ssh -vvv session against a working fedora server and could
not see any difference except for that in the hardy server, once the ssh
connection is established, when I do gedit (or xhost +) I just get the
error 'can't open display' and no debug info
# Package generated configuration file
# See the sshd(8) manpage for details
# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
X11Forwarding is ON:
...
X11Forwarding yes
X11DisplayOffset 10
...
And xauth is installed, when I connect (the first time or after removing
.Xauthority) I get:
/usr/bin/X11/xauth: creating new authority file /home/admin/.Xauthority
The Display variable is OK:
$ echo $DISPLAY
localhost:10.0
Same for me on a supposed to be stable release of a LTS version.
--
gnome-panel will not autostart on lucid
https://bugs.launchpad.net/bugs/542343
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It turned out to be a very strange problem with our network.
You could browse the web but you couldn't download big files (more than
5 or 10mb) cause they got corrupted.
That is the cause of:
bzip2: Data integrity error when decompressing.
Input file = (stdin), output file = (stdout)
It is
I believe Lukazs already fixed most issues:
$ lintian
E: walinuxagent changes: bad-distribution-in-changes-file zesty
W: walinuxagent source: out-of-date-standards-version 3.9.7 (current is 3.9.8)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The maintainer is being handled on a separate bug:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1657528
** Changed in: walinuxagent (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Document with testing details
** Attachment added: "TestingyakketybootspeedregressionvsxenialinEC2.odt"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1629797/+attachment/4753367/+files/TestingyakketybootspeedregressionvsxenialinEC2.odt
--
You received this bug notification
Public bug reported:
Seems yakkety is consistently taking 2-3 minutes to boot on EC2,
compared to the ~30 seconds of the first boot and ~10 seconds thereafter
in xenial.
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Assignee: Dan Watkins (daniel-thewatkins)
Status: New
Public bug reported:
In my tests the /etc/update-manager/release-upgrades.d directory does not seem
to be taken into account for overriding the configuration at:
/etc/update-manager/release-upgrades
Testing on trusty, I have tried this file:
[DEFAULT]
# Override prompting behavior to 'never'
** Changed in: walinuxagent (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603581
Title:
Azure Linux Agent (WALA) 2.1.5 Released
To manage
Above debdiff code can be found in PPA:
https://launchpad.net/~josvaz/+archive/ubuntu/wala-2.1.5-xenial-backport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603581
Title:
Azure Linux Agent
*** This bug is a duplicate of bug 1603581 ***
https://bugs.launchpad.net/bugs/1603581
** This bug has been marked a duplicate of bug 1603581
Azure Linux Agent (WALA) 2.1.5 Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is the debdiff from xenial, it has been tested from a PPA using
both given regression cases.
** Patch added: "lp-1604423.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/walinuxagent/+bug/1603581/+attachment/4774030/+files/lp-1604423.debdiff
** Description changed:
- As
Debdiff updated to point to this public SRU bug
Again, tested from a PPA using both given regression cases.
** Patch added: "lp-1604423.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/walinuxagent/+bug/1603581/+attachment/4774037/+files/lp-1604423.debdiff
--
You received this bug
Trusty backport PPA updated to:
https://launchpad.net/~josvaz/+archive/ubuntu/trusty-wala-backport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603581
Title:
Azure Linux Agent (WALA) 2.1.5
** Description changed:
[Original Description]
As discussed in an email, the Linux Agent (WALA) version 2.1.5 has now
been signed off and is in Master now.
Please find the details below of some of items built into this release :
https://github.com/Azure/WALinuxAgent/releases
** Changed in: walinuxagent (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638960
Title:
[SRU] Update walinuxagent to 2.1.5
To manage
** Changed in: walinuxagent (Ubuntu Xenial)
Assignee: Dan Watkins (daniel-thewatkins) => Jose L. VG (josvaz)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603581
Title:
Azure Linux Ag
Trusty debdiff from current trusty walinuxagent 2.1.3
The proposed package comes from the yakkety walinuxagent 2.1.5 package
with no other chnages that the last changelog entry.
** Patch added: "lp-1603581-trusty.debdiff"
Walinux agent 2.1.5 is abilable for testing in this public test images:
Xenial:
https://josvaz.blob.core.windows.net/shared/Ubuntu-xenial-16_04-LTS-amd64-server-20161020-wala2.1.5-os-2016-11-03-644FF1D6.vhd
And also now for Trusty here:
Xenial backput of walinuxagent 2.1.5 has passed the SRU tests according to:
https://wiki.ubuntu.com/walinuxagentUpdates
SRU Test Cases
These are automated tests:
1.) Build new cloud image with -purposed package
2.) Boot instance
3.) Confirm that instance provisioned
4.) Run standard tests and
Public bug reported:
[Impact]
Version 2.1.5 introduced goal state processing extension, multi-nic
improvements & several bug fixes:
https://github.com/Azure/WALinuxAgent/releases
[Test case 1]: Upgrade testing
1.) Launch instance on Azure
2.) Upgrade walinuxagent from -proposed
3.) Confirm that
The attached debdiff has been tested from a PPA using both given
regression cases.
** Patch added: "lp-1604423.debdiff"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1638960/+attachment/4771880/+files/lp-1604423.debdiff
--
You received this bug notification because you are a
Patch diff against the wrong version (I generated from yakkety package)
This is the debdiff from xenial, and again has been tested from a PPA
using both given regression cases.
** Patch added: "lp-1604423.debdiff"
** Patch removed: "lp-1604423.debdiff"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1638960/+attachment/4771880/+files/lp-1604423.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Walinuxagent 2.1.5 is ready for testing on this Xenial public image:
https://josvaz.blob.core.windows.net/shared/Ubuntu-xenial-16_04-LTS-amd64-server-20161020-wala2.1.5-os-2016-11-03-644FF1D6.vhd
We have done some tests on our own and we have started the SRU process
to incldue the package in
** Changed in: walinuxagent (Ubuntu Trusty)
Status: New => In Progress
** Changed in: walinuxagent (Ubuntu Trusty)
Assignee: Dan Watkins (daniel-thewatkins) => Jose L. VG (josvaz)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Marked verification-failed-trusty as this package version should not be
released for trusty, instead we need to upload a new one with auto-
update on.
** Tags added: verification-failed-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Our SRU tests passed but I will not mark as verified. We are to enable
wala 2.1.5 autoupdates BEFORE we release 2.1.5 for trusty, so I need to
update the package and re-upload to proposed.
For xenial we already released a 2.1.5, so will need to do a full SRU
again with autoupdates on (same as for
Actually marked it verification-done-trusty. Talking to Dan it was clear
that it will be less work at this point to get a trusty wala 2.1.5 out
now and then diff the autoupdate on against it on the next SRU cycle.
** Tags removed: verification-failed-trusty
** Tags added: verification-done-trusty
default is enabled
AutoUpdate.Enabled=n
AutoUpdate.GAFamily=Prod
"
After some discussion we have agreed Ubuntu packages for yakkety, xenial
& trusty should enable AutoUpdate.
** Affects: walinuxagent (Ubuntu)
Importance: Undecided
Assignee: Jose L. VG (josvaz)
Status
See also recent release work of walinuxagent 2.1.5 at:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1603581
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650522
Title:
walinuxagent
This is now fix released, autoupdate neablement will happen on a separate
tracking bug:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1650522
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: walinuxagent (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650522
Title:
walinuxagent 2.1.5 needs to have AutoUpdate On
To manage
Hi Daniel,
I also had this problem earlier today, the source page was there but not
the binary.
Dimitri & Steve fixed a dependency issue for me and I got the newly
built amd64 package from proposed as expected. I am trying it on a test
image as we speak.
Check out again, if you can't still get
Hi Daniel,
It is difficult to quantify, but we decided to go on and release wala
2.1.5-0ubuntu4~14.04.0 cause:
- It had actually passed verification already.
- It introduced a delta we already verified and tested. If we threw away the
package at this point next SRU will have to verify both the
Trusty debdiff from current trusty walinuxagent 2.0.16
The proposed package comes from the yakkety walinuxagent 2.1.5 package
with oine change:
[ Steve Langasek ]
* Drop systemctl reference from ephemeral-disk-warning.conf, this command
doesn't exist in trusty.
** Patch added:
walinuxagent trusty backport test image has been refreshed:
https://josvaz.blob.core.windows.net/shared/Ubuntu_DAILY_BUILD-trusty-14_04_5-LTS-amd64-server-20161130-wala-1480614674-en-us-30GB
We aim for this image to enter proposed today as it has passed our
manual tests.
Can Azure test this
We have tested a new package version for yakkety both installing manually and
in a test image:
https://josvaz.blob.core.windows.net/shared/Ubuntu_DAILY_BUILD-yakkety-16_10-amd64-server-20161214-wala215-autoupdate-1482143205-en-us-30GB
Please, do test the above image from the Azure side as well.
yakkety debdiff from latest updates to the proposed change
** Patch added: "lp-1650522.debdiff"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1650522/+attachment/4794034/+files/lp-1650522.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
+ [Original Description]
+
From Daniel Sol:
"
I was working on one of my 16.10 servers today and I was trying to get
the Linux agent to take it latest goal state update and it was not
doing anything. I looked in ./etc/waagent.conf and found it was disabled:
xenial debdiff from latest from updates to the proposed change
** Patch added: "lp-1650522-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1650522/+attachment/4794044/+files/lp-1650522-xenial.debdiff
--
You received this bug notification because you are a member
trusty debdiff from latest from updates to the proposed change
** Patch added: "lp-1650522-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1650522/+attachment/4794047/+files/lp-1650522-trusty.debdiff
--
You received this bug notification because you are a member
zesty debdiff
** Patch added: "lp-1650522-zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1650522/+attachment/4794035/+files/lp-1650522-zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
removed the first yakkety attemp, will upload debdiff dor zesty now
before yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650522
Title:
walinuxagent 2.1.5 needs to have AutoUpdate On
To
yakkety debdiff from latest from updates to the proposed change
** Patch added: "lp-1650522-yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1650522/+attachment/4794036/+files/lp-1650522-yakkety.debdiff
--
You received this bug notification because you are a
Following https://wiki.ubuntu.com/walinuxagentUpdates CPC automated SRU
testing for proposed walinuxagent 2.2.6 has passed for all three suites;
yakkety, xenial & trusty.
These are the images with the proposed packages that have been tested:
yakkety
Following https://wiki.ubuntu.com/walinuxagentUpdates CPC automated SRU
testing for proposed walinuxagent 2.2.6 has passed for all three suites;
yakkety, xenial & trusty.
These are the images with the proposed packages that have been tested:
yakkety
Links to the test images with walinuxagent 2.2.6 in proposed for Azure
to test:
yakkety
https://josvaz.blob.core.windows.net/shared/Ubuntu_DAILY_BUILD-yakkety-16_10-amd64-server-20170320-wala226-proposed-1490097291-en-us-30GB
xenial
Public bug reported:
bsdtar fails on yakkety. It was discovered while using vagrant, which
could not unpack images due to this issues. The workaround was to use
tar instead (by changing bsdtar into a link to tar), but bsdtar is still
broken.
$ bsdtar
bsdtar: symbol lookup error: bsdtar:
So the missing symbol is there, the problem is that it was not finding
it for my native yakkety environment:
$ nm -D /usr/bin/bsdtar | grep archive_read_add_passphrase
U archive_read_add_passphrase
$ nm -D /usr/lib/x86_64-linux-gnu/libarchive.so.13 |grep
conjure-up snap version was breaking bsdtar!
$ sudo ldconfig -p |grep libarchive
libarchive.so.13 (libc6,x86-64) =>
/snap/conjure-up/140/usr/lib/x86_64-linux-gnu/libarchive.so.13
libarchive.so.13 (libc6,x86-64) =>
/usr/lib/x86_64-linux-gnu/libarchive.so.13
$ sudo snap remove
Something is strange here. It seems to work on a LXD container:
$ lxc start y
$ lxc exec y bash
root@y:~# bsdtar
The program 'bsdtar' is currently not installed. You can install it by typing:
apt install bsdtar
root@y:~# apt install bsdtar
Reading package lists... Done
Building dependency tree
As Azure confirmed they passed their tests too I will be marking this
verified-done now.
** Tags added: verification-done
** Tags removed: verification-done
** Tags added: verification-done-trusty verification-done-xenial
verification-done-yakkety
--
You received this bug notification because
In some occasions it can need to go before cloud-init.
That happen recently to fix a bug for RAX:
https://bugs.launchpad.net/cpc-rax/+bug/1657223
xe-deamon.service in that case had to go before nova-agent.service which
in turn needed to go before ANYTHING expected the network to be
configured,
I'd vote for the "DefaultDependencies=no" option as per experience with this
RAX issue:
https://bugs.launchpad.net/cpc-rax/+bug/1657223
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669755
Title:
68 matches
Mail list logo
