[Bug 1031063] Re: internal error no supported architecture for os type 'hvm'
@ Serge
I write down the process I have tried to solve this issue...
First the nova-compute.log show an ERROR as follow...
2013-05-21 16:19:11.230 ERROR nova.compute.manager [req-0e30e53b-
8d93-4a0b-b378-672a02d6eb417c0d5d8e458f4580972e14af22e8a6ca
8d6292b82686470bb5a46d3c1a565c03] [instance:
71c40047-8422-4623-aaf0-f06353dfcb75] Error: ['Traceback (most recent
call last):\n', ' File /usr/lib/python2.7/dist-
packages/nova/compute/manager.py, line 834, in _run_instance\n
set_access_ip=set_access_ip)\n', ' File /usr/lib/python2.7/dist-
packages/nova/compute/manager.py, line 1093, in _spawn\n
LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', '
File /usr/lib/python2.7/contextlib.py, line 24, in __exit__\n
self.gen.next()\n', ' File /usr/lib/python2.7/dist-
packages/nova/compute/manager.py, line 1089, in _spawn\n
block_device_info)\n', ' File /usr/lib/python2.7/dist-
packages/nova/virt/libvirt/driver.py, line 1520, in spawn\n
block_device_info)\n', ' File /usr/lib/python2.7/dist-
packages/nova/virt/libvirt/driver.py, line 2435, in
_create_domain_and_network\ndomain = self._create_domain(xml,
instance=instance)\n', ' File /usr/lib/python2.7/dist-
packages/nova/virt/libvirt/driver.py, line 2395, in _create_domain\n
domain = self._conn.defineXML(xml)\n', ' File /usr/lib/python2.7/dist-
packages/eventlet/tpool.py, line 187, in doit\nresult =
proxy_call(self._autowrap, f, *args, **kwargs)\n', ' File
/usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 147, in
proxy_call\nrv = execute(f,*args,**kwargs)\n', ' File
/usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 76, in
tworker\nrv = meth(*args,**kwargs)\n', ' File /usr/lib/python2.7
/dist-packages/libvirt.py, line 2760, in defineXML\nif ret is
None:raise libvirtError(\'virDomainDefineXML() failed\', conn=self)\n',
libvirtError: internal error no supported architecture for os type
'hvm'\n]
Then I check the /usr/lib/python2.7/dist-packages/libvirt.py at line
2760, it is a function in class virConnect
def defineXML(self, xml):
ret = libvirtmod.virDomainDefineXML(self._o, xml)
if ret is None:raise libvirtError('virDomainDefineXML() failed',
conn=self)
__tmp = virDomain(self,_obj=ret)
return __tmp
To output the xml I add some code as follow and restart nova-compute
service
def defineXML(self, xml):
# save xml files to a temporary location
import __builtin__ as bu
f = bu.open(/tmp/libvirt.xml, w)
f.write(xml) # Write a string to a file
f.close()
ret = libvirtmod.virDomainDefineXML(self._o, xml)
if ret is None:raise libvirtError('virDomainDefineXML() failed',
conn=self)
__tmp = virDomain(self,_obj=ret)
return __tmp
When re-create a vm use OpenStack Dashboard, I got the /tmp/libvirt.xml
as follow
domain type=kvm
uuid563fab12-f8b3-4689-b9b6-b3ba89c98246/uuid
nameinstance-0007/name
memory524288/memory
vcpu1/vcpu
sysinfo type=smbios
system
entry name=manufacturerOpenStack Foundation/entry
entry name=productOpenStack Nova/entry
entry name=version2013.1/entry
entry name=serialc56740d8-bfbc-db37-fe43-75ba7c50cdb8/entry
entry name=uuid563fab12-f8b3-4689-b9b6-b3ba89c98246/entry
/system
/sysinfo
os
typehvm/type
boot dev=hd/
smbios mode=sysinfo/
/os
features
acpi/
apic/
/features
clock offset=utc
timer name=pit tickpolicy=delay/
timer name=rtc tickpolicy=catchup/
/clock
cpu mode=host-model match=exact/
devices
disk type=file device=disk
driver name=qemu type=qcow2 cache=none/
source
file=/var/lib/nova/instances/563fab12-f8b3-4689-b9b6-b3ba89c98246/disk/
target bus=virtio dev=vda/
/disk
interface type=bridge
mac address=fa:16:3e:dd:b1:94/
model type=virtio/
source bridge=br-int/
target dev=tapcd5492b6-18/
virtualport type=openvswitch
parameters interfaceid=cd5492b6-1835-464a-b705-d5fed0766237/
/virtualport
/interface
serial type=file
source
path=/var/lib/nova/instances/563fab12-f8b3-4689-b9b6-b3ba89c98246/console.log/
/serial
serial type=pty/
input type=tablet bus=usb/
graphics type=vnc autoport=yes keymap=en-us listen=0.0.0.0/
/devices
/domain
One can find the first line (domain type=kvm) that it still specify to use
KVM rather than Qemu, though I already specify libvirt_type=qemu in
nova.conf. According to #3 @Jamie's post, I found two possible way to solve it.
1. change the first line to domain type=qemu
2. change the line 16 to type arch='x86_64'hvm/type
For testing, I have added some code in /usr/lib/python2.7/dist-
packages/libvirt.py to change the xml (ex. xml =
xml.replace('type=kvm', 'type=qemu',1)). Both method works fine.
So I still do not sure is it the bug of libvirt of Nova?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
[Bug 1182240] Re: Brazilian Portuguese language errorpage directory
I am re-opening this due to the closure being based on an assumption that the original report was accurate. pt-bz refers to Portuguese reading/writing citizens of Belize (NOT Brazil). Which is a valid ISO code missing from the squid-langpack package. Any information on whether Belize Portuguese dialect can be presented with Brazillian or European Portuguese texts or whether they require a third translation is very welcome. Until then upstream will contain a symlink entry for pt-bz to pt-br based on the geographical distance for dialect locale. ** Changed in: squid3 (Ubuntu) Status: Invalid = 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/1182240 Title: Brazilian Portuguese language errorpage directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1182240/+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 1182746] Re: FTBFS: requires internet connectivity
** Changed in: dnsjava (Debian) Importance: Undecided = Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsjava in Ubuntu. https://bugs.launchpad.net/bugs/1182746 Title: FTBFS: requires internet connectivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsjava/+bug/1182746/+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 1182240] Re: Brazilian Portuguese language errorpage directory
Thanks Amos. http://www.squid-cache.org/Versions/langpack/ suggests that there should be a pt, and when I try that, I seem to get some Portuguese back (although it doesn't look like all strings are supported). However, pt- bz doesn't seem to alias to it. ** Summary changed: - Brazilian Portuguese language errorpage directory + squid3 does not have pt-bz language support ** Changed in: squid3 (Ubuntu) Importance: Undecided = Wishlist -- 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/1182240 Title: squid3 does not have pt-bz language support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1182240/+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 993291] Re: [SRU] package nis 3.17-32ubuntu1.2 failed to install/upgrade: invoke-rc.d: unknown initscript, /etc/init.d/nis not found.
Oneiric is EOL out now ** Changed in: nis (Ubuntu Oneiric) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/993291 Title: [SRU] package nis 3.17-32ubuntu1.2 failed to install/upgrade: invoke- rc.d: unknown initscript, /etc/init.d/nis not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993291/+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 1182613] Re: puppet completely broken on saucy
Confirmed. ** Changed in: puppet (Ubuntu) Status: New = Triaged ** Changed in: puppet (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1182613 Title: puppet completely broken on saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1182613/+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 1180355] Re: LXC Template ubuntu-cloud does not work
Thank you very much for your answer. I tried: $ sudo lxc-create -t ubuntu-cloud -n test With that i get the same error: $ sudo lxc-create -t ubuntu-cloud -n test No config file specified, using the default config ubuntu-cloudimg-query ist /usr/bin/ubuntu-cloudimg-query wget ist /usr/bin/wget failed to get https://cloud-images.ubuntu.com/query/precise/server/released-dl.current.txt failed to execute template 'ubuntu-cloud' aborted Doing a wget on the url was the right tip. It resulted in: $ wget https://cloud-images.ubuntu.com/query/precise/server/released-dl.current.txt --2013-05-22 09:35:41-- https://cloud-images.ubuntu.com/query/precise/server/released-dl.current.txt Auflösen des Hostnamen »cloud-images.ubuntu.com (cloud-images.ubuntu.com)«... 91.189.88.141 Verbindungsaufbau zu cloud-images.ubuntu.com (cloud-images.ubuntu.com)|91.189.88.141|:443... verbunden. FEHLER: Kann das Zertifikat von »cloud-images.ubuntu.com« nicht prüfen, ausgestellt von »»/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certificates.godaddy.com/repository/CN=Go Daddy Secure Certification Authority/serialNumber=07969287««:. Ein selbst-signiertes Zertifikat gefunden. Verwenden Sie »--no-check-certificate«, um zu dem Server »cloud-images.ubuntu.com« eine nicht gesicherte Verbindung aufzubauen. There must be a problem with the certificates. Altough i havn't changed or configured anything in that direction. I tried to modify the /usr/share/lxc/templates/lxc-ubuntu-cloud script with the --no-check- certificate option on both wget calls but it didn't help. I don't think this is a bug in the lxc package but a bug concerning wget or the certificates. I tried the link from the wget outpuz and the certificate does not seem to exist. Could it be that there is a loadbalancer behind the url and you are getting a different mirror? Regards, Andreas -- 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/1180355 Title: LXC Template ubuntu-cloud does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1180355/+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 1167421] Re: Upgrading from folsom to grizzly results in all tenants/users being disabled
** 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 keystone in Ubuntu. https://bugs.launchpad.net/bugs/1167421 Title: Upgrading from folsom to grizzly results in all tenants/users being disabled To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1167421/+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 1180084] Re: nova-conductor should be in main
** Changed in: nova (Ubuntu Saucy) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1180084 Title: nova-conductor should be in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1180084/+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 1182247] Re: check_ide_smart fails with i/o error
Am 21.05.2013 09:55, schrieb Robie Basak: Please could you check the latest upstream version of nagios-plugins sorry, but which latest upstream version are you talking about?!? Recent upstream version is 1.4.16, same as in Ubuntu and Debian! Anyways .. I would have a look into the options --debug and --interface (which needs an argument). For me it smells like local configurations problem. Cheers, Jan. -- 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/1182247 Title: check_ide_smart fails with i/o error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1182247/+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-interlock] Ubuntu Server - Interlock
Blueprint changed by Andy Whitcroft: Work items set to: Work items: [davewalker] setup meeting between server, security and kernel to discuss support for the cloud archive: TODO -- Ubuntu Server - Interlock https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-interlock -- 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 1004606] Re: virsh create-snapshot fails to create external snapshot (blockdev-snapshot-sync fails in json monitor)
Theodor, can you please tell the rules that you added under TEMPLATE and /etc/apparmor.d/local/usr.sbin.libvirt? Thanks ! -- 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/1004606 Title: virsh create-snapshot fails to create external snapshot (blockdev- snapshot-sync fails in json monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1004606/+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 1167421] Re: Upgrading from folsom to grizzly results in all tenants/users being disabled
** Tags removed: verification-done ** Tags added: verification-needed -- 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/1167421 Title: Upgrading from folsom to grizzly results in all tenants/users being disabled To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1167421/+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 1067779] Re: missing pam_loginuid.so breaks getlogin()
** Bug watch added: Debian Bug tracker #677440 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677440 ** Also affects: openssh (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677440 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #677443 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677443 ** Also affects: cron (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677443 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #677441 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677441 ** Also affects: shadow (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677441 Importance: Unknown Status: Unknown ** Also affects: at (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #677442 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677442 ** Also affects: at (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677442 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1067779 Title: missing pam_loginuid.so breaks getlogin() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1067779/+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-openstack-havana] Openstack Next steps for S
Blueprint changed by Chuck Short: Work items changed: Work items: * Package Openstack havana for 12.04 and 13.10: TODO * MIR conntrack: TODO * MIR python-pecan: TODO * MIR mongodb: TODO * MIR python-ming: TODO * MIR python-happybase: TODO * Package HEAT: TODO * Automated compression of JS: TODO * Look at adding python3 support: TODO * Python3 support: TODO * Add zeromq support to the package: TODO * Add better quantum integration for plugins: TODO - * Add dep-8 tests for packages: TODO + * nova dep8 tests: TODO + * glance dep8 tests: TODO + * keystone dep8 tests: TODO + * horizon dep8 tests: TODO + * quantum dep8 tests: TODO + * novaclient dep8 tests: TODO + * glanceclient dep8 tests: TODO + * keystoneclient dep8 tests: TODO + * quantumclient dep8 tests: TODO * Automatic population of glance with Ubuntu images: TODO - * Improve Ubuntu Documentation: TODO + * Contribure to upstream documentation for Ubuntu: TODO + * Review help.ubuntu.com documentation (https://help.ubuntu.com/community/UbuntuCloudInfrastructure) and merge as appropriate: TODO * Review of Dependencies for 3rd-party plugins: TODO + * General refactor of compute package for easy non-libvirt compute flavor: TODO * Add vsphere support for packages: TODO + * Track status of Ironic incubation vs core status: TODO + * Track quantum rename: TODO + * Refactor cinder-volume for better backend support: TODO + * Confirm tab completion in all clients: TODO + * Package tempest: TODO + * Rename quantum: TODO + * Move packaging to ubuntu-server-dev: TODO + * Update d/control files for new VCS: TODO + * Update d/control Maintainers: TODO -- Openstack Next steps for S https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-havana -- 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 1067779] Re: missing pam_loginuid.so breaks getlogin()
** Changed in: openssh (Debian) Status: Unknown = Fix Released ** Changed in: shadow (Debian) Status: Unknown = New ** Changed in: at (Debian) Status: Unknown = New ** Changed in: cron (Debian) Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1067779 Title: missing pam_loginuid.so breaks getlogin() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1067779/+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-openstack-hypervisor] Openstack Hypervisors
Blueprint changed by Chuck Short: Work items changed: Work items: * Add a more recent version of XCP to the Ubuntu Archive: TODO * Write XCP documentation and Openstack: TODO * Test XCP and Openstack: TODO * Test libvirt-xen and Openstack: TODO * Write documentation on libvirt-xen: TODO * Add lxc block device support for apparmor: TODO * Add lxc qemu-nbd support for Openstack: TODO * Test vmware support and Openstack: TODO * Write documenation on vmware and Openstack: TODO + * [zulcss] Document supported configurations (including juju charm support): TODO + * Collect additional hardening profiles from users: TODO -- Openstack Hypervisors https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-hypervisor -- 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-openstack-qa] Openstack Server QA
Blueprint changed by Chuck Short: Work items changed: Work items: - Add support for quantum based security rules to nova and quantum charms: TODO - Add OpenStack + Quantum with L2 tenant separation: TODO - Add aditional Virtualized activities: TODO - Add smoke testing of the HA configuration: TODO - Regression testing and upgrade testing of OpenStack charms: TODO - Upgrade testing of packages: TODO - Install vmware in openstack-ci lab: TODO - Install Xen in openstack-ci lab: TODO - Add ceilometer charm to openstack-ci lab: TODO - Add tempest Stress Testing to openstack-ci lab: TODO - Update swift-proxy to support ceilometer: TODO - Add Dep-8 tests to openstack packages: TODO - Add ipv6 support to lab: TODO - Add zeromq support tot lab: TODO - Add reporting of test pipeline: TODO - Upstream dependency tracking of pypi: TODO + * Add support for quantum based security rules to nova and quantum charms: TODO + * Add OpenStack + Quantum with L2 tenant separation: TODO + * Add aditional Virtualized activities: TODO + * Add smoke testing of the HA configuration: TODO + * Regression testing and upgrade testing of OpenStack charms: TODO + * [adam_g] Upgrade testing of OpenStack using charm upgrades: TODO + * Upgrade testing of packages: TODO + * Install vmware in openstack-ci lab: TODO + * Install Xen in openstack-ci lab: TODO + * Add ceilometer charm to openstack-ci lab: TODO + * Add tempest Stress Testing to openstack-ci lab: TODO + * Update swift-proxy to support ceilometer: TODO + * Add Dep-8 tests to openstack packages: TODO + * Add ipv6 support to lab: TODO + * Add zeromq support tot lab: TODO + * Add reporting of test pipeline: TODO + * Upstream dependency tracking of pypi: TODO + * Implement mahem badger - tempest integration: TODO + * Review reporting of testing results to public jenkins, investigate performance: TODO + * Review cloudbox inconjunction with Canonical cert team: TODO -- Openstack Server QA https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-qa -- 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 1167421] Re: Upgrading from folsom to grizzly results in all tenants/users being disabled
Packages keystone_2013.1.1-0ubuntu1_all.deb and python-
keystone_2013.1.1-0ubuntu1_all.deb worked for me when upgrading from
folsom to grizzly.
On a side note, this issue reported should have only been an issue when
you have data like this in the extra column in the keystone.user
table:
{password: null, enabled: true, email: null, tenantId:
2f216605a48148f89d4390fc63e64819}
If your data was like this, it would have migrated correctly:
{password: null, enabled: true, email: null, tenantId:
2f216605a48148f89d4390fc63e64819}
This tripped me up as I tried doing some vanilla upgrades from folsom to
grizzly using precise-proposed/folsom and precise-proposed/grizzly
(which still has 1:2013.1-0ubuntu1.1~cloud0) and was unable to replicate
the issue with some newly created dummy users/tenants.
Thanks!
-Matt
** 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 keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1167421
Title:
Upgrading from folsom to grizzly results in all tenants/users being
disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1167421/+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-database-alternatives] Investigate alternatives to mysql
Blueprint changed by Chuck Short: Work items set to: Work items: * [davewalker] Look into migration paths provided by other distros: TODO * [clint-fewbar] Investigate how best to share/conflict libmysql namespace: TODO * [stewart] Package percona for Debian: TODO * [zulcss] sync percona into Saucy: TODO * Help get mariadb into Debian: TODO * [zulcss] Request microrelease exception for mysql: TODO -- Investigate alternatives to mysql https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-database-alternatives -- 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 1182898] [NEW] Please support `juju --version`
Public bug reported: I know we have `juju version` but there's some UNIX law we're breaking if we don't support this common flag. Also please alias -v too. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: juju-core 1.10.0.1-0ubuntu1~ubuntu13.04.1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Wed May 22 09:43:58 2013 Dependencies: InstallationDate: Installed on 2013-03-26 (56 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130326) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1182898 Title: Please support `juju --version` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1182898/+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 1182902] [NEW] juju help does not expose 'version' option
Public bug reported: juju help supports a 'version' flag which is not exposed as an option. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: juju-core 1.10.0.1-0ubuntu3 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:47:37 2013 InstallationDate: Installed on 2013-05-05 (17 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130504) MarkForUpload: True SourcePackage: juju-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- 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/1182902 Title: juju help does not expose 'version' option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1182902/+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 1182901] [NEW] juju help does not expose version number
Public bug reported: For a user wanting to find the version of juju, juju help is primarily recommended as a way to provide additional information, and the version should be specified there. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: juju-core 1.10.0.1-0ubuntu3 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:44:01 2013 InstallationDate: Installed on 2013-05-05 (17 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130504) MarkForUpload: True SourcePackage: juju-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- 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/1182901 Title: juju help does not expose version number To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1182901/+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] [NEW] charm-tools requires extra environments.yaml config
Public bug reported: 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 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) ** Affects: charm-tools (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 saucy -- 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 requires extra environments.yaml config 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 1182905] Re: charm-tools requires extra environments.yaml config
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: charm-tools (Ubuntu) Status: New = Confirmed -- 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 requires extra environments.yaml config 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 1182905] Re: charm-tools requires extra environments.yaml config
Note: was using Juju 0.7 when this happened. -- 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 requires extra environments.yaml config 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
[Blueprint servercloud-s-seeded-qa-workflow] Improving QA for seeded server packages
Blueprint changed by Yolanda Robla: Work items changed: Work items: [andreserl] write dep-8 test for heartbeat/corosync/pacemaker: TODO [andreserl] write dep-8 test for tftpd-hpa: TODO [gandelman-a] write dep-8 test for haproxy: TODO [gandelman-a] write dep-8 tests puppet + facter: TODO Get all tests automated by QA team: DONE [ivoks] write dep-8 test for bacula: TODO [yolanda] write dep-8 test for ganglia: DONE [yolanda] write dep-8 test for iscsitarget: DONE [james-page] write dep-8 test for jenkins: TODO [yolanda] write dep-8 test for nagios3: DONE [yolanda] write dep-8 test for open-iscsi: DONE [yolanda] write dep-8 test for quagga: DONE [yolanda] write dep-8 test for radvd: DONE [james-page] write dep-8 test for solr-tomcat/jetty: TODO [yolanda] write dep-8 test for tgt: DONE [james-page] write dep-8 test for openvswitch: DONE [james-page] Write some guidelines for test authors so we get things right first time: TODO [james-page] Update https://wiki.ubuntu.com/QATeam/RequiredTests where appropriate: DONE [pcarrier] write dep-8 test for munin: TODO - [yolanda] write dep-8 test for clamav: TODO - [racb] write dep-8 test for exim4: TODO + [yolanda] write dep-8 test for clamav: DONE + [yolanda] write dep-8 test for exim4: TODO [racb] write dep-8 test for mailman: TODO [racb] write dep-8 test for memcached: TODO [racb] write dep-8 test for squid3: TODO [racb] write dep-8 test for varnish: TODO [racb] write dep-8 test for vsftpd: TODO review backuppc for continued seed inclusion: TODO review likewise-open for continued seed inclusion: TODO [serge-hallyn] write dep-8 test for kvm: TODO [serge-hallyn] write dep-8 test for lxc: DONE [yolanda] write dep-8 test for amavisd-new: DONE [yolanda] write dep-8 test for nut: DONE [yolanda] write dep-8 test for postfix: DONE [yolanda] write dep-8 test for slapd/openldap: DONE [pcarrier] write dep-8 test for snmpd: TODO [yolanda] write dep-8 test for spamassassin: DONE [zulcss] write dep-8 test for freeradius: TODO [zulcss] write dep-8 test for rabbitmq-server: TODO -- Improving QA for seeded server packages https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-seeded-qa-workflow -- 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 requires extra environments.yaml config
** Branch linked: lp:~marcoceppi/ubuntu/saucy/charm-tools/fix-deps -- 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 requires extra environments.yaml config 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 1182905] Re: charm-tools requires extra environments.yaml config
** Changed in: charm-tools (Ubuntu) Status: Confirmed = Fix Committed -- 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 requires extra environments.yaml config 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 1182540] Re: lxc smoke test, test_lxc_apparmor appears to hang on saucy VM
This is also breaking all live filesystem builds, because udevd --daemon hangs around after debootstrap and eventually part of auto/build refuses to exit as a result. ** Package changed: udev (Ubuntu) = systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Importance: Undecided = Critical ** No longer affects: lxc (Ubuntu) ** Changed in: systemd (Ubuntu) Status: New = Confirmed -- 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/1182540 Title: lxc smoke test, test_lxc_apparmor appears to hang on saucy VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1182540/+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 1182247] Re: check_ide_smart fails with i/o error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nagios-plugins (Ubuntu) Status: New = Confirmed -- 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/1182247 Title: check_ide_smart fails with i/o error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1182247/+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 1182947] [NEW] Cannot specify interpreter path in AGI call
Public bug reported: When trying to call an AGI script like this exten = 1234,n,AGI(/path/to/interpreter /path/to/script,args) Asterisk says: WARNING[19529]: res_agi.c:1621 launch_script: Failed to execute '/path/to/interpreter /path/to/script': File does not exist. This is not serious, as in most cases it can be worked around by specifying the interpreter path on the script first line. It could however pose a problem for Java, where de interpreter is not usually placed on a standard path. This happens on :1.8.10.1~dfsg-1ubuntu1. ** Affects: asterisk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to asterisk in Ubuntu. https://bugs.launchpad.net/bugs/1182947 Title: Cannot specify interpreter path in AGI call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1182947/+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 1182624] Re: Uncached instance builds fail with non-zero root disk sizes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nova (Ubuntu) Status: New = Confirmed -- 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/1182624 Title: Uncached instance builds fail with non-zero root disk sizes To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1182624/+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-seeded-qa-workflow] Improving QA for seeded server packages
Blueprint changed by Yolanda Robla: Work items changed: Work items: [andreserl] write dep-8 test for heartbeat/corosync/pacemaker: TODO [andreserl] write dep-8 test for tftpd-hpa: TODO [gandelman-a] write dep-8 test for haproxy: TODO [gandelman-a] write dep-8 tests puppet + facter: TODO Get all tests automated by QA team: DONE [ivoks] write dep-8 test for bacula: TODO [yolanda] write dep-8 test for ganglia: DONE [yolanda] write dep-8 test for iscsitarget: DONE [james-page] write dep-8 test for jenkins: TODO [yolanda] write dep-8 test for nagios3: DONE [yolanda] write dep-8 test for open-iscsi: DONE [yolanda] write dep-8 test for quagga: DONE [yolanda] write dep-8 test for radvd: DONE [james-page] write dep-8 test for solr-tomcat/jetty: TODO [yolanda] write dep-8 test for tgt: DONE [james-page] write dep-8 test for openvswitch: DONE [james-page] Write some guidelines for test authors so we get things right first time: TODO [james-page] Update https://wiki.ubuntu.com/QATeam/RequiredTests where appropriate: DONE [pcarrier] write dep-8 test for munin: TODO [yolanda] write dep-8 test for clamav: DONE - [yolanda] write dep-8 test for exim4: TODO - [racb] write dep-8 test for mailman: TODO + [yolanda] write dep-8 test for exim4: DONE + [yolanda] write dep-8 test for mailman: TODO [racb] write dep-8 test for memcached: TODO [racb] write dep-8 test for squid3: TODO [racb] write dep-8 test for varnish: TODO [racb] write dep-8 test for vsftpd: TODO review backuppc for continued seed inclusion: TODO review likewise-open for continued seed inclusion: TODO [serge-hallyn] write dep-8 test for kvm: TODO [serge-hallyn] write dep-8 test for lxc: DONE [yolanda] write dep-8 test for amavisd-new: DONE [yolanda] write dep-8 test for nut: DONE [yolanda] write dep-8 test for postfix: DONE [yolanda] write dep-8 test for slapd/openldap: DONE [pcarrier] write dep-8 test for snmpd: TODO [yolanda] write dep-8 test for spamassassin: DONE [zulcss] write dep-8 test for freeradius: TODO [zulcss] write dep-8 test for rabbitmq-server: TODO -- Improving QA for seeded server packages https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-seeded-qa-workflow -- 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 1182902] Re: juju help does not expose 'version' option
** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu) Importance: Undecided = Wishlist -- 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/1182902 Title: juju help does not expose 'version' option To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1182902/+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 1182947] Re: Cannot specify interpreter path in AGI call
Thank you for taking the time to report this bug and helping to make Ubuntu better. This is the sort of thing that would be best fixed upstream - it's probably best not to make distro-specific changes in this area. Have you considered testing for this problem in the original upstream release and reporting the problem to Asterisk's bug tracker? ** Changed in: asterisk (Ubuntu) Importance: Undecided = Wishlist ** Tags added: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to asterisk in Ubuntu. https://bugs.launchpad.net/bugs/1182947 Title: Cannot specify interpreter path in AGI call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1182947/+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 1182898] Re: Please support `juju --version`
** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu) Importance: Undecided = Wishlist -- 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/1182898 Title: Please support `juju --version` To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1182898/+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 1182901] Re: juju help does not expose version number
** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu) Importance: Undecided = Wishlist -- 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/1182901 Title: juju help does not expose version number To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1182901/+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 1182980] [NEW] global parameters do not apply to enlistment
Public bug reported: I installed maas, then went to web UI and configured 'global kernel parameters'. I then enlisted a node, and saw that the node did not get my designated kernel parameters on boot. I had added '-- console=ttyS1,115200' as the parameters, but they didn't get to the node, meaning I cannot see log. The work around is to edit /usr/share/pyshared/provisioningserver/pxe/config.commissioning.template and add the parameters there. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: python-maas-provisioningserver 1.3+bzr1461+dfsg-0ubuntu2 [modified: usr/share/pyshared/provisioningserver/pxe/config.commissioning.template] ProcVersionSignature: Ubuntu 3.5.0-30.51-generic 3.5.7.9 Uname: Linux 3.5.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Wed May 22 17:53:15 2013 MarkForUpload: True PackageArchitecture: all SourcePackage: maas UpgradeStatus: Upgraded to raring on 2013-05-22 (0 days ago) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1182980 Title: global parameters do not apply to enlistment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1182980/+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 1182978] [NEW] MAAS will fail to set the correct user if a previous 'maas-commission' user exists
Public bug reported: When we try to re-enlist or re-commission a machine that previously had a maas-commission user, it will fail to correctly add/modify the new 'maas' user, which will cause IPMI power control to fail. ** Affects: maas Importance: Undecided Status: New ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Also affects: maas 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/1182978 Title: MAAS will fail to set the correct user if a previous 'maas-commission' user exists To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1182978/+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
This is due to the package Recommending juju instead of either juju or juju-core. I have an updated recipe and hope to have this fixed in the PPA soon. ** Summary changed: - charm-tools requires extra environments.yaml config + charm-tools installs juju-0.7 -- 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 1182905] Re: charm-tools installs juju-0.7
This only affects users who have juju-core installed and not juju-0.7, those with either juju-0.7 or juju-0.7 and juju-core are unaffected. -- 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 1182978] Re: MAAS will fail to set the correct user if a previous 'maas-commission' user exists
** Branch linked: lp:~andreserl/maas/fix_ipmi_user_creation -- 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/1182978 Title: MAAS will fail to set the correct user if a previous 'maas-commission' user exists To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1182978/+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 1182980] Re: global parameters do not apply to enlistment
** Also affects: maas 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/1182980 Title: global parameters do not apply to enlistment To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1182980/+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 1183109] [NEW] 'juju destroy-environment' missing from 'juju help'
Public bug reported: $SUBJECT says it all. 'juju help' gives me: jono@forge:~$ juju help Juju -- devops distilled https://juju.ubuntu.com/ Juju provides easy, intelligent service orchestration on top of environments such as OpenStack, Amazon AWS, or bare metal. Basic commands: juju init generate boilerplate configuration for juju environments juju bootstrapstart up an environment from scratch juju deploy deploy a new service juju add-relation add a relation between two services juju expose expose a service juju help bootstrap more help on e.g. bootstrap command juju help commandslist all commands juju help topics list all help topics juju destroy-environment is missing. Also see https://bugs.launchpad.net /juju-core/+bug/1182902 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: juju-core 1.10.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2 Uname: Linux 3.9.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Wed May 22 14:03:01 2013 InstallationDate: Installed on 2013-05-05 (17 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130504) MarkForUpload: True SourcePackage: juju-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- 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/1183109 Title: 'juju destroy-environment' missing from 'juju help' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1183109/+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 1183110] [NEW] Handshake error when first bootstrapping with AWS
Public bug reported: When I first configured Juju on my machine (originally 0.7) for AWS I got a handshake error when I first bootstrapped. When I bootstrapped next it worked. I also experienced handshake errors when deploying mysql, but again, second try seemed to work. Switched to gojuju, created new environments.yaml and same issue with first bootstrap: jono@forge:~$ juju bootstrap error: Get https://s3.amazonaws.com/juju-dist/?marker=prefix=tools%2Fjuju-delimiter=: remote error: handshake failure Again, second bootstrap seems to work. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: juju-core 1.10.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2 Uname: Linux 3.9.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Wed May 22 14:04:55 2013 InstallationDate: Installed on 2013-05-05 (17 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130504) MarkForUpload: True SourcePackage: juju-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju-core (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 saucy -- 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/1183110 Title: Handshake error when first bootstrapping with AWS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1183110/+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 1183110] Re: Handshake error when first bootstrapping with AWS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: juju-core (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1183110 Title: Handshake error when first bootstrapping with AWS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1183110/+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 1183109] Re: 'juju destroy-environment' missing from 'juju help'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: juju-core (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1183109 Title: 'juju destroy-environment' missing from 'juju help' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1183109/+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 1183116] [NEW] 'juju status' output when no env is non-intuitive
Public bug reported: When I have just detroyed my environment (or have no environment) and run 'juju status' I get: error: The specified bucket does not exist This doesn't make any sense. It should say something like this instead: No environment available. See http://juju.ubuntu.com/XYZ for how to create one. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: juju-core 1.10.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2 Uname: Linux 3.9.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Wed May 22 14:17:11 2013 InstallationDate: Installed on 2013-05-05 (17 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130504) MarkForUpload: True SourcePackage: juju-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju-core (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug cli-ui i386 papercut saucy -- 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/1183116 Title: 'juju status' output when no env is non-intuitive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1183116/+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 1183116] Re: 'juju status' output when no env is non-intuitive
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: juju-core (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1183116 Title: 'juju status' output when no env is non-intuitive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1183116/+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 1183109] Re: 'juju destroy-environment' missing from 'juju help'
** Tags added: cli-ui papercut -- 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/1183109 Title: 'juju destroy-environment' missing from 'juju help' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1183109/+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 1183129] [NEW] 'juju status' difficult to read and provides unneccessary information
Public bug reported: From using 'juju status' it provides me with a lot of detail, but most of it I don't care about. I care about the following: * Are my machines up. * Are my charms connected. * Where can access my service online? To illustrate this I deployed two wordpress charms with mysql. This is what 'juju status' gives me: jono@forge:~$ juju status machines: 0: agent-state: started agent-version: 1.10.0 dns-name: ec2-107-22-102-86.compute-1.amazonaws.com instance-id: i-d5db6fbf series: precise 1: agent-state: started agent-version: 1.10.0 dns-name: ec2-54-226-44-116.compute-1.amazonaws.com instance-id: i-74500d1c series: precise 2: agent-state: started agent-version: 1.10.0 dns-name: ec2-54-226-45-46.compute-1.amazonaws.com instance-id: i-5a500d32 series: precise 3: agent-state: started agent-version: 1.10.0 dns-name: ec2-54-226-15-107.compute-1.amazonaws.com instance-id: i-13169273 series: precise services: mysql: charm: cs:precise/mysql-19 exposed: false relations: db: - wordpress units: mysql/0: agent-state: started agent-version: 1.10.0 machine: 2 public-address: ec2-54-226-45-46.compute-1.amazonaws.com wordpress: charm: cs:precise/wordpress-15 exposed: true relations: db: - mysql loadbalancer: - wordpress units: wordpress/0: agent-state: started agent-version: 1.10.0 machine: 1 public-address: ec2-54-226-44-116.compute-1.amazonaws.com wordpress/1: agent-state: pending agent-version: 1.10.0 machine: 3 public-address: ec2-54-226-15-107.compute-1.amazonaws.com I just took a few minutes to play with an alternative way of presenting this information based upon the information I really care about (I think all the detail shown above should be accessible with 'juju status -v'). I think this is a better way of displaying it: jono@forge:~$ juju status Overview: [All services started] wordpress/0: ec2-54-226-44-116.compute-1.amazonaws.com wordpress/1: ec2-54-226-44-116.compute-1.amazonaws.com mysql: ec2-54-226-45-46.compute-1.amazonaws.com Topology: mysql/0 --|-- wordpress/0 |-- wordpress/1 Machines: 0 (i-d5db6fbf) [STARTED] Version:1.10.0 DNS:ec2-107-22-102-86.compute-1.amazonaws.com Series: precise 1 (i-74500d1c) [STARTED] Version:1.10.0 DNS:ec2-54-226-44-116.compute-1.amazonaws.com Series: precise 2 (i-5a500d32) [STARTED] Version:1.10.0 DNS:ec2-54-226-45-46.compute-1.amazonaws.com Series: precise 3 (i-5a500d32) [STARTED] Version:1.10.0 DNS:ec2-54-226-15-107.compute-1.amazonaws.com Series: precise The 'Overview' section tells me if everything is up and where to access my things. The 'Topology' section makes it clear that everything is connected. The 'Machines' section gives me details about the individual machines, but I re-formatted these to highlight the status (I put all status indications in square brackets in this mock-up). I would strongly recommend we display this (or another improved) simplified status as the default and show the detail with -v. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: juju-core 1.10.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2 Uname: Linux 3.9.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Wed May 22 14:35:59 2013 InstallationDate: Installed on 2013-05-05 (17 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130504) MarkForUpload: True SourcePackage: juju-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju-core (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug cli-ui i386 saucy -- 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/1183129 Title: 'juju status' difficult to read and provides unneccessary information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1183129/+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 1183129] Re: 'juju status' difficult to read and provides unneccessary information
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: juju-core (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1183129 Title: 'juju status' difficult to read and provides unneccessary information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1183129/+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 1182552] Re: freshclam crashed with SIGSEGV in cl_engine_free()
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please can you arrange to get us a full backtrace, including debugging symbols? Instructions at: https://help.ubuntu.com/community/ReportingBugs#Reporting_an_application_crash Once done, please change the bug status back to New. Thanks! -- 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/1182552 Title: freshclam crashed with SIGSEGV in cl_engine_free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1182552/+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 1182552] Re: freshclam crashed with SIGSEGV in cl_engine_free()
Note: clamav does appear to have debug symbol ddebs at ddebs.ubuntu.com. ** Changed in: clamav (Ubuntu) Status: New = Incomplete -- 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/1182552 Title: freshclam crashed with SIGSEGV in cl_engine_free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1182552/+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 1068145] Re: Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates now break
3.2.1 is out, once it makes it way into Debian and then Ubuntu archive I'll work on getting a possible backport accepted for Precise, Quantal and Raring. Thanks Adam -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1068145 Title: Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates now break To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1068145/+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-charmhelper2] Charm Development Tooling
Blueprint changed by Antonio Rosales: Work items changed: Work items: [marcoceppi] Consolidate existing forks/helper code bases: DONE Develop repos/organization structure of code base (modularize code): TODO Define distribution methods: TODO [marcoceppi] Update charm tools to promote best practices wrt stubbing/libraries WITH TESTS: TODO [marcoceppi] sync up with james and adam when structuring lp:charm-helpers: TODO [wedgwood] With help from marcoceppi, bac, adam_g, and james_page get core libraries ready: TODO [marcoceppi] charm-tools: Do not auto-fill charm description from package in charm create.: TODO + Shell out language specific commands: TODO -- Charm Development Tooling https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charmhelper2 -- 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 1183164] [NEW] maas-import-ephemerals failed with File Exists
*** This bug is a duplicate of bug 1182646 *** https://bugs.launchpad.net/bugs/1182646 Public bug reported: I added the 'daily' stream, and to /etc/maas/import_ephemerals, by appending: STREAM=daily ARCHES=amd64 i386 RELEASES=precise quantal raring saucy Then, ran maas-import-ephemerals, and it died like: Wed, 22 May 2013 21:54:59 +0100: finished. wrote to /var/lib/maas/ephemeral/.working/maas-import-ephemerals.mnccmE/precise/amd64/dist-root.tar.gz cmd failed: maas-provision install-pxe-image --arch=amd64 --subarch=generic --release=precise --purpose=commissioning --image=/tmp/tmp.KQXnCcCqmc --symlink=xinstall Traceback (most recent call last): File /usr/lib/python2.7/runpy.py, line 162, in _run_module_as_main __main__, fname, loader, pkg_name) File /usr/lib/python2.7/runpy.py, line 72, in _run_code exec code in run_globals File /usr/lib/python2.7/dist-packages/provisioningserver/__main__.py, line 39, in module main() File /usr/lib/python2.7/dist-packages/provisioningserver/utils.py, line 400, in __call__ self.execute(argv) File /usr/lib/python2.7/dist-packages/provisioningserver/utils.py, line 395, in execute args.handler.run(args) File /usr/lib/python2.7/dist-packages/provisioningserver/pxe/install_image.py, line 165, in run install_dir(args.image, destination, args.symlink) File /usr/lib/python2.7/dist-packages/provisioningserver/pxe/install_image.py, line 127, in install_dir os.symlink(old, sdest) OSError: [Errno 17] File exists failed to install tftp image [rel: precise, arch: amd64: name: maas-precise-daily-amd64-ephemeral-20130520] This system was upgraded from a trunk ppa to raring, and then purged and re-installed, so it is quite possible something was just out of whack from that. But the first time, import-pxe-files worked fine, it was only after adding daily that it failed. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: maas-cluster-controller 1.3+bzr1461+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu May 23 02:24:59 2013 MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=screen-bce PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: Upgraded to raring on 2013-05-22 (0 days ago) modified.conffile..etc.maas.maas.local.celeryconfig.cluster.py: [inaccessible: [Errno 13] Permission denied: '/etc/maas/maas_local_celeryconfig_cluster.py'] modified.conffile..etc.sudoers.d.99.maas.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/99-maas-sudoers'] ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ** Attachment added: full log of maas-import-pxe-files https://bugs.launchpad.net/bugs/1183164/+attachment/3684387/+files/bug.txt -- 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/1183164 Title: maas-import-ephemerals failed with File Exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1183164/+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 1183164] Re: maas-import-ephemerals failed with File Exists
*** This bug is a duplicate of bug 1182646 *** https://bugs.launchpad.net/bugs/1182646 ** This bug has been marked a duplicate of bug 1182646 maas-import-pxe-files fails to update ephemeral images -- 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/1183164 Title: maas-import-ephemerals failed with File Exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1183164/+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 1182646] Re: maas-import-pxe-files fails to update ephemeral images
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: maas (Ubuntu Raring) 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/1182646 Title: maas-import-pxe-files fails to update ephemeral images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1182646/+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 1182646] Re: maas-import-pxe-files fails to update ephemeral images
** Description changed: + Wed, 22 May 2013 21:54:59 +0100: finished. wrote to /var/lib/maas/ephemeral/.working/maas-import-ephemerals.mnccmE/precise/amd64/dist-root.tar.gz + cmd failed: maas-provision install-pxe-image --arch=amd64 --subarch=generic --release=precise --purpose=commissioning --image=/tmp/tmp.KQXnCcCqmc --symlink=xinstall + Traceback (most recent call last): + File /usr/lib/python2.7/runpy.py, line 162, in _run_module_as_main + __main__, fname, loader, pkg_name) + File /usr/lib/python2.7/runpy.py, line 72, in _run_code + exec code in run_globals + File /usr/lib/python2.7/dist-packages/provisioningserver/__main__.py, line 39, in module + main() + File /usr/lib/python2.7/dist-packages/provisioningserver/utils.py, line 400, in __call__ + self.execute(argv) + File /usr/lib/python2.7/dist-packages/provisioningserver/utils.py, line 395, in execute + args.handler.run(args) + File /usr/lib/python2.7/dist-packages/provisioningserver/pxe/install_image.py, line 165, in run + install_dir(args.image, destination, args.symlink) + File /usr/lib/python2.7/dist-packages/provisioningserver/pxe/install_image.py, line 127, in install_dir + os.symlink(old, sdest) + OSError: [Errno 17] File exists + failed to install tftp image [rel: precise, arch: amd64: name: maas-precise-daily-amd64-ephemeral-20130520] + + [Impact] If new ephemeral images are ready to be installed, maas-import-* scripts fail because it cannot overwrite a symlink that has been created to support FPI. This prevents maas from importing new ephemeral images. [Test Case] 1. Install maas. 2. maas-import-pxe-files 3. edit /etc/maas/import_ephemerals and add STREAM=daily 4. run maas-import-pxe-files again, it will download a newer ephemeral image and will fail to install it. 5. Apply the fix. 6. Run maas-import-pxe-files again, and it will install the image successfully. [Regression Potential] Minimal, this make sure that a new image being imported gets installed successfully. -- 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/1182646 Title: maas-import-pxe-files fails to update ephemeral images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1182646/+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 590537] Re: lo: Disabled Privacy Extensions keeps showing up in the system log
** Changed in: vsftpd (Debian) Status: New = Fix Released -- 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/590537 Title: lo: Disabled Privacy Extensions keeps showing up in the system log To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/590537/+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 1182240] Re: Brazilian Portuguese language errorpage directory
Hi Amos, Actually the Portuguese is not among Belize languages ( http://en.wikipedia.org/wiki/Languages_of_Belize). BZ is the ISO 3166 Code for Belize country, however this issue happens when the chosen mobile phone interface language is Brazilian Portuguese. My SQUID environment is serving traffic coming from mobile browsers. I checked this issue for some Motorola and LG mobile phones, their developers didn't adopt the correct Brazil's ISO 3166 Code. A symlink entry for pt-bz to pt-br is enough workaround. Regards, Igor Le Masson 2013/5/22 Amos Jeffries 1182...@bugs.launchpad.net I am re-opening this due to the closure being based on an assumption that the original report was accurate. pt-bz refers to Portuguese reading/writing citizens of Belize (NOT Brazil). Which is a valid ISO code missing from the squid-langpack package. Any information on whether Belize Portuguese dialect can be presented with Brazillian or European Portuguese texts or whether they require a third translation is very welcome. Until then upstream will contain a symlink entry for pt-bz to pt-br based on the geographical distance for dialect locale. ** Changed in: squid3 (Ubuntu) Status: Invalid = New -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1182240 Title: Brazilian Portuguese language errorpage directory Status in “squid3” package in Ubuntu: New Bug description: On version 3.1.20, the Brazilian Portuguese language abbreviation is defined as pt-bz instead of pt-br in errorpage.cc. Of course this can be solved with error_default_language option in squid.conf (http://wiki.squid-cache.org/Translations), however the abbreviation pt-bz does not exist. root@vm03:~# echo $LC_NAME pt_BR root@vm03:~# egrep -e errorpage|Language /var/log/squid3/cache.log|tail -3 2013/05/20 18:08:46| errorpage.cc(293) errorTryLoadText: '/usr/share/squid3/errors/pt-bz/ERR_DNS_FAIL': (2) No such file or directory 2013/05/20 18:08:46| WARNING: Error Pages Missing Language: pt-bz 2013/05/20 18:09:06| errorpage.cc(293) errorTryLoadText: '/usr/share/squid3/errors/pt-bz/ERR_DNS_FAIL': (2) No such file or directory root@vm03:~# ls -d /usr/share/squid3/errors/pt* /usr/share/squid3/errors/pt /usr/share/squid3/errors/pt-br /usr/share/squid3/errors/pt-pt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1182240/+subscriptions -- 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/1182240 Title: squid3 does not have pt-bz language support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1182240/+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 1183180] [NEW] freshclam crashed with SIGSEGV in cl_engine_free()
Public bug reported: Happened at start. Don't know what to do to reproduce the bug other than using the latest updates from Ubuntu 13.04 ( inluding proposed ) and starting the system. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: clamav-freshclam 0.97.8+dfsg-1ubuntu1.13.04.1 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CrashCounter: 1 Date: Tue May 21 12:07:29 2013 ExecutablePath: /usr/bin/freshclam ExecutableTimestamp: 1367531863 InstallationDate: Installed on 2013-04-25 (25 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: /usr/bin/freshclam -d --quiet ProcCwd: /var/lib/clamav ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f372ca408c1: mov(%rdx,%rax,8),%rsi PC (0x7f372ca408c1) ok source (%rdx,%rax,8) (0x7f3827d053a0) not located in a known VMA region (needed readable region)! destination %rsi ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: clamav StacktraceTop: ?? () from /usr/lib/libclamav.so.6 cl_engine_free () from /usr/lib/libclamav.so.6 ?? () ?? () ?? () Title: freshclam crashed with SIGSEGV in cl_engine_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: clamav (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash apport-failed-retrace raring ** Information type changed from Private to Public -- 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/1183180 Title: freshclam crashed with SIGSEGV in cl_engine_free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1183180/+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 1183180] Stacktrace.txt
** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/1183180/+attachment/3684431/+files/Stacktrace.txt -- 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/1183180 Title: freshclam crashed with SIGSEGV in cl_engine_free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1183180/+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 1183180]
StacktraceTop: ?? () ?? () ?? () ?? () ?? () -- 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/1183180 Title: freshclam crashed with SIGSEGV in cl_engine_free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1183180/+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 1183180] ThreadStacktrace.txt
** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1183180/+attachment/3684432/+files/ThreadStacktrace.txt ** Tags added: apport-failed-retrace ** Tags removed: need-amd64-retrace -- 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/1183180 Title: freshclam crashed with SIGSEGV in cl_engine_free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1183180/+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 1182978] Re: MAAS will fail to set the correct user if a previous 'maas-commission' user exists
** Changed in: maas Status: New = In Progress ** Changed in: maas Assignee: (unassigned) = Andres Rodriguez (andreserl) ** Changed in: maas Importance: Undecided = High -- 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/1182978 Title: MAAS will fail to set the correct user if a previous 'maas-commission' user exists To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1182978/+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 1182980] Re: global parameters do not apply to enlistment
** Changed in: maas Status: New = Triaged ** Changed in: maas Importance: Undecided = High -- 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/1182980 Title: global parameters do not apply to enlistment To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1182980/+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 1182978] Re: MAAS will fail to set the correct user if a previous 'maas-commission' user exists
** Changed in: maas Status: In Progress = Fix Committed -- 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/1182978 Title: MAAS will fail to set the correct user if a previous 'maas-commission' user exists To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1182978/+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
