Public bug reported:
Am trying to get NTP to work with the kernel PPS subsystem, for high-
accuracy GPS-based clocks. On startup of NTPd I see this:
Apr 1 11:18:58 doorway kernel: [ 300.387443] audit: type=1400
audit(1459505938.042:9): apparmor="DENIED" operation="open"
Sorry about this. I do believe it's addressed by our move to Mongo 3.2,
but I haven't tested that as the branch hasn't quite landed. It is
targeted to Juju 2.0 and Ubuntu 16.04 though.
Mark
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I'd love a Wily fix as well. This is preventing me from moving forward
on a project to load balance my web servers.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1445616
Title:
Thanks Robie, excited to take it for a spin :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1512980
Title:
Please enable PPS in the Ubuntu build of ntpd
To manage notifications
Paul, I believe the plan is to move to MongoDB 3.2 with Juju 2.0, which
solves the issue. I am not sure when we will have an upgrade mechanism
from 1.x to 2.x but we intend to do that in due course.
Mark
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Thanks kick-d :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1512980
Title:
Please enable PPS in the Ubuntu build of ntpd
To manage notifications about this bug go to:
I don't understand the current status of this bug.
I think what I'm reading is that this was fixed for trusty-backports
inside of the work done to close #1481737, but I'm not certain. Is there
anyone that could confirm that?
Thank you
--
You received this bug notification because you are a
Is the fix here to ensure that restarts of one are automatically
sequenced with restarts of the other service?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1460164
Title:
upgrade
In Bug #1521771, I spent some time tracking down different behavior
between the mysql-5.5 "init" and "upstart" scripts. They differ on how
many seconds are waited between the SIGTERM and SIGKILL signals are
sent. Different values can mean the difference between a slower clean
shutdown and a
Thanks for the reply.
For the mysql-5.6 package, I recommend clearly out the "init.d" script
except for the redirect to the "upstart" script.
This will avoid the false impression that the code in in the "init.d"
script is still active.
Mark
--
You
Public bug reported:
In `/etc/init/mysql.conf`, the configuration is set to wait 5 minutes
after a SIGTERM is issued before a SIGKILL is issued. The value was
intentionally set that high because sometimes the default of 5 seconds
wasn't long enough [1].
1.
Thank you Christian!
Let's go with 4.2.8 for all the obvious reasons, get it done in Ubuntu
and offer up the patch to Debian.
Mark
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs
PPS driver in
Ubuntu's build of NTP?
http://doc.ntp.org/4.2.6/drivers/driver22.html
Thanks,
Mark
** Affects: ntp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubu
I believe the fix here is in the work to rev to mongo 3.0 or 3.2 in 16.04.
Mark
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log
The proposed update works for us. When is it likely to be released as we
don't want to do this on our production servers?
--
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/1504781
Title:
** Changed in: neutron
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1236439
Title:
switch to use hostnames like nova breaks upgrades of
Public bug reported:
Steps to reproduce (using a docker container):
$ docker pull ubuntu:trusty
$ docker run --rm -it ubuntu:trusty /bin/bash
# lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
# apt-get update
# apt-get install python3.4
python3.4 is already the
Thank you @racb for taking the time to look into this and reassign it
correctly - apols for my clumsy assignment.
Dan @daniel-thewatkins - thanks dude.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
Public bug reported:
This appears at every update
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.5
ProcVersionSignature: Ubuntu 3.13.0-63.104~precise1-generic 3.13.11-ckt25
Uname: Linux 3.13.0-63-generic i686
NonfreeKernelModules: nvidia
Sorry, lost track of the bug as it fell into 100 papercuts...
if it helps I solved my ordering problem by modifying the
/lib/systemd/sysytem/openvswitch-nonetwork.service
as follows
[Unit]
Description=Open vSwitch Internal Unit
PartOf=openvswitch-switch.service
# Without
Public bug reported:
None of the dependencies for nginx-common (lsb-base and init-system-
helpers) require python support so the nginx-common package should not
force the python package to be installed. The current python
dependency should be moved to Suggests or added to the other nginx-*
Thank you for considering this request and marking it appropriately.
Please kindly suggest to the Debian folks that this future ngx-conf
utility should be in a separate package to isolate the need for python.
I only noticed this because I routinely remove anything to do with
python from my VPS
I have a the same problem.
In systemd, there are two files openvswitch-nonetwork.service
openvswitch-switch.service which are supposed to fix this problem
I am testing OpenStack with VXLAN and require
sudo ovs-vsctl add-br br-eth2
sudo ovs-vsctl set port br-eth2 tag=2001
sudo ovs-vsctl add-port
Can we put that fragment in the jujud blob, so it's installed when Juju
is installed? 99-jujud.conf might be a better name for it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
What release is this? juno, kilo, liberty?I ran a couple of tests
with Kilo and the ubuntu cloud archive and don't seem to hit this issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
This is a blocking issue for users of iscsi-based storage HW on
Openstack; is there any way of re-prioritizing this issue?
--
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/1226855
Title:
Matt, Tony, that's for the clarification. I'm still a bit confused as
to when the cloud archive used by trusty (http://ubuntu-
cloud.archive.canonical.com/ubuntu/dists/trusty-updates/) would be
updated to point to this new libvirt cloud level. (sorry for being a
newbie on this).
--
You
When will this get fixed for Trusty? that's where it was originally
reported.
--
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/1439280
Title:
Libvirt CPU affinity error
To manage
Using the patch above (that basically hacks out qemu specifically), nova boot
work fine.
Same qemu environment as I noted in my 4-23 post.
Can we get this patch out for formal review by nova folks?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Yes, this is a known issue which I can reproduce using a Solaris
installation. I still have a few outstanding bugs on my list to do
before I can start looking into this one, but I will keep this bug up to
date as/when I can start work on it - apologies for not being able to be
more specific than
I also see this is still an issue with http://ubuntu-
cloud.archive.canonical.com/ubuntu trusty-updates/kilo main
VERSION=14.04.1 LTS, Trusty Tahr
# virsh version
Compiled against library: libvirt 1.2.12
Using library: libvirt 1.2.12
Using API: QEMU 1.2.12
Running hypervisor: QEMU 2.2.0
Do we need to take into account any overhead being added by the protocol
stack along the way?
For example, if the underlying MAAS machine can be told to use 9000 byte
MTUs and jumbo frames, then each layer up could adopt that, but might
need to chop off some of that for protocol / tunnel /
Any ideas on how one could workaround this?
How to disable affinity in nova, libvirt, or qemu config's?
Some easy place in the code to hack?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Public bug reported:
Several enterprise customers have had problems bootstrapping juju,
getting errors like:
Download failed. wait 15s\nAttempt 5 to download tools from
https://streams.canonic al.com/juju/tools/releases/juju-1.21.3-trusty-
amd64.tgz...\ncurl: (6) Could not resolve host:
Confirmed in Ubuntu 14.04.02 LTS after recent upgrade from Ubuntu 12.04
LTS.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1257186
Title:
memory leakage messages (no talloc
Verified on several VPro machines in the Dell lab, with different AMT
firmware levels.
## PowerEdge T20 FW 9.0.21-build 1462works
## Laptop: E6400 FW 4.2.60-build 1060works
## Laptop: E6520 FW 7.1.4-build 1068works
## Laptop: E6430
This affects the Debian/Ubuntu mailman package. It does not affect the
GNU Mailman project.
** Project changed: mailman = mailman (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ubuntu.
** Also affects: python-boto (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-boto in Ubuntu.
https://bugs.launchpad.net/bugs/1278529
Title:
Using S3, BackendException: No
I simply issued sudo reboot and this happened. So I assume then that
I have a different issue from the original reporter? Should I open a
separate bug and stop polluting this one?
In the meantime I'll pull the requested config files.
--
You received this bug notification because you are a
/etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet manual
auto juju-br0
iface juju-br0 inet dhcp
bridge_ports eth0
/etc/network/interfaces.d is empty
--
You received this bug notification
Same as comment #44 I'm running hardware MAAS and I get this on every
deployment. If I let cloud-init error out I can get logged in and juju-
br0 is up by that point but it doesn't come up until after cloud-init
tries to do it's stuff. This makes the nodes I deploy unusable.
I'm going to see if
@dimitern Thanks for the swift reply. I'll do this now, for your
information I'm currently running juju 1.21-beta3-trusty-amd64 from the
juju-proposed ppa.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Also I've found that if I edit /etc/init/networking.conf and change the
starts on line to:-
starts on stopped cloud-init-local
Then everything works fine although I realise that this is a very poor
solution. Best I could manage with my limited upstart knowledge.
--
You received this bug
@dimitern
Quite right, it is the devel branch I'm using. I was trying to find a
new version which might already have a fix. I'm not very up on building
software based on go. I'm getting the following when I try to run go
install -v launchpad.net/juju-core/...
go build
Here is the bootstrap log created when I run juju bootstrap --to
db2.ed1.mavennetwork.co.uk --debug ~/maas-bootstrap.log
** Attachment added: maas-bootstrap.log
https://bugs.launchpad.net/juju-core/+bug/1271144/+attachment/4282230/+files/maas-bootstrap.log
--
You received this bug
And these are the juju and cloud logs from the node which was
bootstrapped. This node is working fine right now but once it is
rebooted I will get the cloud-init problem. I'll reboot it now and then
post the logs after the problematic boot.
** Attachment added: logs.zip
And lastly the logs from the node after it is rebooted. On this boot it
takes a very long time to come up as cloud-init waits for the network
bridge to come up and then eventually errors out.
** Attachment added: logs2.zip
So later on I had the ability to setup some more servers running with
QEMU and found these packages were causing the same issues:
lib32asan0 lib32atomic1 lib32gcc-4.8-dev lib32gcc1 lib32gcc1 lib32gomp1
lib32itm1 lib32quadmath0 libc6-x32 libx32atomic1 libx32gomp1 libx32itm1
libx32quadmath0
Public bug reported:
don't know! happened during update
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.4
ProcVersionSignature: Ubuntu 3.13.0-40.69~precise1-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic i686
ApportVersion:
I'm seeing the same error on my hardware MAAS cluster with the latest
maas stable and juju stable . Failing bridge on the bootstrap node is
called juju-br0. I will post more info on Monday.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Verified that the fix works on Dell PowerEdge R805 .
maas 1.7.0+bzr3299-0ubuntu1~trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1321885
Title:
IPMI detection and automatic
We'll SRU 1.7 once it's super-solid!
Mark
--
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/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
cluster
** Changed in: openstack-chef
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
https://bugs.launchpad.net/bugs/1279000
Title:
db migrate script to set charset=utf8 for all
I was having this same issue with qemu-ppc both the 2.0 version and a
handbuilt 2.1.0 version running on 14.04. By installing these packages
the error disappeared:
acl libaio1 libasound2 libasound2-data libasyncns0 libbrlapi0.6 libcaca0
libflac8 libogg0 libpulse0 librados2 librbd1 libsdl1.2debian
Public bug reported:
Please can we restore the ability to view a Juju stanza for a user of Ubuntu
OpenStack?
It should take the form:
environment-name:
type: openstack
auth-url: http://192.168.9.97:5000/v2.0
region: region
auth-mode: userpass
Public bug reported:
Please can we restore the ability to view a Juju stanza for a user of Ubuntu
OpenStack?
It should take the form:
environment-name:
type: openstack
auth-url: http://192.168.9.97:5000/v2.0
region: region
auth-mode: userpass
.
Alternatively, I can provide ssh access to an environment which
demonstrates the crash-and-restart behaviour.
Mark
--
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/1318366
Title:
jujud on state
Thanks Gustavo, this is 50% of the issues I see on cloud builds so am
excited to get a build of the tools with this fix applied. Curtis, think
we can spin a build through CI asap that would show up in the testing
tools bucket on S3?
--
You received this bug notification because you are a member
Yes, I saw the same restarting of Mongo, looks like every 10-15 seconds.
--
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/1318366
Title:
jujud on state server panic misses
Attached is a dump of the Juju database in this case.
** Attachment added: dump.tgz
https://bugs.launchpad.net/juju-core/+bug/1318366/+attachment/4164924/+files/dump.tgz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in
After some experiments in compression options, here are all the Juju
logs you could ever want :)
http://people.canonical.com/~mark/juju-server-crash-logs.tar.xz
68M compressed, about 1.9G uncompressed. That's /var/log/juju/ from
machine 0.
--
You received this bug notification because you
Here is a snippet of syslog showing two cycles of Mongo starts and
restarts. This is happening constantly!
Gustavo and I are wondering whether the numactl advice might be
relevant.
** Attachment added: syslog.mongorestarts.log
Digging in further, it appears that jujud is writing to /etc/init/juju-
db.conf (the Upstart job for its database) every few seconds. I'll file
a separate bug about this because it plausibly is the root cause of the
mongo restarts we're seeing.
--
You received this bug notification because you
I've got this in a live environment from the cloud-installer too. How do
I know where to point mongodump?
--
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/1318366
Title:
jujud on
** Changed in: juju-core
Importance: Medium = High
** Changed in: juju-core
Milestone: None = 1.21-alpha1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
logs
Verified. Thanks!
** 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 cobbler-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/833994
Title:
debian-installer does
I have resolved this for this install; this box had an actual user
account called `haproxy`. I renamed this account to something else and
attempted the update again. It was successful that time.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
# this config needs haproxy-1.1.28 or haproxy-1.2.1
global
log 127.0.0.1 local0
log 127.0.0.1 local1 notice
#log loghostlocal0 info
maxconn 4096
#chroot /usr/share/haproxy
user haproxy
group haproxy
daemon
#debug
Public bug reported:
Doing release upgrade from 12.04 to 14.04.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: haproxy 1.4.24-2
ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
Uname: Linux 3.2.0-36-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Fri
** Attachment added: modified.conffile..etc.haproxy.haproxy.cfg.txt
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1334958/+attachment/4140330/+files/modified.conffile..etc.haproxy.haproxy.cfg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
Starting an lxc container, defined via the XML below, results in the
host's eth0 getting disconnected. I see DHCP messages beng generated and
notice this process:
root 5640 0.0 0.0 10232 2416 ?Ss 13:05 0:00
dhclient -1 -v -pf /run/dhclient.eth0.pid -lf
** Tags added: 14.04
--
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/1315188
Title:
No init.d script included in icehouse ubuntu packaging
To manage notifications about this bug
*** This bug is a duplicate of bug 375625 ***
https://bugs.launchpad.net/bugs/375625
screen not freezing up nor turning zombie, but i got the error described
above. it happens reliably. i just manufactured Ubuntu 14.04. when
exiting using ^A^D it does exactly what this bug describes. my
*** This bug is a duplicate of bug 375625 ***
https://bugs.launchpad.net/bugs/375625
also, if i use screen directly, e.g. replace byobu-screen with just
screen, it works as expected.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
To add to this, as I also am experiencing this problem:
My maas has 2 nics and 2 networks:
Outbound eth1: talks to the world (or in thsi case my partner OEM's lab
network
Private eth0: talks only to maas-create nodes. Call it 10.0.0.0/24 .
I've set up maas as DHCP DNS manager for eth0. I
Actually, my last comment encompasses a different problem (that of
isolation), so ignore it.
But do count this as a vote to some kind of NAT on/off tooling in
MAAS.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
don't see a significant moral issue.
Mark
--
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/1305839
Title:
FFe: Support for Third Party Driver Installation
To manage notifications about
The key difference in my mind is recoverability. In the server case, the
install is by nature largely automated, and often will fail altogether
if you don't for example have the ability to configure your hard drives.
Perhaps an analogy for the desktop would be to ask the question - what
if a
Thanks all for the comments and discussion.
Responding to some key points:
* building confidence in code changes both for this FFE and subsequent
SRUs is important, the archive and RM teams have a mandate to seek
comfort on that front before ack'ing an upload under either
circumstances
* in
Also, thank you Adam for pointing out that we need to do the same sort
of ubiquity- and jockey-like calling out of the issues associated with
binary blobs on servers that we do on the PC. I'll get the MAAS folks to
make that very clear on the node page as a way of socialising the
benefits of open
I have not seen any reportable breakage; admittedly I have not fully
stressed maas nor used all of its functions.
--
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/1302741
Title:
We decided that we should land everything but HA and VLAN work this week in
a stable release to minimize the risk that either of those changes could
have on overall stability in the release. However, HA and VLAN work is
underway, and much of it has already landed, and the first HA support is
** Changed in: juju-core
Importance: High = Critical
--
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/1208430
Title:
mongodb runs as root user
To manage notifications about
Reducing the security implications of running MongoDB is an important
thing for us to do. It's not quite critical, because nobody is asking
for it directly now, and the risk is still somewhat limited. But there
is a risk, and I think the general policy of treating even security --
even
** No longer affects: neutron
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1284718
Title:
interface-attach to external network a) works and b) results in
undeletable instances
ignore last comment.
A fresh import works.until you reboot. Even if you changed nothing else in
the configuration of the server or maas, enlistment will no longer work until
you do another maas-import-pxe-files at which time things will work again.
** Tags added: blocks-hwcert-server
**
I'm seeing this error in the Garage MAAS today. As it happens, also have
two interfaces on the network on that machine. Will try reducing to one
and reboot.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
A fresh import works.until you reboot. Even if you changed nothing
else in the configuration of the server or maas, enlistment will no
longer work until you reboot.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Was not able to reproduce after a reboot.
--
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/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this
** Changed in: juju-core
Milestone: None = 1.18.0
--
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/1208430
Title:
mongodb runs as root user
To manage notifications about this
@jamie
However, I don't feel the download size is itself a blocker. We can
perform uploads for everything at first, figure out how to be
smarter/more selective later and along the way work with upstream on
dynamic linking if that makes sense.
I think that is particularly true in *this* case
@gustavo
I think it is right that there are many people in the go community who
would welcome dynamic linking in golang-go, but I also think that if we
want to have it, we need to do the work to add it there. Now that we
have to have Arm64 and Power, if we are going to be investing in
improving
@martin
Traditionally the Tech board has nacked everything in main which pulls
code from third-party sources, i. e. installer packages. Packages in
main must not enable any third-party PPA, pull code or binaries from an
upstream site and run it, and so on.
I think a key point here is that the
@all
Given the timeline and the various other bits on our roadmap, I think
main inclusion for juju core is *not* critical this cycle. We would
rather get agreement, and get this done the right way than create last
minute chaos for the release. But, it is critical that we sort this
and the MRE
that already exists and is quite widely used.
--Mark
On Wed, Mar 26, 2014 at 5:54 PM, Adam Conrad adcon...@0c3.net wrote:
@Mark
So, if we can build them with the packages, what's stopping us from
having a package that includes the bits, and even depends on the right
things to set up a simplestreams
@adam
We *can* build and include tools binaries in the package. And in fact
for many tools, we extract them from the builds, and upload them to a
central distribution point (which uses the same toolchain as the ubuntu
cloud images catalog -- simplestreams.
But, we don't distribute the tools
This bug is also impacting the juju-mongodb package, and therefore juju
on ppc64el.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1294747
Title:
mongodb fails assertion on ppc64el
Hi Lezgin,
This is already in 14.04. You can test right away.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/833994
Title:
debian-installer does not support https when
I saw similar issues at IBM on 10 March. Same look to the logs, same
success with ipmitool. After an apt-get upgrade on the 11th (trusty) and
a reboot, the issues did not appear for me. I did not refresh after the
11th, though.
--
You received this bug notification because you are a member of
Dave, can you turn you hack of your working copy into a branch proposal?
** Changed in: juju-core
Importance: High = Critical
--
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/1273769
1 - 100 of 577 matches
Mail list logo
