[Bug 1175049] [NEW] squid3 - current 3.1.x is strongly deprecated

2013-05-01 Thread H.-Dirk Schmitt
Public bug reported:

Current Ubuntu Versions are:

* squid3 (3.1.19-1ubuntu3.12.04.2) precise-security; urgency=low
* squid3 (3.1.20-1ubuntu3) raring-proposed; urgency=low

The upstream versions are:
* 3.3
* 3.2 [deprecated, see announcement mails]
* 3.1 [old, [see http://www.squid-cache.org/Versions/]

I suggest to make the squid 3.3 available in precise-backports and
saucy.


---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

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

** Affects: squid3 (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: precise saucy

** Tags added: precise saucy

** Bug watch added: Debian Bug tracker #694633
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694633

** Also affects: squid3 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694633
   Importance: Unknown
   Status: Unknown

-- 
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/1175049

Title:
  squid3 - current 3.1.x is strongly deprecated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1175049/+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 1173070] Re: package vsftpd 3.0.2-1ubuntu1 failed to install/upgrade: package vsftpd is not ready for configuration cannot configure (current status `half-installed')

2013-05-01 Thread Eran Uzan
i`m not  really sure what config file you meant so i sent a few...
the /etc/vfstpd was deleted  once i sucessfuly removed the vfstpd package
so i only have it`s main config file... sorry :/


On Tue, Apr 30, 2013 at 10:40 AM, Yolanda Robla yolanda.ro...@canonical.com
 wrote:

 Please can you provide the config file (without usernames or passwords)
 to check the origin of the error?

 ** Changed in: vsftpd (Ubuntu)
Status: New = Incomplete

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1173070

 Title:
   package vsftpd 3.0.2-1ubuntu1 failed to install/upgrade: package
   vsftpd is not ready for configuration  cannot configure (current
   status `half-installed')

 Status in “vsftpd” package in Ubuntu:
   Incomplete

 Bug description:
   I modified the configuration  a little and then upgraded from 12.10 to
   13.04 this might be the reason of the failure

   ProblemType: Package
   DistroRelease: Ubuntu 13.04
   Package: vsftpd 3.0.2-1ubuntu1
   ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
   Uname: Linux 3.8.0-19-generic x86_64
   ApportVersion: 2.9.2-0ubuntu8
   AptOrdering: vsftpd: Configure
   Architecture: amd64
   Date: Fri Apr 26 11:07:30 2013
   DpkgTerminalLog:
dpkg: error processing vsftpd (--configure):
 package vsftpd is not ready for configuration
 cannot configure (current status `half-installed')
   ErrorMessage: package vsftpd is not ready for configuration  cannot
 configure (current status `half-installed')
   InstallationDate: Installed on 2013-01-21 (94 days ago)
   InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64
 (20121017.5)
   MarkForUpload: True
   SourcePackage: vsftpd
   Title: package vsftpd 3.0.2-1ubuntu1 failed to install/upgrade: package
 vsftpd is not ready for configuration  cannot configure (current status
 `half-installed')
   UpgradeStatus: Upgraded to raring on 2013-04-25 (0 days ago)

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1173070/+subscriptions



** Attachment added: vsftpd.conf
   
https://bugs.launchpad.net/bugs/1173070/+attachment/3661144/+files/vsftpd.conf

** Attachment added: sources.list
   
https://bugs.launchpad.net/bugs/1173070/+attachment/3661145/+files/sources.list

** Attachment added: sources.list.distUpgrade
   
https://bugs.launchpad.net/bugs/1173070/+attachment/3661146/+files/sources.list.distUpgrade

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

Title:
  package vsftpd 3.0.2-1ubuntu1 failed to install/upgrade: package
  vsftpd is not ready for configuration  cannot configure (current
  status `half-installed')

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1173070/+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 1175049] Re: Please merge squid3 3.3.3-2 (main) from Debian unstable (main)

2013-05-01 Thread Robie Basak
Thanks for reporting this.

sid is on 3.3.3-2 and Saucy on 3.1.20-1ubuntu3 so a merge is appropriate
here. This needs to happen before any backport.

I'm not sure whether the backports team would like a new bug for this
after Saucy is updated or not.

** Summary changed:

- squid3 - current 3.1.x is strongly deprecated
+ Please merge squid3 3.3.3-2 (main) from Debian unstable (main)

** Tags added: upgrade-software-version

-- 
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/1175049

Title:
  Please merge squid3 3.3.3-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1175049/+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 1160372] Re: Login is not possible

2013-05-01 Thread Vincent DAVY
Hi all,

I compiled the vsftpd package

** Attachment added: vsftpd_3.0.2-1ubuntu1_amd64_patched.deb
   
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+attachment/3661388/+files/vsftpd_3.0.2-1ubuntu1_amd64_patched.deb

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

Title:
  Login is not possible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+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 1160372] Re: Login is not possible

2013-05-01 Thread Vincent DAVY
Here is the patched vsftpd version in 32bits arch.

** Attachment added: vsftpd_3.0.2-1ubuntu1_i386_patched.deb
   
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+attachment/3661389/+files/vsftpd_3.0.2-1ubuntu1_i386_patched.deb

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

Title:
  Login is not possible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+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 1160372] Re: Login is not possible

2013-05-01 Thread Vincent DAVY
Hi all,

Previous messages were sent too fast and I didn't find a way to remove them.
I posted the patched version of vsftpd in both 34 and 32 bits arch : please 
feel free to download.

Don't forget to remove the previous installed version on your system or dpkg 
will tell you that the package is already installed :
sudo apt-get remove vsftpd 
sudo dpkg -i vsftpd_patched.deb

That's all, and it doesn't remove config files.

If you prefer to compile your own version, here is the procedure : 
mkdir vsftpd-patched
cd vsftpd-patched
sudo apt-get build-dep vsftpd
sudo apt-get install fakeroot
apt-get source vsftpd
-- Go on 
https://build.opensuse.org/package/view_file?file=vsftpd-drop-newpid-from-clone.patchpackage=vsftpdproject=openSUSE%3AFactoryrev=3ed24d12e1827ea673331e213ab3d477
 and copy/paste the patch in a file (assuming in 
vsftpd-drop-newpid-from-clone.patch for the rest of this tutorial) 
patch -p0  vsftpd-drop-newpid-from-clone.patch
cd vsftpd-3.0.2/
dpkg-buildpackage -us -uc -nc
cd ../

You'll get the compiled .deb in the directory.
Remove previous installed version of vsftpd on your system and install the 
brand new patched one.
sudo apt-get remove vsftpd 
sudo dpkg -i vsftpd_patched.deb

You can remove the directory where you built the package after
installation.

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

Title:
  Login is not possible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+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 1160372] Re: Login is not possible

