date:20151201

[Bug 349913] Re: sftp: cannot enter umlauts like ä, ö, ü

2015-12-01 Thread Ken Sharp

With 1:6.6p1-2ubuntu2.3 (Trusty) the alt-tab completion works, but the
character isn't echoed back.

sftp> get nave 
Fetching /tmp/naïve to naïve

Attempts to enter a character (AltGr+a for æ or AltGr+[+i for ï, for
example) simply results in an error beep, which is new but thoroughly
useless and a step backwards.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/349913

Title:
  sftp: cannot enter umlauts like ä, ö, ü

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/349913/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1521771] [NEW] init.d.mysql shutdown timeout value does not match init/mysql.conf value

2015-12-01 Thread Mark Stosberg

Public bug reported:

In `/etc/init/mysql.conf`, the configuration is set to wait 5 minutes
after a SIGTERM is issued before a SIGKILL is issued. The value was
intentionally set that high because sometimes the default of 5 seconds
wasn't long enough [1].

 1. https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/620441

The code used for this in the upstart script is:

   kill timeout 300

However the parallel change was not made to /etc/init.d/mysql  
It has the same logic, but waits only 10 seconds, like this:

```
killall -15 mysqld
server_down=
for i in 1 2 3 4 5 6 7 8 9 10; do
  sleep 1
  if mysqld_status check_dead nowarn; then server_down=1; break; fi
done
  if test -z "$server_down"; then killall -9 mysqld; fi
```

I would consider submitting a patch to change the timeout from 10
seconds to 300 in this script, but I can't believe spelling out the
numbers from 1 to 300 is the best way to do that, as the current code
counts to 10 like this.

I know that using upstart and the "service" command are the preferred
way to manage MySQL, but as long as the init.d script continues to be
shipped it should parallel the upstart script when possible.

This change matters to projects like ec2-consistent-shutdown, which
tries to shutdown MySQL cleanly across a number of linux variations. It
currently does that with a hardcoded reference to /etc/init.d/mysql,
which apparenty works, while I don't think the upstart syntax would be
as portable.  [2]

 2. https://github.com/alestic/ec2-consistent-snapshot/pull/68

** Affects: mysql-5.5 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.5 in Ubuntu.
https://bugs.launchpad.net/bugs/1521771

Title:
  init.d.mysql shutdown timeout value does not match init/mysql.conf
  value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1521771/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1521745] [NEW] sshd will fail to start or restart if non-default Port option is incorrectly put after a non-default ListenAddress

2015-12-01 Thread jhartr7

Public bug reported:

I have a system where the default listening port is changed for sshd,
done at the bottom of my sshd_config.  I recently changed the
ListenAddress from its default (unset, which listens on all interfaces)
to bind to a specific IP.  The resulting relevant snippet of my
sshd_config was:

ListenAddress my_ip_here
Port 12345

I then restarted ssh with /etc/init.d/ssh restart and found that ssh was
not listening.

Re-reading the manpage, I see this:

ListenAddress
 Specifies the local addresses sshd(8) should listen on.  The fol‐
 lowing forms may be used:

   ListenAddress host|IPv4_addr|IPv6_addr
   ListenAddress host|IPv4_addr:port
   ListenAddress [host|IPv6_addr]:port

 If port is not specified, sshd will listen on the address and all
 prior Port options specified.  The default is to listen on all
 local addresses.  Multiple ListenAddress options are permitted.
 Additionally, any Port options must precede this option for non-
 port qualified addresses.

On a hunch, I remove the Port line and simply change my relevant config
to:

ListenAddress my_ip_here:12345

sshd then restarted just fine.

In looking at the logs, I see:

Dec  1 11:40:26 jhart-laptop kernel: [1207947.954263] init: ssh main process 
(26655) terminated with status 255
Dec  1 11:40:26 jhart-laptop kernel: [1207947.954277] init: ssh main process 
ended, respawning
Dec  1 11:40:26 jhart-laptop kernel: [1207947.957687] init: ssh main process 
(26658) terminated with status 255
Dec  1 11:40:26 jhart-laptop kernel: [1207947.957703] init: ssh main process 
ended, respawning
Dec  1 11:40:26 jhart-laptop kernel: [1207947.961094] init: ssh main process 
(26661) terminated with status 255
Dec  1 11:40:26 jhart-laptop kernel: [1207947.961115] init: ssh main process 
ended, respawning
Dec  1 11:40:26 jhart-laptop kernel: [1207947.964835] init: ssh main process 
(26664) terminated with status 255
Dec  1 11:40:26 jhart-laptop kernel: [1207947.964852] init: ssh main process 
ended, respawning
Dec  1 11:40:26 jhart-laptop kernel: [1207947.968028] init: ssh main process 
(26667) terminated with status 255
Dec  1 11:40:26 jhart-laptop kernel: [1207947.968043] init: ssh main process 
ended, respawning
Dec  1 11:40:26 jhart-laptop kernel: [1207947.971004] init: ssh main process 
(26670) terminated with status 255
Dec  1 11:40:26 jhart-laptop kernel: [1207947.971021] init: ssh main process 
ended, respawning
Dec  1 11:40:26 jhart-laptop kernel: [1207947.974044] init: ssh main process 
(26673) terminated with status 255
Dec  1 11:40:26 jhart-laptop kernel: [1207947.974087] init: ssh main process 
ended, respawning
Dec  1 11:40:26 jhart-laptop kernel: [1207947.977853] init: ssh main process 
(26676) terminated with status 255
Dec  1 11:40:26 jhart-laptop kernel: [1207947.977868] init: ssh main process 
ended, respawning
Dec  1 11:40:26 jhart-laptop kernel: [1207947.980928] init: ssh main process 
(26679) terminated with status 255
Dec  1 11:40:26 jhart-laptop kernel: [1207947.980944] init: ssh main process 
ended, respawning
Dec  1 11:40:26 jhart-laptop kernel: [1207947.984059] init: ssh main process 
(26682) terminated with status 255
Dec  1 11:40:26 jhart-laptop kernel: [1207947.984075] init: ssh main process 
ended, respawning
Dec  1 11:40:26 jhart-laptop kernel: [1207947.987118] init: ssh main process 
(26685) terminated with status 255
Dec  1 11:40:26 jhart-laptop kernel: [1207947.987132] init: ssh respawning too 
fast, stopped

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: openssh-server 1:5.9p1-5ubuntu1.7
ProcVersionSignature: Ubuntu 3.13.0-66.108~precise1-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.13
Architecture: amd64
Date: Tue Dec  1 11:54:42 2015
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: openssh
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise running-unity

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1521745

