@ 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:
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
** 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
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
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
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.
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
** 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
** 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
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
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
--
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
** 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
** 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
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
** 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
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:
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:
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:
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
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
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
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:
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
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.
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
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
** 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
** 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
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
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.
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
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
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
** 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.
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
** 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.
** 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.
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,
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
**
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
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.
** 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
** 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
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
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,
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.
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.
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
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.
** 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
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
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.
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
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.
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.
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
*** 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,
*** 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
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.
** 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
** 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
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
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
** 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:
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
** 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,
** 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
** 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
** 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
70 matches
Mail list logo