2013-05-01 Thread Vincent DAVY
Note : you need to build on a 64 bits arch to get a 64bits version of the 
package and a 32 bits arch for 32bits one.
I used VM for this.

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

Title:
  Login is not possible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+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 1173595] Re: Unmatched dovecot lines in logwatch

2013-05-01 Thread John Stark
** Changed in: logwatch (Ubuntu)
   Status: Incomplete = New

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

Title:
  Unmatched dovecot lines in logwatch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1173595/+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 1173595] Re: Unmatched dovecot lines in logwatch

2013-05-01 Thread John Stark
Yes, there is a dovecot script in the logwatch directory, which is
partially parsing the dovecot log lines. Unfortunatelly it doesn't seem
to understand the lines I have posted. I am not sure why this is
happening, but I have installed both dovecot and logwatch per apt-get,
so it should not cause such problems.

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

Title:
  Unmatched dovecot lines in logwatch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1173595/+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 1175049] Re: Please merge squid3 3.3.3-2 (main) from Debian unstable (main)

2013-05-01 Thread H.-Dirk Schmitt
I tried a backport in ppa:dirk-computer42/c42-backport  against precise.
It builds with the additional backported packages libecap.

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

** Also affects: precise-backports
   Importance: Undecided
   Status: New

-- 
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/1175049

