[Bug 1288245] Re: mox is needed in requirements
Agreed. Thank you for your work! ** Changed in: horizon Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1288245 Title: mox is needed in requirements To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1288245/+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 1290743] [NEW] [FFE] Pull Xen-4.4 into Trusty
Public bug reported: Normally we would go with Xen-4.3 (as it was in Saucy) for the LTS. However the 4.4 release (which happened yesterday, Mar-10) is supposed to improve support for Arm platforms a lot (hypervisor ABI is now declared stable). Also libvirt/xl integration is supposed to be improved much and last but not least the number of event channels was raised substantially which lifts the limitation of concurrent guests a lot. http://blog.xen.org/index.php/2014/03/10/xen-4-4-released/ ** Affects: xen (Ubuntu) Importance: High Assignee: Stefan Bader (smb) Status: Confirmed ** Description changed: Normally we would go with Xen-4.3 (as it was in Saucy) for the LTS. However the 4.4 release (which happened yesterday, Mar-10) is supposed to improve support for Arm platforms a lot (hypervisor ABI is now declared stable). Also libvirt/xl integration is supposed to be improved much and last but not least the number of event channels was raised substantially which lifts the limitation of concurrent guests a lot. + + http://blog.xen.org/index.php/2014/03/10/xen-4-4-released/ ** Changed in: xen (Ubuntu) Importance: Undecided = High ** Changed in: xen (Ubuntu) Assignee: (unassigned) = Stefan Bader (smb) ** Changed in: xen (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1290743 Title: [FFE] Pull Xen-4.4 into Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1290743/+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 1284248] Re: [mir] python-hplefthandclient
** Changed in: python-hplefthandclient (Ubuntu) Status: Incomplete = In Progress ** Changed in: python-hplefthandclient (Ubuntu) Assignee: (unassigned) = James Page (james-page) ** Also affects: python-hplefthandclient (Ubuntu Trusty) Importance: Undecided Assignee: James Page (james-page) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-hplefthandclient in Ubuntu. https://bugs.launchpad.net/bugs/1284248 Title: [mir] python-hplefthandclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-hplefthandclient/+bug/1284248/+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 1290810] [NEW] please create a default /etc/swift/proxy-server.conf
Public bug reported:
There are default config files for
{account,container,object}-server.conf, but not for proxy-server.conf.
It would simplify things if it was, since most of the file is just fine
for at least simple workflows. I guess at the moment people just
copypaste it from instruction pages like http://www.hpcloud.com/blog
/setting-single-node-openstack-storage-server-part-1 ?
I use this one, where the only variable that realistically gets changed
is super_admin_key:
- 8
[DEFAULT]
bind_port = 8080
log_facility = LOG_LOCAL1
[pipeline:main]
pipeline = healthcheck cache swauth proxy-server
[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true
[filter:swauth]
use = egg:swauth#swauth
set log_name = swauth
super_admin_key = swauthkey
default_swift_cluster = local#http://127.0.0.1:8080/v1
[filter:healthcheck]
use = egg:swift#healthcheck
[filter:cache]
use = egg:swift#memcache
- 8
It would of course be even better if these options had implicit defaults
so that they wouldn't need a configuration file in the first place. But
I tried that (e. g. dropping the various [filter:*] or [app:proxy-
server] sections), and it doesn't work.
** Affects: swift (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to swift in Ubuntu.
https://bugs.launchpad.net/bugs/1290810
Title:
please create a default /etc/swift/proxy-server.conf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1290810/+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 1290813] [NEW] /etc/swift/container-server.conf is missing container-sync section
Public bug reported: With the default /etc/swift/container-server.conf, after adding devices/port etc. to [DEFAULT], swift fails with Unable to find container-sync config section in /etc/swift/container- server.conf Adding an empty section with that name fixes things. This should be there by default, or better yet, it should not fail if the section is not present as it doesn't need to have actual contents anyway. ** Affects: swift (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to swift in Ubuntu. https://bugs.launchpad.net/bugs/1290813 Title: /etc/swift/container-server.conf is missing container-sync section To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1290813/+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 1290448] Re: Invalid Opcode when running samba-tool domain exportkeytab
As this bug stops an other application using the Kerberos details stored in the Samba directory, it is quite a show-stopper for the Trusty release. Is there anything I can tag this bug with or anyone I should notify in an attempt to get 4.1.5 pulled from Jessie for the Trusty release? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1290448 Title: Invalid Opcode when running samba-tool domain exportkeytab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1290448/+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 1290686] Re: Sync libstatgrab 0.90-1.1 (main) from Debian unstable (main)
This bug was fixed in the package libstatgrab - 0.90-1.1 Sponsored for Jackson Doak (noskcaj) --- libstatgrab (0.90-1.1) unstable; urgency=high * Non-maintainer upload. * Fix tests causing FTBFS in some arches due to failing to find /etc/mtab fix-ftbfs-734368.patch (Closes: #734368) -- Manuel A. Fernandez Montecelo m...@debian.org Sat, 08 Mar 2014 16:42:36 + ** Changed in: libstatgrab (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libstatgrab in Ubuntu. https://bugs.launchpad.net/bugs/1290686 Title: Sync libstatgrab 0.90-1.1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libstatgrab/+bug/1290686/+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 1290817] [NEW] Please merge migrate 0.8.5-1 (main) from Debian unstable
Public bug reported: Need migration from 0.8.2-3 to 0.8.5-1 ** Affects: migrate (Ubuntu) Importance: Wishlist Assignee: Yolanda Robla (yolanda.robla) Status: In Progress ** Changed in: migrate (Ubuntu) Importance: Undecided = Wishlist ** Changed in: migrate (Ubuntu) Status: New = In Progress ** Changed in: migrate (Ubuntu) Assignee: (unassigned) = Yolanda Robla (yolanda.robla) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to migrate in Ubuntu. https://bugs.launchpad.net/bugs/1290817 Title: Please merge migrate 0.8.5-1 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/migrate/+bug/1290817/+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 1290819] [NEW] Update the 7.x trunk for 12.04LTS
You have been subscribed to a public bug: Will there be an update to the package 7.0.26-1ubuntu1.2 for precise 12.04 with the bug fixed in last weeks USN-2130-1 http://www.ubuntu.com/usn/usn-2130-1/ For now only the 6.x trunk has been updated for precise: Ubuntu 12.04 LTS: libtomcat6-java 6.0.35-1ubuntu3.4 ** Affects: tomcat7 (Ubuntu) Importance: Undecided Status: New -- Update the 7.x trunk for 12.04LTS https://bugs.launchpad.net/bugs/1290819 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 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 1290819] [NEW] Update the 7.x trunk for 12.04LTS
Public bug reported: Will there be an update to the package 7.0.26-1ubuntu1.2 for precise 12.04 with the bug fixed in last weeks USN-2130-1 http://www.ubuntu.com/usn/usn-2130-1/ For now only the 6.x trunk has been updated for precise: Ubuntu 12.04 LTS: libtomcat6-java 6.0.35-1ubuntu3.4 ** Affects: tomcat7 (Ubuntu) Importance: Undecided Status: New ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-4286 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-4322 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-0050 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 in Ubuntu. https://bugs.launchpad.net/bugs/1290819 Title: Update the 7.x trunk for 12.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1290819/+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 1290819] Re: Update the 7.x trunk for 12.04LTS
** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-2071 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-2067 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 in Ubuntu. https://bugs.launchpad.net/bugs/1290819 Title: Update the 7.x trunk for 12.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1290819/+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 1284248] Re: [mir] python-hplefthandclient
Michael I've patched and enabled the testsuite during the package build. Currently in -proposed. ** Changed in: python-hplefthandclient (Ubuntu Trusty) Status: In Progress = New ** Changed in: python-hplefthandclient (Ubuntu Trusty) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-hplefthandclient in Ubuntu. https://bugs.launchpad.net/bugs/1284248 Title: [mir] python-hplefthandclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-hplefthandclient/+bug/1284248/+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 1284248] Re: [mir] python-hplefthandclient
This bug was fixed in the package python-hplefthandclient - 1.0.1-1ubuntu1 --- python-hplefthandclient (1.0.1-1ubuntu1) trusty; urgency=medium * d/control,rules,d/p/fixup-unit-tests.patch: Fixup mock LHOS server, execute unit tests during package build (LP: #1284248). -- James Page james.p...@ubuntu.com Tue, 11 Mar 2014 12:20:54 + ** Changed in: python-hplefthandclient (Ubuntu Trusty) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-hplefthandclient in Ubuntu. https://bugs.launchpad.net/bugs/1284248 Title: [mir] python-hplefthandclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-hplefthandclient/+bug/1284248/+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 1182905] Re: charm-tools installs juju-0.7
** Changed in: charm-tools (Ubuntu Precise) Status: Triaged = Fix Committed ** Changed in: charm-tools (Ubuntu Precise) Assignee: (unassigned) = Marco Ceppi (marcoceppi) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1182905 Title: charm-tools installs juju-0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1182905/+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 1284248] Re: [mir] python-hplefthandclient
** Changed in: python-hplefthandclient (Ubuntu Trusty) Status: Fix Released = New ** Changed in: python-hplefthandclient (Ubuntu Trusty) Assignee: James Page (james-page) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-hplefthandclient in Ubuntu. https://bugs.launchpad.net/bugs/1284248 Title: [mir] python-hplefthandclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-hplefthandclient/+bug/1284248/+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 1290848] [NEW] maas-enlist reports success when in fact it fails the enlistment process
Public bug reported: This is a side effect of bug 1289485. As shown in http://people.canonical.com/~matsubara/maas-declared-node-failing-02.png maas-enlist reports success enlisting the node but it ends up failing. This was tested with 1.5+bzr1977+2110+246~ppa0~ubuntu14.04.1 ** Affects: maas-enlist (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas-enlist in Ubuntu. https://bugs.launchpad.net/bugs/1290848 Title: maas-enlist reports success when in fact it fails the enlistment process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas-enlist/+bug/1290848/+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 1284248] Re: [mir] python-hplefthandclient
** Changed in: python-hplefthandclient (Ubuntu Trusty) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-hplefthandclient in Ubuntu. https://bugs.launchpad.net/bugs/1284248 Title: [mir] python-hplefthandclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-hplefthandclient/+bug/1284248/+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 1182905] Re: charm-tools installs juju-0.7
** Description changed: This is what happened to me: - * Configured environments.yaml for AWS. - * I bootstrapped Juju, deployed wordpress and mysql and related them. I exposed wordpress and hit it in the browser. It worked. Woo! - * While doing this I decided to install charm-tools - * Now when I use Juju it errors requiring me to configure additional parts of environments.yaml + * Configured environments.yaml for AWS. + * I bootstrapped Juju, deployed wordpress and mysql and related them. I exposed wordpress and hit it in the browser. It worked. Woo! + * While doing this I decided to install charm-tools + * Now when I use Juju it errors requiring me to configure additional parts of environments.yaml Now, at first it only required me to configure a default-series for each provider, which is a no-brainer, but then it asked for maas-oauth config. This completely stopped me in my tracks. I don't care about the other providers as I have already got my AWS provider configured and up and running, and it put Juju in a position where it stopped working for me due to the missing configuration. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: charm-tools 0.3+151-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2 Uname: Linux 3.9.0-2-generic i686 ApportVersion: 2.10.1-0ubuntu1 Architecture: i386 Date: Wed May 22 06:49:59 2013 InstallationDate: Installed on 2013-05-05 (17 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130504) MarkForUpload: True PackageArchitecture: all SourcePackage: charm-tools UpgradeStatus: No upgrade log present (probably fresh install) + + [Impact] + + * Users who install juju-core, then install charm-tools will have their installations broken in precise + * This fix decouples juju from charm-tools as a Recommended package to a Suggested package. This also makes juju-core package a satisfactory Suggestion in addition to juju + + [Test Case] + + * On precise, install juju-core and juju-local using the preferred installation method, from cloud-tools pocket archive. + * Run `juju init` to create environments.yaml + * Switch to local environment, `juju switch local` + * Verify version of juju installed, `juju version` + * Bootstrap with `sudo juju bootstrap` + * Deploy a charm, `juju deploy ubuntu` + * Install charm-tools package from precise archives + * Run `juju version`, command should fail. + * Run `juju --version`, command should succeed with a verion 1.0.0 + * Attempt to connect to environment with `juju status`, should fail + + [Regression Potential] + + * This simply changes the the control file to lower priority of + Recommended packages. + + [Other Info] + + * This has been patched and updated in Saucy and Trusty as of version 1.0.0 of charm-tools. However, 1.0.0 breaks backwards compatibility with 0.3 packaging wise. charm-helper-sh and charm-helper-python are no longer supported and subsequently dropped from 1.0.0 version of charm-tools and it's packaging. Otherwise I likely would have requested a backport of 1.0.0 to precise. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1182905 Title: charm-tools installs juju-0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1182905/+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 1290810] Re: please create a default /etc/swift/proxy-server.conf
I now learned a bit more about the proxy configuration. swauth is broken for me as it always returns 127.0.0.1 storage URLs even if I put the public IP into default_swift_cluster, so I moved away from it to tempauth. So apparently there's quite a bit more variability in this than the initial tutorials suggest, so closing. ** Changed in: swift (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to swift in Ubuntu. https://bugs.launchpad.net/bugs/1290810 Title: please create a default /etc/swift/proxy-server.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1290810/+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 1182905] Re: charm-tools installs juju-0.7
For Precise, I've spoken to Marco and we came up with a minimal diff, that just drops the Recommends to a Suggests. Uploaded. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1182905 Title: charm-tools installs juju-0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1182905/+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 1290743] Re: [FFE] Pull Xen-4.4 into Trusty
Rebuild of qemu and libvirt will be required to depend on the correct libxl. Especially libvirt which otherwise segfaults when launching a guest with the libxl driver. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1290743 Title: [FFE] Pull Xen-4.4 into Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1290743/+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 1290743] Re: [FFE] Pull Xen-4.4 into Trusty
Test builds uploaded to https://launchpad.net/~smb/+archive/xen -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1290743 Title: [FFE] Pull Xen-4.4 into Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1290743/+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 1284248] Re: [mir] python-hplefthandclient
** Branch linked: lp:ubuntu/python-hplefthandclient -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-hplefthandclient in Ubuntu. https://bugs.launchpad.net/bugs/1284248 Title: [mir] python-hplefthandclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-hplefthandclient/+bug/1284248/+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 1290920] [NEW] fails to start container with local provider with non-default LXC path
Public bug reported:
I tried to use the local provider according to
https://juju.ubuntu.com/docs/config-local.html, in particular
https://juju.ubuntu.com/docs/config-LXC.html . James Page already
informed me that the documentation is outdated for trusty, and one needs
to drop the sudo from juju bootstrap. With that, bootstrapping fails
due to not being able to start the container, when using a non-default
LXC path (I can't use /var/lib/lxc, my root partition is too small).
I initially experienced that on my normal trusty workstation, but I
reproduced in a current and pristine trusty cloud-image VM (I just ran
run-adt-test -sUl from lp:auto-package-testing).
$ sudo apt-get install juju-local
Now set up LXC for a different container path:
$ sudo mkdir /srv/lxc
$ echo lxc.lxcpath = /srv/lxc | sudo tee /etc/lxc/lxc.conf
Note that this works just fine with all the LXC tools.
$ juju generate-config
Now create a different juju root:
$ sudo mkdir /srv/juju; sudo chown ubuntu:ubuntu /srv/juju
$ sed -i '/root-dir/ { s/# //; s_:.*$_: /srv/juju_ }' .juju/environments.yaml
$ juju switch local
$ juju bootstrap
Logging to /home/ubuntu/.juju/local/log/cloud-init-output.log on remote host
Starting MongoDB server (juju-db-ubuntu-local)
Bootstrapping Juju machine agent
Starting Juju machine agent (juju-agent-ubuntu-local)
So far so good:
$ juju status
environment: local
machines:
0:
agent-state: started
agent-version: 1.17.4.1
dns-name: localhost
instance-id: localhost
series: trusty
services: {}
There are no actual containers running (sudo lxc-ls --fancy), but that's
the same as with using the default /var/lib/lxc/.
$ juju deploy mysql
Added charm cs:precise/mysql-36 to the environment.
After a while I see:
$ juju status
environment: local
machines:
0:
agent-state: started
agent-version: 1.17.4.1
dns-name: localhost
instance-id: localhost
series: trusty
1:
agent-state-info: '(error: error executing lxc-start: command get_cgroup
failed
to receive response)'
instance-id: pending
series: precise
services:
mysql:
charm: cs:precise/mysql-36
exposed: false
relations:
cluster:
- mysql
units:
mysql/0:
agent-state: pending
machine: 1
In .juju/local/log/machine-0.log I see:
2014-03-11 15:48:49 WARNING juju.worker.instanceupdater updater.go:231 cannot
get instance info for instance : no instances found
2014-03-11 15:49:16 ERROR juju.container.lxc lxc.go:134 container failed to
start: error executing lxc-start: command get_cgroup failed to receive
response
2014-03-11 15:49:16 ERROR juju.provisioner provisioner_task.go:403 cannot start
instance for machine 1: error executing lxc-start: command get_cgroup
failed to receive response
(Attaching the whole file)
Other than that, .juju/local/log/ contains a broken symlink all-
machines.log - /var/log/juju-ubuntu-local/all-machines.log and cloud-
init-output.log without any error messages.
Note that this works with the default /var/lib/lxc/ path.
** Affects: juju (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: .juju/local/log/machine-0.log
https://bugs.launchpad.net/bugs/1290920/+attachment/4018339/+files/machine-0.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1290920
Title:
fails to start container with local provider with non-default LXC path
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1290920/+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 1289564] Re: failure to start message should be explicit about non-VMware hypervisor
** Branch linked: lp:ubuntu/trusty-proposed/open-vm-tools -- 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/1289564 Title: failure to start message should be explicit about non-VMware hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1289564/+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 1290920] Re: fails to start container with local provider with non-default LXC path
In that situation I see: $ sudo lxc-ls --fancy NAMESTATEIPV4 IPV6 AUTOSTART -- ubuntu-local-machine-1 STOPPED - - YES Trying to boot it manually reveals the problem: $ sudo lxc-start -n ubuntu-local-machine-1 lxc-start: No such file or directory - failed to mount '/home/ubuntu/.juju/local/log' on '/usr/lib/x86_64-linux-gnu/lxc/var/log/juju' lxc-start: failed to setup the mount entries for 'ubuntu-local-machine-1' lxc-start: failed to setup the container lxc-start: invalid sequence number 1. expected 2 lxc-start: failed to spawn 'ubuntu-local-machine-1' For testing I commented out the lxc.mount.entry for /home/ubuntu/.juju/local/log in /srv/lxc/ubuntu-local-machine-1/config, and tried to start the container again. It boots now, and starts cloud- init. I can't log in though, as ubuntu/ubuntu does not work and I don't know which account it created, so I stopped the container manually. At this point I don't know how to tell juju to re-poke that instance to continue the setup. Supposedly this is due to some AppArmor restriction? I don't see any REJECTs in dmesg, but failing to bind-mount with a non-default container path sounds like that? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1290920 Title: fails to start container with local provider with non-default LXC path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1290920/+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 1244438] Re: EOL notification system required for HWE kernels in LTSs
** Description changed: We need to have some mechanism to allow us to record that you have an - EOL kernel installed which will no longer recieve updates. + EOL kernel installed which will no longer receive updates. For example for the kernel when a kernel is going EOL the last upload should include an appropriate file: - /var/lib/update-notifier/kernel-eol + /var/lib/update-notifier/kernel-eol We need to coordinate this with the notifier itself to ensure it is displayed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1244438 Title: EOL notification system required for HWE kernels in LTSs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1244438/+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 1289564] Re: failure to start message should be explicit about non-VMware hypervisor
This bug was fixed in the package open-vm-tools - 2:9.4.0-1280544-5ubuntu5 --- open-vm-tools (2:9.4.0-1280544-5ubuntu5) trusty; urgency=low * Change startup message failure to state the reason why open-vm-tools does not start on non-VMware hypervisors (LP: #1289564). -- Ben Howard ben.how...@ubuntu.com Fri, 07 Mar 2014 17:21:03 -0700 ** Changed in: open-vm-tools (Ubuntu) Status: In Progress = Fix Released -- 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/1289564 Title: failure to start message should be explicit about non-VMware hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1289564/+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 1244438] Re: EOL notification system required for HWE kernels in LTSs
So, if all these update notification things check a single semaphore file, say /var/lib/update-notifier/no-hwe-oel-warning, then the OEM people can drop that flag in place on a forced update, to avoid their users being notified of stack upgrades before they've validated the upgrade path. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1244438 Title: EOL notification system required for HWE kernels in LTSs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1244438/+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 1244438] Re: EOL notification system required for HWE kernels in LTSs
Should we include the name of the base OS in the semaphore, e.g. /var/lib/update-notifier/no-12.04-hwe-eol-warning ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1244438 Title: EOL notification system required for HWE kernels in LTSs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1244438/+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 1290331] Re: query_cache_* configuration not appropriate for all mysql alternatives
This bug was fixed in the package percona-xtradb-cluster-5.5 - 5.5.34-25.9+dfsg-0ubuntu3 --- percona-xtradb-cluster-5.5 (5.5.34-25.9+dfsg-0ubuntu3) trusty; urgency=medium * d/p/70_mysql_va_list.patch: Cherry pick patch from mysql-5.5 to ensure that va_list usage is portable, fixing FTBFS on armhf and arm64. -- James Page james.p...@ubuntu.com Tue, 11 Mar 2014 15:24:43 + ** Changed in: percona-xtradb-cluster-5.5 (Ubuntu Trusty) Status: Fix Committed = Fix Released -- 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/1290331 Title: query_cache_* configuration not appropriate for all mysql alternatives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1290331/+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 1195189] Re: tomcat7-instance-create instances not compatible with Eclipse
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tomcat7 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 in Ubuntu. https://bugs.launchpad.net/bugs/1195189 Title: tomcat7-instance-create instances not compatible with Eclipse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1195189/+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 1195189] Re: tomcat7-instance-create instances not compatible with Eclipse
Testing here, Eclipse reconized the instance when I created a symbolic link to the lib/ path. Maybe just adding the link to skel/ should solve it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 in Ubuntu. https://bugs.launchpad.net/bugs/1195189 Title: tomcat7-instance-create instances not compatible with Eclipse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1195189/+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 1290423] Re: maintainer scripts always run db_sync during upgrade
James, cinder also doesn't have logic to only issue db_sync if the connection is the default sqllite one. Should I check all OpenStack services to make sure they're using the right search key and are only issuing db_sync if the connection is the default sqllite one? ** Changed in: keystone (Ubuntu Trusty) Assignee: (unassigned) = Corey Bryant (corey.bryant) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1290423 Title: maintainer scripts always run db_sync during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1290423/+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 1254872] Re: libvirtError: Timed out during operation: cannot acquire state change lock
** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1254872 Title: libvirtError: Timed out during operation: cannot acquire state change lock To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1254872/+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 1254872] Re: libvirtError: Timed out during operation: cannot acquire state change lock
** Also affects: libvirt (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu) Importance: Undecided = High ** Changed in: libvirt (Ubuntu) Status: New = Fix Released ** Changed in: libvirt (Ubuntu Precise) Importance: Undecided = High ** Changed in: libvirt (Ubuntu Precise) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1254872 Title: libvirtError: Timed out during operation: cannot acquire state change lock To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1254872/+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 1157914] Re: time never catches up to reality after VM sleep
On Mar 11, 2014, at 04:54 AM, Serge Hallyn wrote: Thanks for filing this bug. I'd like to try to reproduce it but need a few more details. Can you tell us exactly how you set up the vm, how you start it, and how you initiate suspend? Is this all done through virt-manager? You say it is a vmware fusion vm - does that mean you started with a .vmdk of an appliance, converted it to qcow2 or raw, and are using that? If not, what does it mean? This is a Trusty guest running in VMware Fusion 6.0.2 on an OS X 10.9.2 host. Trusty was installed fresh some time ago and has been rolling updated ever since. When you quit Fusion, it suspends the VM. You can of course suspend the VM explicitly any other time. You can also take a disk snapshot and restore that snapshot at a later date. All of these exhibit the same symptom - the VM's time gets behind, sometimes by a long while, and it never catches up. If you go to System Settings (in Ubuntu of course) - Time Date, and look at Set time: then Automatically from the Internet is set. What this implies to me at least, is that the system will keep its time in sync with the network servers. I would thus expect that when the VM is resumed, it would eventually catch up either with the real time. What I think is happening is that this settings panel actually only has an effect at system boot time. Can you confirm whether this setting should periodically sync system time to the internet servers, or whether ntp must be installed in order to keep time in sync. ntp is *not* currently installed. I'm perfectly willing to accept that ntp is required in order for a suspended VM's time to resync with internet server time. If that's the case, then I think we have a design bug here - the Automatically from the Internet setting is either misleading, or should prompt to install ntp (maybe with panic 0 set?). At one point I think this did happen. However, if this setting is supposed to keep time in sync without ntp, then there's a functional bug here. I'm mostly trying to get verification on what expected behavior is. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1157914 Title: time never catches up to reality after VM sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1157914/+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 1157914] Re: time never catches up to reality after VM sleep
Thanks, Barry. So IIUC this has nothing to do with qemu, so I'm switching it to linux. Is it safe to assume that other VMs - other Ubuntu releases, or other distros, or windows, do not have this behavior? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: Incomplete = Invalid ** No longer affects: qemu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1157914 Title: time never catches up to reality after VM sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157914/+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 1216817] Re: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
** Changed in: nginx (Debian) Status: New = Confirmed -- 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/1216817 Title: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+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 1261873] Re: 'net usershare' returned error 255
The smb.conf provided by Cliff Carson in the comment #4 solved the same problem on 14.04 too -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1261873 Title: 'net usershare' returned error 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1261873/+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 1275649] Re: MAAS packaging doesn't include maas-generated named.conf.options.inside.maas file
** Changed in: maas (Ubuntu) Status: New = Confirmed -- 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/1275649 Title: MAAS packaging doesn't include maas-generated named.conf.options.inside.maas file To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1275649/+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 1290920] Re: fails to start container with local provider with non-default LXC path
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: juju (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1290920 Title: fails to start container with local provider with non-default LXC path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1290920/+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 1091780] Re: nova-network - iptables-restore v1.4.12: host/network `None' not found
[Expired for nova (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nova (Ubuntu) Status: Incomplete = Expired -- 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/1091780 Title: nova-network - iptables-restore v1.4.12: host/network `None' not found To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1091780/+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