Title:
  sshd will fail to start or restart if non-default Port option is
  incorrectly put after a non-default ListenAddress

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1521745/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1521748] [NEW] Bug 1511158 750gMaxter HDpackage mysql-server-5.6 5.6.27-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-12-01 Thread ken78724

Public bug reported:

Bug 1511158 750gMaxter HDpackage mysql-server-5.6 5.6.27-0ubuntu1 failed
to install/upgrade: subprocess installed post-installation script
returned error exit status 1

Amid upstart after updates first applied on 1T WD 15.10, secondly 12.02
120g hd, thirdly 8.04 on 80g hd and fourthly this 15.10 750g the mysql
defaulted and gave the 1st paragraph and short line notice.  {the 1T
WD 15.10, secondly 12.02 120g hd, thirdly 8.04 on 80g hd went good but
not the issue on the 750g Maxter having 15.10 new Ubuntu Buzz install,
identical to the 15.10 on the 1 tb WD hd} [sorry for wordiness]

12-1-15
Error mounting /dev/sdd4 at /media/ken/767c4efa-c577-44ac-8451-d445f987b53c: 
Command-line `mount -t "jfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdd4" 
"/media/ken/767c4efa-c577-44ac-8451-d445f987b53c"' exited with non-zero exit 
status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdd4,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.

11-11-15
Read /usr/share/doc/mysql-server-5.6/README.Debian to deal with the error
ken@k78724:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... The following packages were automatically installed and 
are no longer required:
  linux-headers-4.2.0-16 linux-headers-4.2.0-16-generic
  linux-image-4.2.0-16-generic linux-image-extra-4.2.0-16-generic
Use 'apt-get autoremove' to remove them.
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up mysql-server-5.6 (5.6.27-0ubuntu1) ...
2015-11-11 10:37:15 0 [Warning] TIMESTAMP with implicit DEFAULT value is 
deprecated. Please use --explicit_defaults_for_timestamp server option (see 
documentation for more details).
2015-11-11 10:37:15 0 [Note] /usr/sbin/mysqld (mysqld 5.6.27-0ubuntu1) starting 
as process 3045 ...

ken@k78724:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up mysql-server-5.6 (5.6.27-0ubuntu1) ...
Job for mysql.service failed because a timeout was exceeded. See "systemctl 
status mysql.service" and "journalctl -xe" for details.
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing package mysql-server-5.6 (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-server-5.6; however:
  Package mysql-server-5.6 is not configured yet.

dpkg: error processing package mysql-server (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup 
error from a previous failure.

  Errors were encountered while processing:
 mysql-server-5.6
 mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
ken@k78724:~$ 
ken@k78724:~$ sudo dpkg --configure -a
Setting up mysql-server-5.6 (5.6.27-0ubuntu1) ...
2015-11-07 09:01:21 0 [Warning] TIMESTAMP with implicit DEFAULT value is 
deprecated. Please use --explicit_defaults_for_timestamp server option (see 
documentation for more details).
2015-11-07 09:01:21 0 [Note] /usr/sbin/mysqld (mysqld 5.6.27-0ubuntu1) starting 
as process 10117 ...
11:31pm 11-6-15
read the /usr/share/doc/mysql-server-5.6/README.Debian file for│ 
 │ more information

11-4-15 on configuring: mysql server – 5.6 mysql “foot” user:
Unable to set password for the MySQL "root" user  │ 
 │   │ 
 │ An error occurred while setting the password for the MySQL│ 
 │ administrative user. This may have happened because the account already   │ 
 │ has a password, or because of a communication problem with the MySQL  │ 
 │ server.   │ 
 │   │ 
 │ You should check the account's password after the package installation.   │ 
 │   │ 
 │ Please read the /usr/share/doc/mysql-server-5.6/README.Debian file for│ 
 │ more information.

Error message was sent and I copied this note From terminal
Selecting previously unselected package grub-efi-amd64-bin.
Preparing to unpack

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-12-01 Thread dino99

@Bryan

Get the same issue with midori (its confusing as it is not directly depending 
on libnss3).
The default browser used is 'google'; and i get that issue when:
- i use the 'google' search field
- i type an incomplete part url into the top url bar (without http://www.)

So the steps are identical. When libnss3 is downgraded, midori works
again.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1468185] Re: Function 'innodb' already exists and other errors

2015-12-01 Thread eggersrj

Is there a work-around or fix for those that get stuck with a bad
upgrade?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1468185

Title:
   Function 'innodb' already exists and other errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468185/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1517889] Re: package nginx-light (not installed) failed to install/upgrade: underprosessen installerte post-installation-skript returnerte feilstatus 1

2015-12-01 Thread Thomas Ward

This looks to me that maybe you have IPv6 disabled.  Did you make any
changes to disable IPv6 on your system?

** Changed in: nginx (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1517889

Title:
  package nginx-light (not installed) failed to install/upgrade:
  underprosessen installerte post-installation-skript returnerte
  feilstatus 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1517889/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1521786] Re: package nginx-core 1.9.3-1ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2015-12-01 Thread Thomas Ward

Your installation appears to be broken somehow, with
/etc/nginx/nginx.conf having gone missing.

Back up your site configurations and anything else in /etc/nginx/* you
wish to save (as well as /var/, then go about purging and reinstalling
nginx:

sudo apt-get remove --purge nginx nginx-core nginx-common
sudo apt-get update
sudo apt-get install nginx nginx-core nginx-common


This should give you a 'fresh start' and should restore the nginx.conf file.  
However, note that you will need to restore any site configurations you added 
separately (and changes to the default config if any) yourself.

(This is not, however, a bug in the package itself, more a failed system
configuration or something messing with things it shouldn't)

** Changed in: nginx (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1521786

Title:
  package nginx-core 1.9.3-1ubuntu1 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1521786/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1521786] [NEW] package nginx-core 1.9.3-1ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2015-12-01 Thread Bernhard Nikola

Public bug reported:

Description:Ubuntu 15.10
Release:15.10

  Installiert:   1.9.3-1ubuntu1
  Installationskandidat: 1.9.3-1ubuntu1
  Versionstabelle:
 *** 1.9.3-1ubuntu1 0
500 http://de.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
 1.8.0-1~wily 0
500 http://nginx.org/packages/ubuntu/ wily/nginx amd64 Packages

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: nginx-core 1.9.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Tue Dec  1 23:38:00 2015
DuplicateSignature: package:nginx-core:1.9.3-1ubuntu1:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
InstallationDate: Installed on 2015-11-29 (2 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu1
SourcePackage: nginx
Title: package nginx-core 1.9.3-1ubuntu1 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nginx (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check wily

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1521786

Title:
  package nginx-core 1.9.3-1ubuntu1 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1521786/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1517889] Re: package nginx-light (not installed) failed to install/upgrade: underprosessen installerte post-installation-skript returnerte feilstatus 1

2015-12-01 Thread Thomas Ward

Confirmed in testing.  Your system has IPv6 disabled completely, which
is a non-standard setup.  This is an issue with your server, and not an
issue in the package.

To fix this, either reconfigure your server to have IPv6 enabled (even
if it's just on the localhost and not a public IPv6), or remove the line
in /etc/nginx/sites-available/default/ that looks like this:

listen [::]:80 default_server;

** Changed in: nginx (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1517889

Title:
  package nginx-light (not installed) failed to install/upgrade:
  underprosessen installerte post-installation-skript returnerte
  feilstatus 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1517889/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1353939] Change abandoned on nova (stable/juno)

2015-12-01 Thread OpenStack Infra

Change abandoned by Matt Riedemann (mrie...@us.ibm.com) on branch: stable/juno
Review: https://review.openstack.org/221529
Reason: Juno is EOL soon.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1353939

Title:
  Rescue fails with 'Failed to terminate process: Device or resource
  busy' in the n-cpu log

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1353939/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1516989] Re: juju status broken

2015-12-01 Thread Johan Ehnberg

I confirm the fix is effective. For large environments where hooks have failed, 
here's a one-liner after running the fix to re-run all the failed hooks, which 
should return the agents to normal (idle) state:
for i in `juju status --format tabular|grep failed|awk '{print $1;}'`;do echo 
Fixing $i;juju resolved -r $i;done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1516989

Title:
  juju status  broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1469143] Re: kpartx -d fails with image paths longer than 63 characters

2015-12-01 Thread Mathieu Trudel-Lapierre

** Description changed:

+ [Impact]
+ Users of kpartx to load disk images, possibly multiple images with the same 
file name (but in different paths).
+ 
+ [Test case]
+ See below, also see 
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1469143/comments/3
+ 
+ [Regression potential]
+ This changes makes the matching for loaded images more robust, and so has a 
very limited risk of regression. Since there is a call to stat() introduced, 
one may notice a slowdown if the stat() call blocks for a reason, and the 
operation will fail if the stat() call fails for any reason, since the device 
and inode are now required.
+ 
+ ---
+ 
  $ apt-show-versions multipath-tools
  multipath-tools:amd64/vivid 0.4.9-3ubuntu12 uptodate
  
  Reproduce:
  Mount an image from a path longer than 63 chars succeeds:
  $ sudo kpartx -av 
asfd1asdf2asdf3asdf4asdf5asdf6asfd7asdf8asdf9asf10asdf11asdf12asdf13/disk.img
  add map loop0p1 (252:0): 0 409600 linear /dev/loop0 2048
  add map loop0p2 (252:1): 0 2 linear /dev/loop0 411648
  add map loop0p5 : 0 819200 linear /dev/loop0 413696
  add map loop0p6 : 0 819200 linear /dev/loop0 1234944
  add map loop0p7 : 0 819200 linear /dev/loop0 2056192
  add map loop0p8 : 0 1316864 linear /dev/loop0 2877440
  
  but dismounting fails:
  $ sudo kpartx -dv 
asfd1asdf2asdf3asdf4asdf5asdf6asfd7asdf8asdf9asf10asdf11asdf12asdf13/disk.img
  
  strace shows that the parameter on the dismount appears to get cut at 63 
chars:
  ioctl(3, DM_LIST_VERSIONS, 0x15b89b0)   = 0
  
stat("asfd1asdf2asdf3asdf4asdf5asdf6asfd7asdf8asdf9asf10asdf11asdf12asdf13/disk.img",
 {st_mode=S_IFREG|0644, st_size=2147483648, ...}) = 0
  stat("/dev/loop0", {st_mode=S_IFBLK|0660, st_rdev=makedev(7, 0), ...}) = 0
  open("/dev/loop0", O_RDONLY)= 4
  ioctl(4, LOOP_GET_STATUS, {number=0, offset=0, flags=0, 
name="asfd1asdf2asdf3asdf4asdf5asdf6asfd7asdf8asdf9asf10asdf11asdf12a", ...}) = 0
  close(4)= 0
  stat("/dev/loop1", {st_mode=S_IFBLK|0660, st_rdev=makedev(7, 1), ...}) = 0
  open("/dev/loop1", O_RDONLY)= 4
  ioctl(4, LOOP_GET_STATUS, {number=0, offset=0, flags=0, 
name="asfd1asdf2asdf3asdf4asdf5asdf6asfd7asdf8asdf9asf10asdf11asdf12a", ...}) = 
-1 ENXIO (No such device or address)
  
  if the path is 63 chars or less, the dismount also succeeds.
  
  This is quickly becomes an issue if you want to use full disk paths in
  your shell scripts.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1469143

Title:
  kpartx -d fails with image paths longer than 63 characters

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1469143/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1468897] Re: multipath creates binding for Removable(USB) drives

2015-12-01 Thread Mathieu Trudel-Lapierre

** Also affects: multipath-tools (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: multipath-tools (Ubuntu Vivid)
   Status: New => In Progress

** Changed in: multipath-tools (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: multipath-tools (Ubuntu Vivid)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1468897

Title:
  multipath creates binding for Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1386637] Re: multipath shows non-mpath disks as being multipath

2015-12-01 Thread Mathieu Trudel-Lapierre

** Also affects: multipath-tools (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: multipath-tools (Ubuntu Vivid)
   Status: New => In Progress

** Changed in: multipath-tools (Ubuntu Vivid)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1386637

Title:
  multipath shows non-mpath disks as being multipath

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1386637/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1503286] Re: ISST-LTE: Boot of Ubuntu15.10 lpar fails: "mounting /dev/sdn2 on /root failed: Device or resource busy" [multipath]

2015-12-01 Thread Mathieu Trudel-Lapierre

** Description changed:

+ [Impact]
+ Systems with disks that have long spin-up times or otherwise take a while to 
be detected may be affected by a failure to boot due to the drives underlying 
multipath devices not being available.
+ 
+ [Test case]
+ This issue is difficult to reproduce.
+  - Boot a system with the boot device on multipath.
+ This may be limited to POWER LPARs. See description below.
+ 
+ [Regression Potential]
+ Given that a new initramfs script is introduced to add a udev trigger with a 
timeout of 2 minutes (121 seconds), users may notice a delay of up to two 
minutes in booting if devices take 2 minutes or more to be brought up or 
detected by udev.
+ 
+ ---
+ 
  == Comment: #0 - Manjunatha H R  - 2015-09-25 11:05:36 ==
  Booting of Ubuntu15.10 lpar fails and control falls to initramfs.
  
  uname -a
  --
  Linux (none) 4.2.0-10-generic #12-Ubuntu SMP Tue Sep 15 19:46:04 UTC 2015 
ppc64le GNU/Linux
  
- 
  Boot log:
  -
-   Booting a command list
+   Booting a command list
  
  Loading Linux 4.2.0-10-generic ...
  Loading initial ramdisk ...
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 4.2.0-10-generic (buildd@fisher04) (gcc 
version 5.2.1 20150911 (Ubuntu 5.2.1-17ubuntu4) ) #12-Ubuntu SMP Tue Sep 15 
19:46:04 UTC 2015 (Ubuntu 4.2.0-10.12-generic 4.2.0)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-4.2.0-10-generic 
root=UUID=822dd709-5b69-45a9-aba5-63cb55768ffb ro splash quiet 
topology_updates=off
  memory layout at init:
-   memory_limit :  (16 MB aligned)
-   alloc_bottom : 0bf8
-   alloc_top: 1000
-   alloc_top_hi : 1000
-   rmo_top  : 1000
-   ram_top  : 1000
+   memory_limit :  (16 MB aligned)
+   alloc_bottom : 0bf8
+   alloc_top: 1000
+   alloc_top_hi : 1000
+   rmo_top  : 1000
+   ram_top  : 1000
  found display   : /pci@800202c/display@0, opening... done
  instantiating rtas at 0x0eb6... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0bf9 -> 0x0bf91965
  Device tree struct  0x0bfa -> 0x0bfe
  Quiescing Open Firmware ...
  Booting Linux via __start() ...
-  -> smp_release_cpus()
+  -> smp_release_cpus()
  spinning_secondaries = 199
-  <- smp_release_cpus()
-  <- setup_system()
+  <- smp_release_cpus()
+  <- setup_system()
  [2.868103] [drm:radeon_device_init [radeon]] *ERROR* Unable to find PCI 
I/O BAR
  [3.074553] [drm:radeon_atombios_init [radeon]] *ERROR* Unable to find PCI 
I/O BAR; using MMIO for ATOM IIO
  [5.060785] lpfc 0002:90:00.0: 0:1303 Link Up Event x1 received Data: x1 
x0 x80 x0 x0 x0 0
  Scanning for Btrfs filesystems
  fsck from util-linux 2.26.2
  /dev/sdn2 is in use.
  e2fsck: Cannot continue, aborting.
  
  fsck exited with status code 8
  [   36.233086]  rport-0:0-9: blocked FC remote port time out: removing rport
  mount: mounting /dev/sdn2 on /root failed: Device or resource busy
  Target filesystem doesn't have requested /sbin/init.
  mount: mounting /dev on /root/dev failed: No such file or directory
  No init found. Try passing init= bootarg.
  
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.
  
  (initramfs)
  -
  
- 
  This lpar is having multipath disks and boot disk is on a multipath disk.
  Boot passes only whenever fsck tries to scan boot disk via :  /dev/dm OR 
/dev/mapper/mpath
  
  Boot Pass scenarios:
  
  1. Boot passed when fsck tried scanning "/dev/mapper/mpathb"
  fsck from util-linux 2.26.2
  /dev/mapper/mpathb-part2: clean, 81802/3139584 files, 1040598/12558080 blocks
  
  2. Boot passed when fsck tried scanning  "/dev/dm-3"
  Scanning for Btrfs filesystems
  fsck from util-linux 2.26.2
  /dev/dm-3: clean, 81802/3139584 files, 1040605/12558080 blocks
  
- 
- Boot fails, whenever fsck is called on /dev/sd 
+ Boot fails, whenever fsck is called on /dev/sd
  
  Boot fail scenario: Boot failed when fsck is called on "/dev/sdn"
  -
  Scanning for Btrfs filesystems
  fsck from util-linux 2.26.2
  /dev/sdn2 is in use.
  e2fsck: Cannot continue, aborting.
  
  fsck exited with status code 8
  [   36.108653]  rport-0:0-9: blocked FC remote port time out: removing rport
  mount: mounting /dev/sdn2 on /root failed: Device or resource busy
  Target filesystem doesn't have requested /sbin/init.
  
  mount: mounting /dev on /root/dev failed: No such file or directory
  No init found. Try passing init= bootarg.
  
  BusyBox v1.22.1 (Ubuntu

[Bug 1516989] Re: juju status broken

2015-12-01 Thread Cheryl Jennings

Just a note to those using the script to insert the workload status -
you'll see a bogus time in the "since" field:  31 Dec 1969
18:00:00-06:00

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1516989

Title:
  juju status  broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1516989] Re: juju status broken

2015-12-01 Thread Jill Rouleau

** Tags added: canonical-bootstack

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1516989

Title:
  juju status  broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1516989] Re: juju status broken

2015-12-01 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: juju-core (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1516989

Title:
  juju status  broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-12-01 Thread en

Doesn't affect duckduckgo.com etc but only google (sub)domains!

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1361373] Re: package squid3 3.1.19-1ubuntu3.12.04.2 failed to install/upgrade: ErrorMessage: 子程序新的 pre-installation script 傳回了錯誤退出狀態 1

2015-12-01 Thread Launchpad Bug Tracker

[Expired for squid3 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: squid3 (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1361373

Title:
  package squid3 3.1.19-1ubuntu3.12.04.2 failed to install/upgrade:
  ErrorMessage: 子程序 新的 pre-installation script 傳回了錯誤退出狀態 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1361373/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1462729] Re: init config doesn't located at /etc/init.d

2015-12-01 Thread Launchpad Bug Tracker

[Expired for squid3 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: squid3 (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1462729

Title:
  init config doesn't located at /etc/init.d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1462729/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1521722] [NEW] ftbfs on s390x on ubuntu/debian/upstream

2015-12-01 Thread Dimitri John Ledkov

Public bug reported:

ftbfs on s390x on ubuntu/debian/upstream

** Affects: ldb (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: ftbfs s390x

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ldb in Ubuntu.
https://bugs.launchpad.net/bugs/1521722

Title:
  ftbfs on s390x on ubuntu/debian/upstream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ldb/+bug/1521722/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-12-01 Thread Bryan Quigley

@dino99  I can't reproduce this with midori.  Are the symptoms identical
for you?  Are there any midori specific steps?

I couldn't reproduce this issue on Debian sid.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1499510] Re: [SRU] Fix Typo in socket attribute name in TCPKeepAliveAdapter

2015-12-01 Thread James Page

Promoted to -updates for Kilo UCA.

** Changed in: cloud-archive/kilo
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-novaclient in Ubuntu.
https://bugs.launchpad.net/bugs/1499510

Title:
  [SRU] Fix Typo in socket attribute name in TCPKeepAliveAdapter

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1499510/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address

2015-12-01 Thread Mike Pontillo

Getting closer:

http://paste.ubuntu.com/13595538/

I still don't know exactly why this is happening, but I think I can get
it fixed within a day.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1519527

Title:
  juju 1.25.1:  lxc units all have the same IP address - changed to
  claim_sticky_ip_address

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1519527/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address

2015-12-01 Thread Mike Pontillo

I can confirm that I have replicated the issue in my local MAAS test
bed.

I'm seeing behavior such as this:

$ maas admin device claim-sticky-ip-address 
node-ad58adcc-980a-11e5-a692-525400130e6f
Success.
Machine-readable output follows:
{
"macaddress_set": [
{
"mac_address": "01:02:03:04:05:07"
}
], 
"zone": {
"resource_uri": "/MAAS/api/1.0/zones/default/", 
"name": "default", 
"description": ""
}, 
"parent": "node-0f48bcc8-9263-11e5-9fc7-525400130e6f", 
"ip_addresses": [], 
"hostname": "cheap-coast.maas", 
"system_id": "node-ad58adcc-980a-11e5-a692-525400130e6f", 
"owner": "root", 
"tag_names": [], 
"resource_uri": 
"/MAAS/api/1.0/devices/node-ad58adcc-980a-11e5-a692-525400130e6f/"
}

I would expect to see some ip_addresses here, but we've got nothing.

I'm still working on the root cause.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1519527

Title:
  juju 1.25.1:  lxc units all have the same IP address - changed to
  claim_sticky_ip_address

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1519527/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1518016] Re: [SRU] Nova kilo requires concurrency 1.8.2 or better

2015-12-01 Thread James Page

python-oslo.concurrency and nova promoted to -updates for Kilo UCA.

** Changed in: cloud-archive/kilo
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1518016

Title:
  [SRU] Nova kilo requires concurrency 1.8.2 or better

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1518016/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-12-01 Thread Igor

> dino99 (9d9)
> Looks like related to these changes:
> nss (2:3.21-1)

The question is, why the Google Chrome is not affected by this, since it
depends on the same library?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2015-12-01 Thread Talat Batheesh

Hi Rafael,

After updating libibverbs and libmlx4 (upstream version) from the
openfabrics, the issue solved.

git clone git://git.kernel.org/pub/scm/libs/infiniband/libibverbs.git libibverbs
git clone git://git.openfabrics.org/~yishaih/libmlx4.git

# apt-get install libnl-3-dev libnl-route-3-dev

we must to update the libibverbs abd libmlx4 to updated version.

Yours,
Talat

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1312419

Title:
  nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1312419/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1521560] [NEW] User can delete any image

2015-12-01 Thread Viktor Křivák

*** This bug is a security vulnerability ***

Public security bug reported:

Not sure if I don't have some typo in config but it is look like that
from Kilo, user can delete any image via nova API. Only uuid is needed.
Also user can list every image image in system even non public which
doesn't belong to him.

# Image info:
$ glance image-show 3ce0aadd-2e79-4d6b-86db-5ccd0fce3eba
+--+--+
| Property | Value|
+--+--+
| checksum | ee1eca47dc88f4879d8a229cc70a07c6 |
| container_format | bare |
| created_at   | 2015-11-30T18:08:05Z |
| disk_format  | qcow2|
| hw_vif_model | e1000|
| id   | 3ce0aadd-2e79-4d6b-86db-5ccd0fce3eba |
| min_disk | 0|
| min_ram  | 0|
| name | Cirros 0.3.4 |
| owner| d697f13bce95426d82179c216a8e3f1c |
| protected| False|
| size | 13287936 |
| status   | active   |
| tags | []   |
| updated_at   | 2015-11-30T18:08:06Z |
| virtual_size | None |
| visibility   | public   |
+--+--+


# Notice it is just public image with owner (another as myself)

# My session
$openstack token issue
++--+
| Field  | Value|
++--+
| expires| 2015-12-01T11:03:03.988742Z  |
| id |  |
| project_id | 873a42b1eb3a42768f6b702c55b5c932 |
| user_id| 37d0d3638ab243f786e68649fad84354 |
++--+


# And then this somehow works
$ nova image-delete 3ce0aadd-2e79-4d6b-86db-5ccd0fce3eba
$ nova image-list
+--+-+++
| ID   | Name| Status | Server |
+--+-+++
| 90678a27-c1e7-499b-9c06-bc6c01e100b3 | Debian 7 - Refstack | ACTIVE ||
| f851e1d7-9e17-4c6f-beda-de3b3ea40db1 | Debian 8| ACTIVE ||
+--+-+++
$ nova image-show 3ce0aadd-2e79-4d6b-86db-5ccd0fce3eba
ERROR (CommandError): No image with a name or ID of 
'3ce0aadd-2e79-4d6b-86db-5ccd0fce3eba' exists.
$ glance image-show 3ce0aadd-2e79-4d6b-86db-5ccd0fce3eba
404 Not Found: No image found with ID 3ce0aadd-2e79-4d6b-86db-5ccd0fce3eba 
(HTTP 404)

Glance always correctly return 404 but nova delete it even if I'm just a member.
If I don't have any mistake in config this is serious security bug, because 
anyone can delete any image.

My opinion is that nova call glance internally as admin and it don't do any 
additional controls of permission.
Quick fix can be just add filter to nova/image/api.py 

My nova version: 2015.1.2-2 (Kilo)
Test on Debian GNU/Linux 8.2 (jessie) but I think this bug is general

** Affects: nova (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Nova configuration with removed passwords"
   https://bugs.launchpad.net/bugs/1521560/+attachment/4527887/+files/nova.conf

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1521560

Title:
  User can delete any image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1521560/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1520192] Re: multipath-tools from Precise should have been fixed together with Trusty fixes

2015-12-01 Thread Gábor Mészáros

With the backported package the problem cannot be reproduced.

** Attachment added: "Log that shows no problem with newer version of 
multipath-tools and kpartx"
   
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192/+attachment/4527997/+files/reproduction_fixed.log

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1520192

Title:
  multipath-tools from Precise should have been fixed together with
  Trusty fixes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1520192] Re: multipath-tools from Precise should have been fixed together with Trusty fixes

2015-12-01 Thread Gábor Mészáros

** Attachment added: "Log that shows the problem"
   
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192/+attachment/4527996/+files/reproduction_failing.log

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1520192

Title:
  multipath-tools from Precise should have been fixed together with
  Trusty fixes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-12-01 Thread Marc Deslauriers

nss 3.20.1 works, nss 3.21 doesn't.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-12-01 Thread dino99

confirm #19 test above

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1520192] Re: multipath-tools from Precise should have been fixed together with Trusty fixes

2015-12-01 Thread Gábor Mészáros

Steps taken to provoke the problem:
1.) deploy any VM instance using nova commands, that is booted from EMC VNX 
series SAN connected to compute using iscsi, dm-multipath
2.) unplug/disable network connectivity on any of the active paths
3.) check multipath -ll output for faulty failed path/device status.
4.) re-plug/enable network connectivity on the disabled paths
5.) check multipath -ll output for recovering to active enabled path/device 
status

Somtimes the problem occurs when disabling the interface, other times
only when re-enabling it.

Expected output for multipath -ll:
36006016047813400dd029f614896e511 dm-3 DGC ,VRAID   
size=50G features='0' hwhandler='1 alua' wp=rw
`-+- policy='round-robin 0' prio=70 status=active
  |- 6:0:0:15 sdi   8:128  active ready  running
  |- 7:0:0:15 sdk   8:160  active ready  running
  |- 8:0:0:15 sdm   8:192  active ready  running
  `- 9:0:0:15 sdo   8:224  active ready  running

Actual output (even after several hours of waiting, with active traffic on 
storage):
36006016047813400dd029f614896e511 dm-3 DGC,VRAID
size=50G features='0' hwhandler='1 alua' wp=rw
`-+- policy='round-robin 0' prio=70 status=active
  |- 6:0:0:159 sdi 8:128 active ready  running
  |- 7:0:0:159 sdk 8:160 failed ready  running
  |- 8:0:0:159 sdm 8:192 active ready  running
  `- 9:0:0:159 sdo 8:224 failed ready  running

A previously discovered workaround for the problem can be achieved by reloading 
the multipath-tools service (or restarting, but multipath -r does not always 
fixes it).
The package with backported changes is confirmed to fix the issue, without 
having to reload the service.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1520192

Title:
  multipath-tools from Precise should have been fixed together with
  Trusty fixes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-12-01 Thread Barry Warsaw

On Dec 01, 2015, at 01:38 PM, Marc Deslauriers wrote:

>1- I can't reproduce this by installing the daily live cd in a VM
>2- I can reproduce it successfully by installing the daily live cd on real 
>hardware

Confirmed that my working machine is a VM and the busted one is physical
hardware.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

2015-12-01 Thread Adam Katz

Peter:  Yes, that's all true (it's a workaround after all), though you
could add the ssh-agent command to your startup scripts.  I've updated
my Stack Exchange answer 
to reflect that.

BTW, you don't actually need the `mv` line since the .broken socket
isn't terribly useful.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/201786

Title:
  ssh Agent admitted failure to sign using the key on big endian
  machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1516085] Re: quotas calls fail when CONF.keymgr.encryption_auth_url is not configured

2015-12-01 Thread OpenStack Infra

Fix proposed to branch: master
Review: https://review.openstack.org/251937

** Changed in: cinder
 Assignee: Michal Dulko (michal-dulko-f) => Szymon Borkowski 
(szymon-borkowski)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1516085

Title:
  quotas calls fail when CONF.keymgr.encryption_auth_url is not
  configured

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1516085/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

2015-12-01 Thread Adam Katz

While this is not a big endian problem, it is a problem and it is NOT
solved yet.  I doubt it will be solved until Ubuntu bug 1420522
 is
solved.

This is GNOME bug 754028 
(Among others, see 
https://bugzilla.gnome.org/buglist.cgi?no_redirect=0=ed25519#)

** Bug watch added: GNOME Bug Tracker #754028
   https://bugzilla.gnome.org/show_bug.cgi?id=754028

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/201786

Title:
  ssh Agent admitted failure to sign using the key on big endian
  machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1506187] Re: [SRU] Azure: cloud-init should use VM unique ID

2015-12-01 Thread Martin Pitt

Hello Stephen, or anyone else affected,

Accepted cloud-init into wily-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.7~bzr1149-0ubuntu5 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: cloud-init (Ubuntu Wily)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1506187

Title:
  [SRU] Azure: cloud-init should use VM unique ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1506187/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1517865] Re: nginx-extras push module fd leak

2015-12-01 Thread Thomas Ward

We aren't asking for what version of the module fixed this we are
looking for the exact code commit that fixes the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1517865

Title:
  nginx-extras push module fd leak

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1517865/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1517865] Re: nginx-extras push module fd leak

2015-12-01 Thread Sergey

I'm not very experienced in this, but module was fixed and taged as v0.73 on 2 
Sep 2014
https://github.com/slact/nchan/issues/90

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1517865

Title:
  nginx-extras push module fd leak

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1517865/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1500581] Re: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’]

2015-12-01 Thread Armin Kunaschik

The new version from the PPA works fine on amd64 but doesn't on i386 with a 
current 15.10 on VMPlayer 12.0.1.
There are no visible errors, vmware-hgfsclient does not show any shared 
folders, mount gives i/o errors. vmware tools also don't work on i386, so there 
might be a general problem.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1500581

Title:
  open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf)
  [error: implicit declaration of function ‘nd_set_link’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1500581/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-12-01 Thread dino99

@Igor

- chromium is affected, and indeed use the faulty libnss3 package (which works 
again if libnss3 is downgraded)
- midori is also affected, but does not use libnss3 as a dependency directly; 
supposing some sub-depency is disturbed

- problem exist with 'google' as the default browser, but not with
'duckduckgo' for example (and possibly with the other search engines)

That system is a 64 bits wily -> xenial installation with 'proposed'
archive activated

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1469143] Re: kpartx -d fails with image paths longer than 63 characters

2015-12-01 Thread Mathieu Trudel-Lapierre

** Changed in: multipath-tools (Ubuntu Vivid)
   Status: New => In Progress

** Changed in: multipath-tools (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: multipath-tools (Ubuntu Precise)
   Status: New => In Progress

** Changed in: multipath-tools (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: multipath-tools (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: multipath-tools (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: multipath-tools (Ubuntu Precise)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

** Changed in: multipath-tools (Ubuntu Trusty)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

** Changed in: multipath-tools (Ubuntu Vivid)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1469143

Title:
  kpartx -d fails with image paths longer than 63 characters

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1469143/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1503286] Re: ISST-LTE: Boot of Ubuntu15.10 lpar fails: "mounting /dev/sdn2 on /root failed: Device or resource busy" [multipath]

2015-12-01 Thread Mathieu Trudel-Lapierre

** Changed in: multipath-tools (Ubuntu Trusty)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1503286

Title:
  ISST-LTE: Boot of Ubuntu15.10 lpar fails: "mounting /dev/sdn2 on /root
  failed: Device or resource busy" [multipath]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1503286/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1521621] [NEW] Quagga BGP and static routes with metric bug

2015-12-01 Thread Stefan

Public bug reported:

If for instance you learn a DST route of 172.18.1.1/32  from your BGP
neighbor with a metric of 0, and you add a static route of 172.18.1.1/32
with a metric of 20, the BGP route disappears out of the kernel routing
table. This is normal behavior.

So if you statically add a route of 172.18.1.1/32 with a metric of 20,
another of 172.18.1.1/32 with a metric of 25 and another with a metric
of 35 the BGP route is still missing.

Now when you delete any of the three routes, for instance the one with
the metric of 25. Qaugga's BGP daemon adds the BGP route back into the
routing table, thinking the route was deleted.

Not sure if this is the desired functionality or a bug.

Example:

BGP learned route:

route -n | grep 172.18.1.1
172.18.1.1 10.19.0.1  255.255.255.255 UGH   0  00 eth3

Adding static route with metric:

route -n | grep 172.18.1.1
172.18.1.1 10.19.0.1  255.255.255.255 UGH   20  00 eth3

Adding more static routes:

route -n | grep 172.18.1.1
172.18.1.1 10.19.0.1  255.255.255.255 UGH   20  00 eth3
172.18.1.1 10.19.0.1  255.255.255.255 UGH   25  00 eth3
172.18.1.1 10.19.0.1  255.255.255.255 UGH   35  00 eth3

Deleting one of the static routes:

172.18.1.1 10.19.0.1  255.255.255.255 UGH   0  00 eth3
172.18.1.1 10.19.0.1  255.255.255.255 UGH   25  00 eth3
172.18.1.1 10.19.0.1  255.255.255.255 UGH   35  00 eth3

** Affects: quagga (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quagga in Ubuntu.
https://bugs.launchpad.net/bugs/1521621

Title:
  Quagga BGP and static routes with metric bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/quagga/+bug/1521621/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-12-01 Thread Marc Deslauriers

OK, a few more notes on reproducing this:

1- I can't reproduce this by installing the daily live cd in a VM
2- I can reproduce it successfully by installing the daily live cd on real 
hardware

This means it's probably not related to which Google servers are being
hit, and is likely hardware-dependent. This matches the behaviour Barry
noticed in comment #10.

On the real hardware, where the problem occurs, I see "Fontconfig error:
Cannot load default config file" on the console with every character
that I type in the URL bar which results in a failed google lookahead
search.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1520568

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1423972] [NEW] cloud-init user-data mime conversion fails on base64 encoded data

2015-12-01 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Cloud-init's conversion of user-data to mime fails when the user-data is
base64 encoded due to the Python2 to Python3 switch. base64.b64decode in
Python 2 returns a string, whilst Python3 returns a byte stream.

Consider:
  import base64

  hi = "aGkK"
  print(type(base64.b64decode(hi)).__name__)
  if 'hi' in str(base64.b64decode(hi)):
 print("works")
  if 'hi' in base64.b64decode(hi):
 print("works on Py2")

ben@prongs:~$ python /tmp/proof.py 
str
works
works on Py2
ben@prongs:~$ python3 /tmp/proof.py 
bytes
works
Traceback (most recent call last):
  File "/tmp/proof.py", line 10, in 
if 'hi' in base64.b64decode(hi):
TypeError: Type str doesn't support the buffer API

** Affects: cloud-init
 Importance: High
 Assignee: Ben Howard (utlemming)
 Status: Fix Committed

** Affects: cloud-init (Ubuntu)
 Importance: Critical
 Assignee: Ben Howard (utlemming)
 Status: In Progress


** Tags: apport-collected bot-comment patch uec-images vivid
-- 
cloud-init user-data mime conversion fails on base64 encoded data
https://bugs.launchpad.net/bugs/1423972
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to cloud-init in Ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1506187] Re: [SRU] Azure: cloud-init should use VM unique ID

2015-12-01 Thread Ben Howard

Verified for 15.10 and 14.04.

** Tags removed: verification-needed
** Tags added: verification-done verification-done-wily

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1506187

Title:
  [SRU] Azure: cloud-init should use VM unique ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1506187/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1423972] Re: cloud-init user-data mime conversion fails on base64 encoded data

2015-12-01 Thread Mathew Hodson

** Package changed: ubuntu => cloud-init (Ubuntu)

** Changed in: cloud-init (Ubuntu)
Milestone: ubuntu-15.03 => None

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1423972

Title:
  cloud-init user-data mime conversion fails on base64 encoded data

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1423972/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1510108] Re: pre-installed lxc in cloud-image means loss of access to 10.0.X.0/24

2015-12-01 Thread Jon Grimm

** Changed in: lxc (Ubuntu Wily)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: lxc (Ubuntu Xenial)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1510108

Title:
  pre-installed lxc in cloud-image means loss of access to 10.0.X.0/24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1510108/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1516989] Re: juju status broken

2015-12-01 Thread Cheryl Jennings

** Also affects: juju-core/1.25
   Importance: Undecided
   Status: New

** Changed in: juju-core/1.25
   Status: New => Fix Committed

** Changed in: juju-core/1.25
   Importance: Undecided => Critical

** Changed in: juju-core/1.25
 Assignee: (unassigned) => Jesse Meek (waigani)

** Changed in: juju-core/1.25
Milestone: None => 1.25.2

** Changed in: juju-core
Milestone: 1.25.2 => 1.26-alpha3

** Changed in: juju-core
   Status: Fix Committed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1516989

Title:
  juju status  broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

54 matches

Mail list logo