Title:
  Please merge squid3 3.3.3-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/precise-backports/+bug/1175049/+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 1175003] Re: Sync pep8 1.4.4-1 (main) from Debian unstable (main)

2013-05-01 Thread Benjamin Drung
This bug was fixed in the package pep8 - 1.4.4-1
Sponsored for Adam Gandelman (gandelman-a)

---
pep8 (1.4.4-1) unstable; urgency=low

  * New upstream release. (Closes: #694443)

 -- David Watson dwat...@debian.org  Wed, 06 Mar 2013 13:52:24 +

** Changed in: pep8 (Ubuntu)
   Status: New = Fix Released

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

Title:
  Sync pep8 1.4.4-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pep8/+bug/1175003/+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 1175049] Re: Please merge squid3 3.3.3-2 (main) from Debian unstable (main)

2013-05-01 Thread H.-Dirk Schmitt
Just a note: Squid 3.3 (3.2) is needing some configuration tweaks :

Especially:

* Helper name  changes: 
http://www.squid-cache.org/Versions/v3/3.2/RELEASENOTES.html#toc2.6
* Changes to existing tags: 
http://www.squid-cache.org/Versions/v3/3.2/RELEASENOTES.html#toc3.2

-- 
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/1175049

Title:
  Please merge squid3 3.3.3-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/precise-backports/+bug/1175049/+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 1113821] Re: libvirt-bin deletes /etc/dnsmasq.d/libvirt-bin on upgrade

2013-05-01 Thread Serge Hallyn
@Adam,

The raring-proposed version of libvirt-bin properly sets up
/etc/dnsmasq.d/libvirt-bin, and remove/install does not cause the file
to be dropped.  (fix verified)

-- 
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/1113821

Title:
  libvirt-bin deletes /etc/dnsmasq.d/libvirt-bin on upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1113821/+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 1173595] Re: Unmatched dovecot lines in logwatch

2013-05-01 Thread Robie Basak
** Changed in: logwatch (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  Unmatched dovecot lines in logwatch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1173595/+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 1175049] Re: Please merge squid3 3.3.3-2 (main) from Debian unstable (main)

2013-05-01 Thread Robie Basak
** Changed in: squid3 (Ubuntu)
   Status: New = Triaged

** Changed in: squid3 (Ubuntu)
   Importance: Undecided = Medium

-- 
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/1175049

Title:
  Please merge squid3 3.3.3-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/precise-backports/+bug/1175049/+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 1087183] Re: MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'

2013-05-01 Thread Scott Moser
Some context.  The situation is not at all simple. Here are some things to
think about:

a.) debian manual says what you see in /etc/hosts is actually *correct*

http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_hostname_resolution

Ie, there *should* be an entry for 127.0.1.1 pointing to the system's
hostname.  This is done so that 'hostname' always resolves to
something that can be reached (even in the absense of dns or
networking).

b.) relying on dns provided by maas assumes that connection to maas's dhcp
server is present even after installation.  Ideally the instance once
deployed could be detached from the management network entirely.

This is very much a future maas feature, but it is something to think
about.

c.) 'hostname --fqdn' as juju (and other things use) should not be used.
From the man page of 'hostname'
 | If a machine has multiple network interfaces/addresses or is used
 | in a mobile environment, then it may either have multiple
 | FQDNs/domain names or none at all. Therefore avoid using
 | hostname --fqdn, hostname --domain and dnsdomain‐ name.
 ..
 | -f, --fqdn, --long
 | Display the FQDN (Fully Qualified Domain Name).  A FQDN
 | consists of a short host name and the DNS domain name. Unless
 | you are using bind or NIS for host lookups you can change the
 | FQDN and the DNS domain name (which is part of the FQDN) in the
 | /etc/hosts file. See the warnings in section THE FQDN above, and
 | avoid using this option; use hostname --all-fqdns instead.

