[Bug 685096] Re: USB Passthrough not working for Windows 7 guest
I can connect to network with qemu 2.0 with and win 7 pro 64bit guest. qemu-system-x86_64 -machine accel=kvm -smp 2 -m 1024 -net none -device usb-ehci,id=usb,bus=pci.0,addr=0x4 -device usb- host,vendorid=0x0b95,productid=0x772b,id=hostdev0,bus=usb.0 -usb -usbdevice tablet -hda /srv/rhev/virtual.qcow -soundhw hda -boot c Bus 007 Device 014: ID 0b95:772b ASIX Electronics Corp. Unfortunately there is lack of automation and documentation. Ideally you would use something like qemu-system-x86_64 -machine accel=kvm -smp 2 -m 1024 -net none -usb2 -usbdevice host:0b95:772b -usbdevice tablet -hda /srv/rhev/virtual.qcow -soundhw hda -boot c Tthe usb device info from Linux should be enough to determine if the device is to be connected to usb1 or usb2, right? ** Attachment added: Win 7 device manager https://bugs.launchpad.net/qemu/+bug/685096/+attachment/4129559/+files/screenshot-20140611122419.png -- 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/685096 Title: USB Passthrough not working for Windows 7 guest To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/685096/+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 1307614] Re: MAAS sometimes attempts to install to USB flash drive
Roderick, To quote the page you referenced: | Ubuntu Server (CLI) Installation | 300 MHz x86 processor | 192 MiB of system memory (RAM) | 1 GB of disk space | Graphics card and monitor capable of 640x480 | CD drive 1GB for server. so 2GB is *twice* the *recommended* (not required) amount. The point is that determining which disk is right is more about how the system will be used than anything else. Curtin allows the user via config to specify the drives (by device name) that are considered for installation. Admittedly, its not very dynamic, and requires knowledge of the how the system you're installing on, but simply: partitioning_commands: builtin: curtin block-meta --device=/dev/sdb simple That overrides the 'builtin' partitioning command (which is 'block-meta simple'). You can accomplish that through maas vi editing the configs that it sends to curtin. My argument boils down to this: The user is who knows what the right configuration is. Curtin did automatically choose a valid configuration. Coding a long list of hueristics to determine what the user wants is not ever going to satisfy all use case. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1307614 Title: MAAS sometimes attempts to install to USB flash drive To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1307614/+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 1297962] Re: [sru] Nova-compute doesnt start
** Changed in: nova Status: Fix Committed = Fix Released ** Changed in: nova Milestone: None = juno-1 -- 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/1297962 Title: [sru] Nova-compute doesnt start To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1297962/+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 1274772] Re: libvirt.txt in gate is full of error messages
** Changed in: nova Status: Fix Committed = Fix Released ** Changed in: nova Milestone: None = juno-1 -- 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/1274772 Title: libvirt.txt in gate is full of error messages To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1274772/+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 1328659] Re: import_boot_images task fails on utopic
I ran the tests again[1] with an updated packaging branch[2] which adds the syslinux-dev package as dependency but got another failure, this time a missing /usr/lib/syslinux/chain.c32 file. Looks like the path for that file changed on utopic's syslinux-common: ubuntu@utopic:~$ dpkg -L syslinux-common|grep chain /usr/lib/syslinux/modules/bios/chain.c32 /usr/lib/syslinux/modules/efi64/chain.c32 /usr/lib/syslinux/modules/efi32/chain.c32 /usr/share/doc/syslinux-common/txt/chain.txt.gz So I think there are two bugs here, one is the missing dependency, so import_boot_images can find the pxelinux.0 file. Another one is the hardcoded /usr/lib/syslinux path in provisioningserver/boot/pxe.py which ends up pointing to the wrong place on utopic. [1] http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-maas-manual/30/artifact/results/artifacts/maas-logs/var/log/maas/celery.log [2] lp:~matsubara/maas/syslinux-dev-dep-utopic ** Also affects: maas (Ubuntu) Importance: Undecided Status: New -- 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/1328659 Title: import_boot_images task fails on utopic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1328659/+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 1328659] Re: import_boot_images task fails on utopic
** Changed in: maas Status: New = Triaged ** Changed in: maas Importance: Undecided = Critical -- 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/1328659 Title: import_boot_images task fails on utopic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1328659/+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 1328958] [NEW] Local provider fails to bootstrap on utopic
Public bug reported: I'm trying to init and bootstrap the juju local provider on utopic. I keep getting a chown: invalid user error: max@eden:~$ rm -rf .juju max@eden:~$ juju init A boilerplate environment configuration file has been written to /home/max/.juju/environments.yaml. Edit the file to configure your juju environment and run bootstrap. max@eden:~$ juju switch local amazon - local max@eden:~$ juju bootstrap uploading tools for series [utopic precise trusty] Logging to /home/max/.juju/local/cloud-init-output.log on remote host chown: invalid user: ‘ubuntu:ubuntu’ Bootstrap failed, destroying environment ERROR exit status 1 max@eden:~$ ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- 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/1328958 Title: Local provider fails to bootstrap on utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1328958/+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-u-juju-core] Server team specific Juju work for Utopic
Blueprint changed by Robie Basak: Work items changed: Work items: Provide Juju 2.x in Trusty: TODO + Land juju-core update in Utopic: TODO + Land juju-quickstart update in Utopic: TODO -- Server team specific Juju work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-juju-core -- 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 1322498] Re: Unable to set swift container ACL's on existing containers
This bug was fixed in the package ceph - 0.80.1-0ubuntu1.1 --- ceph (0.80.1-0ubuntu1.1) trusty; urgency=medium * Fix issue setting Swift ACL's on existing containers (LP: #1322498): - d/p/bug-8428.patch: Cherry pick proposed fix from upstream VCS. -- James Page james.p...@ubuntu.com Mon, 02 Jun 2014 09:09:37 +0100 ** Changed in: ceph (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 ceph in Ubuntu. https://bugs.launchpad.net/bugs/1322498 Title: Unable to set swift container ACL's on existing containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1322498/+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 1322498] Update Released
The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1322498 Title: Unable to set swift container ACL's on existing containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1322498/+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 985489] Re: nova-compute stops processing compute.$HOSTNAME occasionally on libvirt
@wangpan I'm revisiting this bug, do you have a link to the change that you proposed? Even if you didn't think it was adequate I'd like to see your approach. -Mike -- 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/985489 Title: nova-compute stops processing compute.$HOSTNAME occasionally on libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/985489/+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 1329015] [NEW] getdeb repository not work
Public bug reported: befor install s-d-p on server I have add archive.getdeb.net repository and if I do a sudo apt-get update all work fine. then I install s-d-p and s-d-p-c now if I do sudo apt-get update I get this error W: Impossible get http://archive.getdeb.net/ubuntu/dists/trusty-getdeb/apps/binary-amd64/Packages 403 Forbidden but if the mirror dest domain is missing I have understand that the client have to get file avoid using s-d-p if I add in /etc/squid-deb-proxy/mirror-dstdomain.acl.d./10-default a row like this: archive.getdeb.net or .archive.getdeb.net and restart s-d-p and now I do sudo apt-get update I get the same error W: Impossible get http://archive.getdeb.net/ubuntu/dists/trusty-getdeb/apps/binary-amd64/Packages 403 Forbidden ** Affects: squid-deb-proxy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1329015 Title: getdeb repository not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1329015/+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 1329049] [NEW] quickstart fails, hardcodes /var/lib/lxc/ somewhere
Public bug reported: I am on current Utopic, and installed the utopic-proposed juju packages (as 1.18.1 is known to not work on utopic): ii juju-core1.18.4-0ubuntu1 amd64Juju is devops distilled - client ii juju-local 1.18.4-0ubuntu1 all dependency package for the Juju local provider ii juju-mongodb 2.4.10-0ubuntu1 amd64MongoDB object/document-oriented database for Juju ii juju-quickstart 1.3.1-0ubuntu1 all Easy configuration of Juju environments ii python-jujuclient0.17.5-0ubuntu2 all Python API client for juju With no pre-existing ~/.juju, quickstart fails with: $ juju quickstart changes to the environments file have been saved juju quickstart v1.3.1 bootstrapping the local environment (type: local) sudo privileges will be required to bootstrap the environment retrieving the environment status retrieving the Juju API address connecting to wss://10.0.3.1:17070 requesting juju-gui deployment charm URL: cs:precise/juju-gui-90 juju-gui deployment request accepted exposing service juju-gui requesting new unit deployment juju-gui/0 deployment request accepted juju-gui/0 deployment is pending machine 1 provisioning is pending juju-quickstart: error: machine 1 is in an error state: error: open /var/lib/lxc/martin-local-machine-1/config: no such file or directory ERROR exit status 1 $ juju status environment: local machines: 0: agent-state: started agent-version: 1.18.4.1 dns-name: localhost instance-id: localhost series: utopic 1: agent-state-info: '(error: open /var/lib/lxc/martin-local-machine-1/config: no such file or directory)' instance-id: pending series: precise services: juju-gui: charm: cs:precise/juju-gui-90 exposed: true units: juju-gui/0: agent-state: pending machine: 1 I have changed the LXC path, as my /var/lib/ is too small for many containers: $ cat /etc/lxc/lxc.conf lxc.lxcpath = /scratch/lxc So I suppose juju-quickstart (or perhaps juju itself) hardcodes /var/lib/lxc/ somewhere, instead of asking LXC: $ sudo lxc-config lxc.lxcpath /scratch/lxc (Ideally it wouldn't care about these files in the first place and only use the lxc-* tools to interact with containers, as the structure of this dir should be an internal implementation detail. But I realize that for some things this might not be possible) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: juju-quickstart 1.3.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8 Uname: Linux 3.15.0-5-generic x86_64 ApportVersion: 2.14.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 11 21:48:06 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-27 (104 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224) PackageArchitecture: all SourcePackage: juju-quickstart UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju-quickstart (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-quickstart in Ubuntu. https://bugs.launchpad.net/bugs/1329049 Title: quickstart fails, hardcodes /var/lib/lxc/ somewhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1329049/+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 1329049] Re: quickstart fails, hardcodes /var/lib/lxc/ somewhere
It indeed created some stuff there, which LXC can't see: $ sudo ls -l /var/lib/lxc/ drwxr-xr-x 3 root root 4096 Jun 11 21:45 juju-precise-template drwxr-xr-x 3 root root 4096 Mär 11 11:04 martin-local-machine-1 I wiped /var/lib/lxc/ again and made a /var/lib/lxc → /scratch/lxc symlink, and with that it gets further. It still fails, but I'll file this as a separate bug. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-quickstart in Ubuntu. https://bugs.launchpad.net/bugs/1329049 Title: quickstart fails, hardcodes /var/lib/lxc/ somewhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1329049/+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 1329051] [NEW] local boostrapping of juju-gui fails on git not found
Public bug reported:
I am on current Utopic, and installed the utopic-proposed juju packages
(as 1.18.1 is known to not work on utopic):
ii juju-core 1.18.4-0ubuntu1 amd64 Juju is devops distilled - client
ii juju-local 1.18.4-0ubuntu1 all dependency package for the Juju local provider
ii juju-mongodb 2.4.10-0ubuntu1 amd64 MongoDB object/document-oriented database
for Juju
ii juju-quickstart 1.3.1-0ubuntu1 all Easy configuration of Juju environments
ii python-jujuclient 0.17.5-0ubuntu2 all Python API client for juju
With no pre-existing ~/.juju, and a workaround for bug 1329049,
quickstart does this:
$ juju quickstart
juju quickstart v1.3.1
bootstrapping the local environment (type: local)
sudo privileges will be required to bootstrap the environment
retrieving the environment status
retrieving the Juju API address
connecting to wss://10.0.3.1:17070
requesting juju-gui deployment
charm URL: cs:precise/juju-gui-90
juju-gui deployment request accepted
exposing service juju-gui
requesting new unit deployment
juju-gui/0 deployment request accepted
juju-gui/0 deployment is pending
machine 1 provisioning is pending
juju-gui/0 placed on 10.0.3.219
machine 1 is started
and now hangs eternally.
$ juju status
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.4.1
dns-name: localhost
instance-id: localhost
series: utopic
1:
agent-state: started
agent-version: 1.18.4.1
dns-name: 10.0.3.219
instance-id: martin-local-machine-1
series: precise
hardware: arch=amd64
services:
juju-gui:
charm: cs:precise/juju-gui-90
exposed: true
units:
juju-gui/0:
agent-state: pending
agent-version: 1.18.4.1
machine: 1
public-address: 10.0.3.219
unit-juju-gui-0.log shows an endless stream of
2014-06-11 20:03:18 ERROR juju.worker.uniter.charm git.go:211 git command
failed: exec: git: executable file not found in $PATH
path:
/var/lib/juju/agents/unit-juju-gui-0/state/deployer/update-20140611-220318576432597
args: []string{init}
2014-06-11 20:03:18 WARNING juju.worker.uniter.charm git_deployer.go:200 no
current staging repo
2014-06-11 20:03:18 ERROR juju.worker.uniter.filter filter.go:116 tomb: dying
2014-06-11 20:03:18 ERROR juju runner.go:220 worker: exited uniter:
ModeInstalling cs:precise/juju-gui-90: git init failed: exec: git: executable
file not found in $PATH
So apparently the charm is missing to install git?
Also, is it really on purpose that juju-gui-0 runs on precise, not on
trusty? Even with a pre-existing .juju/environments.yaml with default-
series: trusty in the local section it does that.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: juju-core 1.18.4-0ubuntu1 [origin: unknown]
ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8
Uname: Linux 3.15.0-5-generic x86_64
ApportVersion: 2.14.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 11 22:01:09 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-27 (104 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug third-party-packages utopic
--
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/1329051
Title:
local boostrapping of juju-gui fails on git not found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1329051/+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 1329051] Re: local boostrapping of juju-gui fails on git not found
Exactly the same issue with $ juju init # edit .juju/environments.yaml to select trusty as default release, and default to local $ juju bootstrap uploading tools for series [utopic precise trusty] Logging to /home/martin/.juju/local/cloud-init-output.log on remote host Starting MongoDB server (juju-db-martin-local) Bootstrapping Juju machine agent Starting Juju machine agent (juju-agent-martin-local) $ juju deploy juju-gui Added charm cs:trusty/juju-gui-2 to the environment. $ juju status environment: local machines: 0: agent-state: started agent-version: 1.18.4.1 dns-name: localhost instance-id: localhost series: utopic 1: agent-state: started agent-version: 1.18.4.1 dns-name: 10.0.3.104 instance-id: martin-local-machine-1 series: trusty hardware: arch=amd64 services: juju-gui: charm: cs:trusty/juju-gui-2 exposed: false units: juju-gui/0: agent-state: pending agent-version: 1.18.4.1 machine: 1 public-address: 10.0.3.104 .juju/local/log/unit-juju-gui-0.log now loops on teh same git error. -- 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/1329051 Title: local boostrapping of juju-gui fails on git not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1329051/+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 1329051] Re: local boostrapping of juju-gui fails on git not found
So I poked further, and thought to install git manually: $ sudo lxc-attach -n martin-local-machine-1 root@martin-local-machine-1:/# apt-get install git Fehl http://archive.ubuntu.com/ubuntu/ trusty/main liberror-perl all 0.17-1.1 Verbindung mit 127.0.0.1:3142 nicht möglich (127.0.0.1) - connect (111: Connection refused) A-ha! /etc/apt/apt.conf.d/42-juju-proxy-settings indeed used that for a proxy (it seems to sort of autodetect apt-cacher-ng, or just blindly uses the host's apt proxy), but of course that's only valid on my host, not in the container. I fixed that to http://10.0.3.1:3142, and installed git. Now the charm continues. So perhaps it actually did try to install git, but if so, there's no trace of it in unit-juju-gui-0.log. But after installing git manually, the charm goes on with installing more packages, and finally succeeds. I get the Juju GUI now (found the password in environments/local.jenv). ** Summary changed: - local boostrapping of juju-gui fails on git not found + local charm deployment fails on git not found due to wrong apt proxy -- 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/1329051 Title: local charm deployment fails on git not found due to wrong apt proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1329051/+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 1008475] Re: winbindd nsswitch fails with RID backend on 12.04
** Changed in: samba Status: Confirmed = Incomplete -- 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/1008475 Title: winbindd nsswitch fails with RID backend on 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1008475/+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 1329051] Re: local charm deployment fails on git not found due to wrong apt proxy
I just got the very same problem with cs:trusty/postgresql-1, with the same solution. So I figure the problem is the improper usage of the host proxy that has a localhost address. It needs to be translated to talking to the proxy on the host. -- 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/1329051 Title: local charm deployment fails on git not found due to wrong apt proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1329051/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
Hi, I tried to test this and couldn't get it to work, though I may have done something stupid. I run precise, and upgraded to the lts-trusty kernel. I then removed open-vm-tools ( friends), and inserted the custom built precise package. That all worked fine, but I still can't mount vmhgfs as I did before I did the kernel upgrade in the first place (more precisely, my /etc/fstab line worked, whereas now the system still hangs on boot until I press 'S' at the console). I note the above says The modules which fail to build have been merged upstream, ***with the exception of the host-guest file system (hgfs) module which has been replaced with an hgfs FUSE helper***. These modules are available in v3.9 of the kernel and later (Saucy and later) (my emphasis). That rather implies that the FUSE helper is now included within the package(s). If so, how do I use it as the previous syntax does not appear to work. If not, how does one get the FUSE helper? Alex amb@nimrod-ubuntu:~$ fgrep vmhgfs /etc/fstab .host:/amb-nimrod /home/amb/nimrod vmhgfs none 0 0 amb@nimrod-ubuntu:~$ sudo mount -t vmhgfs .host:/amb-nimrod /home/amb/nimrod Error: cannot mount filesystem: No such device amb@nimrod-ubuntu:~$ uname -a Linux nimrod-ubuntu 3.13.0-29-generic #53~precise1-Ubuntu SMP Wed Jun 4 22:06:25 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux amb@nimrod-ubuntu:~$ dpkg --list | egrep '(open-vm|linux-image|linux-headers)' ii linux-headers-3.13.0-29 3.13.0-29.53~precise1 Header files related to Linux kernel version 3.13.0 ii linux-headers-3.13.0-29-generic 3.13.0-29.53~precise1 Linux kernel headers for version 3.13.0 on 64 bit x86 SMP ii linux-headers-3.2.0-64 3.2.0-64.97 Header files related to Linux kernel version 3.2.0 ii linux-headers-3.2.0-64-generic 3.2.0-64.97 Linux kernel headers for version 3.2.0 on 64 bit x86 SMP ii linux-headers-3.8.0-35 3.8.0-35.52~precise1 Header files related to Linux kernel version 3.8.0 ii linux-headers-3.8.0-35-generic 3.8.0-35.52~precise1 Linux kernel headers for version 3.8.0 on 64 bit x86 SMP ii linux-headers-generic 3.2.0.64.76 Generic Linux kernel headers ii linux-headers-generic-lts-trusty3.13.0.29.25 Generic Linux kernel headers ii linux-image-3.13.0-29-generic 3.13.0-29.53~precise1 Linux kernel image for version 3.13.0 on 64 bit x86 SMP ii linux-image-3.2.0-48-generic3.2.0-48.74 Linux kernel image for version 3.2.0 on 64 bit x86 SMP ii linux-image-3.2.0-57-generic3.2.0-57.87 Linux kernel image for version 3.2.0 on 64 bit x86 SMP ii linux-image-3.2.0-58-generic3.2.0-58.88 Linux kernel image for version 3.2.0 on 64 bit x86 SMP ii linux-image-3.2.0-64-generic3.2.0-64.97 Linux kernel image for version 3.2.0 on 64 bit x86 SMP ii linux-image-3.8.0-35-generic3.8.0-35.52~precise1 Linux kernel image for version 3.8.0 on 64 bit x86 SMP ii linux-image-generic 3.2.0.64.76 Generic Linux kernel image ii linux-image-generic-lts-trusty 3.13.0.29.25 Generic Linux kernel image ii open-vm-tools-lts-trusty 2:9.4.0-1280544-5ubuntu6~precise1Open VMware Tools for virtual machines hosted on VMware (CLI) ii open-vm-tools-lts-trusty-dbg 2:9.4.0-1280544-5ubuntu6~precise1Open VMware Tools for virtual machines hosted on VMware (debug) ii open-vm-tools-lts-trusty-desktop 2:9.4.0-1280544-5ubuntu6~precise1Open VMware Tools for virtual machines hosted on VMware (GUI) -- 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/1275656 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1328659] Re: import_boot_images task fails on utopic
** Branch linked: lp:~matsubara/maas/syslinux-dev-dep-utopic -- 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/1328659 Title: import_boot_images task fails on utopic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1328659/+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 1328166] Re: /etc/cron.d/maas_remote_syslog_compress not removed on package uninstall
How did you uninstall? I tried on a pristine utopic VM (1.5.2+bzr2282-0ubuntu1) and with apt-get remove --purge, the file was successfully removed but with apt-get remove only the file was preserved as expected. ** Changed in: maas (Ubuntu) Status: New = Incomplete -- 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/1328166 Title: /etc/cron.d/maas_remote_syslog_compress not removed on package uninstall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1328166/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
Further playing about suggests I need (somehow) vmware-hgfsclient, but the package seems devoid of any documentation or manual pages. -- 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/1275656 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1322151] Re: ImportError: No module named pexpect setting up maas-dns
This has been verified in the MAAS qa lab: http://d-jenkins.ubuntu- ci:8080/view/MAAS/job/utopic-adt-maas/14/consoleFull ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1322151 Title: ImportError: No module named pexpect setting up maas-dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1322151/+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 1324944] Re: MAAS fires 5 tasks to write_dhcp_config when only one nodegroup change was made
This has been verified in the MAAS QA lab: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-maas/70/artifact/results/artifacts/maas-logs/var/log/maas/celery.log and http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/trusty-adt-maas/279/artifact/results/artifacts/maas-logs/var/log/maas/celery.log/*view*/, only one write_dhcp_config task is fired. Nevermind the traceback in the logs, that's been filed as bug 1328656 ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1324944 Title: MAAS fires 5 tasks to write_dhcp_config when only one nodegroup change was made To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1324944/+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 1328166] Re: /etc/cron.d/maas_remote_syslog_compress not removed on package uninstall
Thanks for testing. I had thought I'd used purge via a separate script, but now that I look back I'm not sure. My apologies for the bug spam ** Changed in: maas (Ubuntu) Status: Incomplete = Invalid -- 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/1328166 Title: /etc/cron.d/maas_remote_syslog_compress not removed on package uninstall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1328166/+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 1311724] Re: Macbook Air resumes immidiately after suspend
Today it almost fried my macbook, was very hot when i got it out of bag. I have MacBookPro11,2, contents of cat /proc/acpi/wakeup are exactly as above. Started after package upgrades couple weeks ago, now persists with all kernels i have on grub loader. 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1311724 Title: Macbook Air resumes immidiately after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1311724/+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 1289489] Re: Installing MAAS from cloud-tools-next on precise fails
Hi Ryan, I tried this in a pristine precise VM with the current version of maas in cloud-tools-next (1.5+bzr2252-0ubuntu1~ctools0) and didn't get any errors during install. I didn't get errors when I ran the upgrade test from cloud-tools to cloud-tools-next either so I'm closing this as invalid. Please re-open if you are able to reproduce. Thanks! ** Changed in: maas (Ubuntu) Status: Confirmed = Invalid -- 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/1289489 Title: Installing MAAS from cloud-tools-next on precise fails To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1289489/+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 908112] Re: #110992 still happens (modules are not loaded)
So at least in 1.8.13-1 it still doesn't work. I don't know how to get 1.8.14-2 in Precise LTS. Below is what I get when trying to run ipmitool without loading the ipmi modules explicitly with /etc/rc.local Please advise. jason@server:~$ apt-cache policy ipmitool ipmitool: Installed: 1.8.13-1~ubuntu12.04.1 Candidate: 1.8.13-1~ubuntu12.04.1 Version table: *** 1.8.13-1~ubuntu12.04.1 0 100 http://archive.ubuntu.com/ubuntu/ precise-backports/universe amd64 Packages 100 /var/lib/dpkg/status 1.8.11-5ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages jason@server:~$ sudo ipmitool -I open mc info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory Get Device ID command failed jason@server:~$ sudo modprobe ipmi_msghandler sudo modprobe ipmi_devintf sudo modprobe ipmi_si jason@server:~$ sudo ipmitool -I open mc info Device ID : 32 Device Revision : 1 Firmware Revision : 1.23 IPMI Version : 2.0 Manufacturer ID : 10876 Manufacturer Name : Supermicro Product ID: 2054 (0x0806) Product Name : Unknown (0x806) Device Available : yes Provides Device SDRs : no Additional Device Support : Sensor Device SDR Repository Device SEL Device FRU Inventory Device IPMB Event Receiver IPMB Event Generator Chassis Device -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/908112 Title: #110992 still happens (modules are not loaded) To manage notifications about this bug go to: https://bugs.launchpad.net/eilt/+bug/908112/+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 1328659] Re: import_boot_images task fails on utopic
Ok, so we're either going to have to detect which file should be used or make the switch to utopic on trunk. Since we want to continue to deploy trunk to trusty, we'll have to detect the file's location. ** Tags added: provisioning -- 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/1328659 Title: import_boot_images task fails on utopic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1328659/+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 1321427] Re: [SRU] Update walinuxagent package for Precise to v2.0.5
We have run our network, VNET, BVT and E2E tests using the walinuxagent 2.0.5 package for Ubuntu 12.04 and found no issues. Cloud Test Update: * Network Tests : Completed. [41 PASS, 1 XFAIL] Expected Failed Tests : 1. NETWORK-IDNS-SINGLEHS-CHANGED-HOSTNAME Reason : After changing the hostname of another VM in same hosted service, we are unable to resolve new hostname with nslookup. This is expected behavior on Ubuntu systems as they set 'Provisioning.MonitorHostName=n' in /etc/waagent.conf. * VNET Tests : Completed [15 PASS, 0 FAIL] No issues. * BVT Tests : Completed * E2E Tests : Completed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1321427 Title: [SRU] Update walinuxagent package for Precise to v2.0.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1321427/+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 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-trusty -- 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/1313450 Title: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313450/+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 1300739] Re: keepalived doesn't load any ipv6 virtual servers
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1300739 Title: keepalived doesn't load any ipv6 virtual servers To manage notifications about this bug go to: https://bugs.launchpad.net/keepalived/+bug/1300739/+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: template container contains user log mount in error
I found that the code was committed back in march to not mount the log dir in the container. My juju-precise-template lxc container had a line that include a mount to /home/tim/.juju/local/log, which caused cgroups to complain when logged in as my other local user. Removing the juju-precise-template and getting juju to recreate it fixed the problem for me. My template container was created about a week before the code landed in trunk. @pitti, can I get you to take a look inside the config file for the lxc container to see if you have a similar problem? ** Changed in: juju-core Assignee: Tim Penhey (thumper) = (unassigned) ** Changed in: juju-core Importance: High = Low ** Changed in: juju-core Milestone: next-stable = None ** Summary changed: - template container contains user log mount in error + non-default lxc-dir breaks local provider -- 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: non-default lxc-dir breaks local provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+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 1290920] Re: non-default lxc-dir breaks local provider
Gah, I should read the entire description before changing things. This was a different problem to me that had exactly the same error message. -- 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: non-default lxc-dir breaks local provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+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 1290920] Re: non-default lxc-dir breaks local provider
For the record, on current utopic I didn't see this failed to mount '/home/ubuntu/.juju/local/log' error message any more. I still have trouble with non-default lxcpath, but it's different now. I filed bug 1329049 about that yesterday. So from my POV this can be closed, not sure if Tim still wants to keep this for the bug he's seeing? -- 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: non-default lxc-dir breaks local provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+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