d.) There are really at least 2 different hostnames that matter
local-hostname:
  Maas has this concept, and provides 'local-hostname' to cloud-init
  in meta-data.  Juju's MAAS provider assumes that it can reach
  machines via the 'local-hostname'. ('juju ssh service/0' for
  example).

  That assumption might not be true.  While MAAS nodes (and thus the
  juju bootstrap node) are likely to be able to talk to each other via
  local-hostnames, it isn't true that other resources can.

public-hostname:
  In EC2, there is a 'public-hostname' that is resolves to the IPv4
  globally routeable address.  This makes sense to use in some cases,
  but as it is something like ec2-54-234-174-100.compute-1.amazonaws.com
  Its probably not something that a user would say
  Check out my new website at 
http://ec2-54-234-174-100.compute-1.amazonaws.com;

extrenally-provided-hostname:
  This is what the user would actually direct people to.

e.) for reference, 'manage_etc_hosts' first came into MAAS in revno 395
(my commit) due to bug 972067
I have a long winded bug report there
https://bugs.launchpad.net/maas/+bug/972067

Mainly the above is just a brain dump, and a list of things that have to
be thought about.

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

Title:
  MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1087183/+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 1138905] Re: managesieve segfault

2013-05-01 Thread Hendrik Haddorp
This issue seems to be resolved in the version shipping in 13.04.

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

Title:
  managesieve segfault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1138905/+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 1175049] Re: Please merge squid3 3.3.3-2 (main) from Debian unstable (main)

2013-05-01 Thread H.-Dirk Schmitt
Backported package (from  ppa:dirk-computer42/c42-backport) works
without any problems for me.

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

-- 
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/1175049

Title:
  Please merge squid3 3.3.3-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/precise-backports/+bug/1175049/+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


[Blueprint servercloud-s-juju-charm-testing] Juju Charm Testing

2013-05-01 Thread Antonio Rosales
Blueprint changed by Antonio Rosales:

Whiteboard changed:
  Discussion:
   *Bug submission on charm failure.
   *Define a process around how charm maintainers respond to test failures and 
subsequent bugs. Can a user run a manual test and submit the test back to the 
bug report to update testing status to green.
   *Enable Autocharm tester to be more resilient against provider failures, and 
Jenkins usage.
   simulate provider failure, and be able to recover: $ juju ssh MACHINE 
sudo shutdown now
   * Define WIs to execute auto charm testing on Go.
   * Continuous Integration (also will help with gating on charm commits)
   * Juju Testing Blogging
   * Juju testing communication to Juju lists.
   * Work on integrating/fixing Charm runner (graph testing/ dependency/env set 
up testing).
  
  Add a Jenkins workflow to run a charm or a set of charms in the following LXC 
environments:
   -raring container on raring host
   -raring container on precise host
   -precise container on raring host
   -precise container on precise host
  
  Reference Links:
   *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html
   * Charm Test Spec [source] 
http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst
   * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester
   * Charm Runner: https://launchpad.net/charmrunner
   * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/
  
  [USER STORIES]
  [ASSUMPTIONS]
  [RISKS]
  [IN SCOPE]
  [OUT OF SCOPE]
  [USER ACCEPTANCE]
  [RELEASE NOTE/BLOG]
  
  (Needs spec and WI definition) -[a.rosales; 12-DEC-2012]
  
  === UDS 1303 Notes ===
  Pad: http://pad.ubuntu.com/uds-1303-servercloud-r-juju-charm-testing
  
  Question:
  Is there a way in meta-data to explicitly state provider support.
  -Example: Ceph: Does cloud provider have block support
  -More broadly stated does the cloud provider have the capabilities the 
charm needs
  
  Idea:
    -In charm testing status be able to show that a charm failure can be a 
result of the provider not providing the needed capabilities, ie the Ceph charm 
fails on a provider because it does not support object store.
    -Make interface usage more verbose in the charm description.
    -Need a rule/spec on how a interface should be implemented
  -Need to investigate possible enforment of interfaces
   -**Have the testing framework iterate through the operational deployment 
requirments.
  
  Interfaces doc link broken:
    -Example: http://jujucharms.com/interfaces/ceph-client  Interface doc link 
broken:
    https://juju.ubuntu.com/Interfaces/ceph-client -- broken
  
  Meta-language testing (http://paste.ubuntu.com/5588570/):
  
  Lanugage suggestions:
  http://lettuce.it/
  http://cukes.info/
+ 
+ Charm-Runner integration:
+  - https://launchpad.net/juju-deployer
+ 
+ Wrap Go/Py juju client status:
+  - https://launchpad.net/python-jujuclient

-- 
Juju Charm Testing
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charm-testing

-- 
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 1175295] [NEW] open-vm-dkms 2012.12.26-958366-0ubuntu3: open-vm-tools kernel module failed to build

2013-05-01 Thread Fabio Marconi
Public bug reported:

Release of Ubuntu:13.10
Package Version:
Expected Results:
Actual Results:


Hallo
This popup at the startup of the session, system works.

Thanks
Fabio

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: open-vm-dkms 2012.12.26-958366-0ubuntu3
ProcVersionSignature: Ubuntu 3.9.0-0.3-generic 3.9.0
Uname: Linux 3.9.0-0-generic x86_64
ApportVersion: 2.10-0ubuntu1
Architecture: amd64
DKMSKernelVersion: 3.9.0-0-generic
Date: Wed May  1 20:17:21 2013
InstallationDate: Installed on 2012-10-12 (201 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20121011)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 2012.12.26-958366-0ubuntu3
SourcePackage: open-vm-tools
Title: open-vm-dkms 2012.12.26-958366-0ubuntu3: open-vm-tools kernel module 
failed to build
UpgradeStatus: Upgraded to saucy on 2013-05-01 (0 days ago)

** Affects: open-vm-tools (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
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/1175295

Title:
  open-vm-dkms 2012.12.26-958366-0ubuntu3: open-vm-tools kernel module
  failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1175295/+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 1175295] Re: open-vm-dkms 2012.12.26-958366-0ubuntu3: open-vm-tools kernel module failed to build

2013-05-01 Thread Nate Muench (Mink)
** Branch linked: lp:~n-muench/ubuntu/saucy/open-vm-tools/open-vm-tools
.april-update

-- 
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/1175295

Title:
  open-vm-dkms 2012.12.26-958366-0ubuntu3: open-vm-tools kernel module
  failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1175295/+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 1175295] Re: open-vm-dkms 2012.12.26-958366-0ubuntu3: open-vm-tools kernel module failed to build

2013-05-01 Thread Nate Muench (Mink)
In progress.  I've linked prep branch.  It'll be slow work until we get
the LiveCD start coming out, and also it's still early in the
development cycle, so I'm taking my time.

I still have to test the packaging, but the prep branch isn't mature
enough to start auto building it, since the (planned) major changes
haven't been pushed yet.

** Changed in: open-vm-tools (Ubuntu)
 Assignee: (unassigned) = Nate Muench (Mink) (n-muench)

** Changed in: open-vm-tools (Ubuntu)
   Status: New = In Progress

-- 
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/1175295

Title:
  open-vm-dkms 2012.12.26-958366-0ubuntu3: open-vm-tools kernel module
  failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1175295/+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 1155652] Re: cloud-final is not executed during creation of a container from template ubuntu-cloud

2013-05-01 Thread Serge Hallyn
*** This bug is a duplicate of bug 1124384 ***
https://bugs.launchpad.net/bugs/1124384

** This bug has been marked a duplicate of bug 1124384
   Configuration reload clears event that others jobs may be waiting on

-- 
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/1155652

Title:
  cloud-final is not executed during creation of a container from
  template ubuntu-cloud

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1155652/+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 1173070] Re: package vsftpd 3.0.2-1ubuntu1 failed to install/upgrade: package vsftpd is not ready for configuration cannot configure (current status `half-installed')

2013-05-01 Thread Serge Hallyn
Thanks for submitting this bug.  Based on dmesg, it looks like the
vsftpd executable was deleted before the attempt to remove the package.
If I understand correctly, you have now successfully removed vsftpd, and
dont' care to reinstall it.  I'll go ahed and mark the bug invalid
(meaning unreproducible, so we cannot get more information), please
reply if that is not correct.

** Changed in: vsftpd (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  package vsftpd 3.0.2-1ubuntu1 failed to install/upgrade: package
  vsftpd is not ready for configuration  cannot configure (current
  status `half-installed')

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1173070/+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 1100843] Re: Live Migration Causes Performance Issues

2013-05-01 Thread Jonathan Jefferson
I used this handy tool to run system call preliminary benchmarks: 
http://code.google.com/p/byte-unixbench/

 In a nutshell, what I found is a confirmation that live migration does indeed 
degrade performance on precise KVM. 
 I hope the below results help narrow down this critical problem to eventually 
have it resolved in 12.04 LTS version.

detail results:
Compiled the benchmarking tool and then:
root@sample-vm:~/UnixBench# ./Run syscall

Output:

** before live-migration **

Benchmark Run: Wed May 01 2013 20:29:54 - 20:32:04
1 CPU in system; running 1 parallel copy of tests
System Call Overhead4177612.4 lps   (10.0 s, 7 samples)
System Benchmarks Partial Index  BASELINE   RESULTINDEX
System Call Overhead  15000.04177612.4   2785.1
   
System Benchmarks Index Score (Partial Only) 2785.1


** after live-migration **

Benchmark Run: Wed May 01 2013 20:35:16 - 20:37:26
1 CPU in system; running 1 parallel copy of tests
System Call Overhead3065118.3 lps   (10.0 s, 7 samples)
System Benchmarks Partial Index  BASELINE   RESULTINDEX
System Call Overhead  15000.03065118.3   2043.4
   
System Benchmarks Index Score (Partial Only) 2043.4


XML domain dump:

  memory1048576/memory
  currentMemory1048576/currentMemory
  vcpu1/vcpu
  cputune
shares1024/shares
  /cputune
  os
type arch='x86_64' machine='pc-1.0'hvm/type
boot dev='hd'/
  /os
  features
acpi/
  /features
  clock offset='utc'/
  on_poweroffdestroy/on_poweroff
  on_rebootrestart/on_reboot
  on_crashdestroy/on_crash
  devices
emulator/usr/bin/kvm/emulator
disk type='file' device='disk'
  driver name='qemu' type='qcow2'/
  source file='HIDEME'/
  target dev='vda' bus='virtio'/
  alias name='virtio-disk0'/
  address type='pci' domain='0x' bus='0x00' slot='0x04' 
function='0x0'/
/disk
disk type='file' device='cdrom'
  driver name='qemu' type='raw'/
  source file='HIDEME'/
  target dev='hda' bus='ide'/
  readonly/
  alias name='ide0-0-0'/
  address type='drive' controller='0' bus='0' unit='0'/
/disk
controller type='ide' index='0'
  alias name='ide0'/
  address type='pci' domain='0x' bus='0x00' slot='0x01' 
function='0x1'/
/controller

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

Title:
  Live Migration Causes Performance Issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1100843/+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 1172981] Re: clamav 0.97.8 security update

2013-05-01 Thread Seth Arnold
** Description changed:

  ClamAV has released 0.97.8 to address several security issues:
  http://blog.clamav.net/2013/04/clamav-0978-has-been-released.html
  
- CVEs are not currently assigned.
+ CVE-2013-2020 and CVE-2013-2021.

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-2020

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-2021

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

Title:
  clamav 0.97.8 security update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1172981/+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


[Blueprint servercloud-s-cloud-archive] Ubuntu Cloud Archive Status Check

2013-05-01 Thread Adam Gandelman
Blueprint changed by Adam Gandelman:

Assignee: (none) = Adam Gandelman

-- 
Ubuntu Cloud Archive Status Check
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive

-- 
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