** Branch linked: lp:~gmb/maas/dustins-patch
--
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/1310846
Title:
amt template gives up way too easily
To manage notifications about this bug
AFAICS, kernel-libipsec is not part of the Ubuntu strongSwan package,
hence it can't be enabled.
Not sure if there are that many uses cases for kernel-libipsec on a
standard Linux distribution to justify its inclusion; kernel-netlink is
preferable on 95% of use cases.
Regards
Martin
--
You
Supporting flexible locations of qemu and alternate location for the
ovmf BIOS would allow to get rid of patches. So sounds useful. Note that
the 14.04 (Trusty) release of Ubuntu (as well as the 13.10 (Saucy)
release) were not using the Xen version of qemu for xl but the generic
upstream qemu
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1310076
Title:
lost
** Changed in: juju-core/1.18
Status: Triaged = In Progress
** Changed in: juju-core/1.18
Assignee: (unassigned) = Nate Finch (natefinch)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server
@Thomas, Simon, can you reveal whether there are maybe special options enabled
in the global config or for the resource configs? Both other sides are running
12.04 (Precise) and have not been upgraded, right?
The difference is that Simon did not reboot the upgraded machine but Thomas did
and
While debian/strongswan-plugin-kernel-libipsec.install lists
usr/lib/ipsec/plugins/libstrongswan-kernel-libipsec.so the strongswan-
plugin-kernel-libipsec package does not actually include that file.
The reason for this is how dh_install is called in debian/rules, due to
the
I have the same symptoms on my kernel 3.2 cluster indeed:
drbdsetup show all
Could not connect to 'drbd' generic netlink family
I'm sorry I didn't notice this in my tests - I never use drbdsetup which
is supposed to be a low-level tool.
--
You received this bug notification because you are a
On Mon, Apr 14, 2014 at 06:10:31PM -, Mads Martin Jørgensen wrote:
[...]
...All of
the services provided on a Ubuntu system will potentially break, since
it does not conform to the json standard that everyone else does.
That
On Mon, Apr 14, 2014 at 08:39:01PM -, Jeroen van der Ham wrote:
[...]
...I'm now
trying to convince all package maintainers to use the --local-service
option by default.
AIUI, you've effectively convinced Ubuntu, by virtue of
Hm, ok. So we where only using drbdadm in testing? In theory there is
also a compat version of drbdsetup there and like for drbdadm the
fallback should be drbdsetup-83 (in /lib/drbd) ...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Antarctica/Macquarie$
This rings a bell, but I think it's a different (perhaps related) bug
that I can't find right now. This bug is when the system timezone
doesn't get picked up by default at all.
I don't understand why PHP is so special it needs to be told
indivdually about my time zone,
Looks very much like drbdsetup does not fall back to the 8.3 version, even
though it should according to this commit:
http://git.drbd.org/gitweb.cgi?p=drbd-8.4.git;a=commit;h=b5ef99654f8008a7b6632261f39fc908b4e84210
Anyway, executing /lib/drbd/drbdsetup-83 instead of /sbin/drbdsetup seems
i see no uncommon options in my configs, i built the cluster basically of
linbits dox.
i run a standard pp with no extra repos and did not upgrade to 8.4 whatsoever.
(the updated) node storage0:
root@storage1:~# ssh storage0 cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
I did some more digging through the logs, and it turns out that the command is
called, but fails due to not being called as root user.
For access to the zfs stats you need to be root. This worked ok in 13.10, but
it looks like the dfree command is not executed as root user anymore. I would
call
thx stefan lionel, will try your suggestions ASAP.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
To
@Renan
I believe Dimitri made this change to avoid breaking php5-fpm on upgrade
from Precise to Trusty, because the previous version of upstart needs to
have support for the new feature before we can use it.
AFAICT, this means that we can fix this in Trusty+1, but it will remain
like this in
As a workaround verified at my end, you may simply symlink the 8.3 tools
somewhere in the path, so that drbdsetup will find them:
ln -s /lib/drbd/drbdsetup-83 /sbin
Alternatively, you may revert drbd-utils to the 8.3 bersion which is still
available from the release repository and freeze it
** Also affects: elinks (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733482
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to elinks in Ubuntu.
** Also affects: juju-mongodb (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
Status: Triaged = Invalid
** Changed in: juju-core
Milestone: 1.19.1 = None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I can confirm the problem with the netlink error.
Apr 20 11:54:59 node1 lrmd: [3636]: info: RA output:
(res_drbd_1:0:monitor:stderr) Could not connect to 'drbd' generic
netlink family
I'm using 12.04 with 3.2 kernel (3.2.0-60-generic).
The Pacemaker resource agent is also shipped in a new
I cannot specify it further, since it's our own API that communicates
via JSON that broke, due to php-json in Ubuntu not conforming to the
JSON standard. Time will tell how many will get hit by this bug. Might
be zero, might be thousands. Fact of the matter is still that it accepts
JSON input that
** Information type changed from Private Security to Public Security
** Also affects: python-django (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: python-django (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: python-django (Ubuntu
** Information type changed from Private Security to Public Security
** Also affects: python-django (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: python-django (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: python-django (Ubuntu
** Information type changed from Private Security to Public Security
** Also affects: python-django (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: python-django (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: python-django (Ubuntu Trusty)
On 18 April 2014 11:58, Renan Gonçalves renan.sad...@gmail.com wrote:
The package 5.5.9+dfsg-1ubuntu3 have the correct upstart script with
reload signal USR2, which works great on Ubuntu Trusty since it uses
upstart = 1.10.0
The fix for this bug introduces a new package, called
From my (quick) reading of the source code, drbdadmin works because it adds
/lib/drbd to the path using add_lib_drbd_to_path(), and drbdsetup seems not to.
One reason for this could be that the driver calls drbdsetup with an abolute
path and the source says in case drbdsetup is called with an
This bug was fixed in the package python-django - 1.6.1-2ubuntu0.1
---
python-django (1.6.1-2ubuntu0.1) trusty-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.1.1-2ubuntu1.10
---
python-django (1.1.1-2ubuntu1.10) lucid-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.1.1-2ubuntu1.10
---
python-django (1.1.1-2ubuntu1.10) lucid-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.6.1-2ubuntu0.1
---
python-django (1.6.1-2ubuntu0.1) trusty-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.6.1-2ubuntu0.1
---
python-django (1.6.1-2ubuntu0.1) trusty-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.1.1-2ubuntu1.10
---
python-django (1.1.1-2ubuntu1.10) lucid-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.3.1-4ubuntu1.9
---
python-django (1.3.1-4ubuntu1.9) precise-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.4.1-2ubuntu0.5
---
python-django (1.4.1-2ubuntu0.5) quantal-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.3.1-4ubuntu1.9
---
python-django (1.3.1-4ubuntu1.9) precise-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.4.1-2ubuntu0.5
---
python-django (1.4.1-2ubuntu0.5) quantal-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.5.4-1ubuntu1.1
---
python-django (1.5.4-1ubuntu1.1) saucy-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.5.4-1ubuntu1.1
---
python-django (1.5.4-1ubuntu1.1) saucy-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.5.4-1ubuntu1.1
---
python-django (1.5.4-1ubuntu1.1) saucy-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.3.1-4ubuntu1.9
---
python-django (1.3.1-4ubuntu1.9) precise-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
This bug was fixed in the package python-django - 1.4.1-2ubuntu0.5
---
python-django (1.4.1-2ubuntu0.5) quantal-security; urgency=medium
* SECURITY UPDATE: unexpected code execution using reverse()
(LP: #1309779)
- debian/patches/CVE-2014-0472.patch: added filtering to
Hi Martin,
strongswan-plugin-kernel-libipsec does provide the plugin (or
supposedly) in Ubuntu 14.04.
There are two reasons (or at least mine) to use kernel-libipsec, one is
that kernel-libipsec provides a separate interface so that
filtering/inspecting the packets would be easier with iptables,
On Tue, Apr 22, 2014 at 11:31:36AM -, Mads Martin Jørgensen wrote:
3) Move all servers that use JSON away from Ubuntu and on to something
with a JSON standard conforming php-json.
For other readers, I would point out that AIUI Fedora (and thus RHEL and
CentOS) and Debian (and thus Ubuntu)
I would rather fix drbdsetup in the same way drbdadm works (so add the
libpath). That way the compat binaries are not exposed in the normal
search path. Which I believe is intentional as from the user perspective
there should be only one command. I am working on a patch and some test
binaries
Thanks for your reply.
I not tried xen trusty package for now but only a fast watch on debian folder
of packages source.
seabios and upstream qemu is not specified on configure for what I saw
(./configure --enable-xend --prefix=/usr) and I think should be done to have
seabios and upstream qemu
*** This bug is a duplicate of bug 1243076 ***
https://bugs.launchpad.net/bugs/1243076
** This bug has been marked a duplicate of bug 1243076
libapache2-mod-auth-mysql is missing in 13.10 amd64
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: spamassassin (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.net/bugs/1310307
Title:
spamassassin postinst uses a login shell
To
Ah... I think that probably is also good put qemu-system-x86 as dipendency
since is default for disks on file also on pv domUs.
Is used also for vnc (and spice basic support if my patch will be accepted on
xen 4.5) on pv domUs.
Then using the 4.4 xl seem to me a few cases where it is not used,
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I was unable to link the upstream bug to this one. Please can you
comment here when there's some resolution on the debugging proceeding in
the upstream bug?
It sounds to me that not being able to ensure a binary
** Patch removed: openssh_enable_btmp_saucy.debdiff
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/743858/+attachment/4055600/+files/openssh_enable_btmp_saucy.debdiff
** Patch removed: openssh_enable_btmp_precise.debdiff
Also lost my slave on prod system today, pacemaker,crm cluster with
drbd.
lrmd: [1952]: info: RA output: (res_drbd_1:1:monitor:stderr) Could not
connect to 'drbd' generic netlink family
My resources are marked as Unconfigured on slave, but still Primary on
master.
Have not rebooted.
What is
New version of the debdiff from new version after security SRU
** Patch added: openssh_enable_btmp_precise_v2.debdiff
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/743858/+attachment/4092562/+files/openssh_enable_btmp_precise_v2.debdiff
--
You received this bug notification because
New version of the debdiff from new version after security SRU
** Patch added: openssh_enable_btmp_saucy_v2.debdiff
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/743858/+attachment/4092561/+files/openssh_enable_btmp_saucy_v2.debdiff
--
You received this bug notification because you
Linbit's Lars Ellenberg confirmed on the ML that adding /lib/drbd to the
path won't fix drbdsetup in all cases: drbdsetup-83 has to be in the
same directory as the drbdsetup, and it also applies to drbdadmin.
On Tue, Apr 22, 2014 at 01:56:16PM +0200, Lionel Sausin wrote:
(...)
Is the correct
Anyone seeing the error message, try the proposed package on the
upgraded server. Those are for Precise (12.04) and you will need only
the one matching your installation (64bit or 32bit).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Proposing to fix this by adding the patch in drbdsetup, too. See attached
debdiff. Test packages can be found at
http://people.canonical.com/~smb/lp1185756/
** Patch added: Debdiff of proposed fix.
Public bug reported:
When powering multiple nodes on at once, in different sub-processes. The
following error is generated and the node is not powered off or on
accordingly.
Traceback (most recent call last):
File stdin, line 2, in module
File
qemu-system-x86 is on the recommends list which will pull in upstream qemu.
Right now the build of Xen modifies the source in a way to look for
qemu-system-i386 on the path provided by qemu. This also causes seabios to be
used. ovmf would need testing. Ovmf was not really looked at. So for the
@Stefan, your proposed fix (http://people.canonical.com/~smb/lp1185756/)
worked for me on Precise 64bit with kernel 3.2. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Public bug reported:
After installing a fresh ubuntu 14.04 (twice), following every step of
this doc :
http://maas.ubuntu.com/docs/install.html#disc-install
I can't access the webui on http://ip_address/MAAS
I always get the error :
Internal Server Error
The server encountered an internal
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1311158
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1281758
Public bug reported:
byobu-screen seems badly broken with regard to 'ctrl-a'.
fresh instance/user:
* run 'byobu-screen'
* hit 'ctrl-a'
* answer '1' to the ctrl-a prompt
byobu (screen) dies.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: byobu 5.77-0ubuntu1
ProcVersionSignature: User
** Changed in: juju-deployer
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-jujuclient in Ubuntu.
https://bugs.launchpad.net/bugs/1284690
Title:
all watcher api regression
To manage
Sorry for my bad english.
I not understand if you mean right.
About seabios, upstream qemu and ovmf from distro package I mean simply for
example:
for seabios ./configure ... --with-system-seabios=/usr/share/seabios/bios.bin
and remove tools-firmware-seabios-packaged patch.
About ovmf is better
** Changed in: byobu (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1311177
Title:
byobu-screen ctrl-a causes death
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: byobu (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-0472
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-0474
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
*** This bug is a duplicate of bug 1311151 ***
https://bugs.launchpad.net/bugs/1311151
Hi Jeff, thanks for the detailed bug report, I'm duping this against bug
1311151 since this seems to be the main issue and how you workarounded
the problem. Given the other symptoms you describe this is
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-0472
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-0473
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
I saw now the test I did with qemu from debian packages and I always use
/usr/bin/qemu-system-x86_64, since xen not use emulated cpu _64 or not
should not be different but probably is different for spice-server that
if I remember good have problem on 32 bit.
--
You received this bug notification
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-0473
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-0474
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
Linking the /lib/drbd/drbdsetup-8.3 to /sbin did NOT solve the problem
for me. Had to revert to to old packages then everyting worked after
cluster restart.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
** Changed in: python-seamicroclient (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-seamicroclient in Ubuntu.
https://bugs.launchpad.net/bugs/1311140
Title:
powering multiple
So we talk about different sides. Debian has not, yet packaged up Xen-4.4
(there was a post to Debian today asking how we can change that), I did package
Xen-4.4 for Ubuntu Trusty (14.04). That does a lot of the things you were
suggesting. Maybe not all in a way that will be ok with Debian. I
The proposed package fixes the issue at my end too.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756
Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
To
@Rocco, could you try whether the proposed packages from comment #59
would work? The error message only in the drbdsetup code when it fails
to find the compat binary. So I hope that you will not loose the
connection again. I know it really would suck if not but it would give
higher confidence in
I'm getting this same message when trying to run sudo update-
pepperflashplugin-nonfree --install. I'm having problems getting flash
plugin to work with Chrome and trying the method @
https://wiki.ubuntu.com/Chromium/Getting-Flash#help all I end up with is
another problem.
Mine is an Upgrade of
** Patch added: Final debdiff patch
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1308974/+attachment/4092743/+files/debdiff.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
First news from the upstream bug:
It seams as if the problem was not the file contents, but the file name,
the second 'o' allegedly was a cyrillic o...
*damned trap*
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
I've found that if I perform a fresh install, without internet access
(while still having a fully configured network), that the install works
and I have full access to the web ui.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
I tested this in my environment and it seems to work properly.
-Juan
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1302633
Title:
pacemaker: Discarding cib_apply_diff message
** 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 pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1302633
Title:
pacemaker: Discarding cib_apply_diff message
Public bug reported:
REPRO STEPS:
Trying to ssh into iloCM from an Ubuntu 14.04 terminal ssh client
(OpenSSH_6.6, OpenSSL 1.0.1f 6 Jan 2014). CM was running 1.20p20.
$ssh -vvv administra...@cm-deke.americas.hpqcorp.net
Connection fails with this message:
debug1: sending SSH2_MSG_KEXDH_INIT
Logged a public bug
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1311250
** Information type changed from Proprietary to Private
** Also affects: openssh (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Private to Public
** No longer affects:
Julian: THAT makes more sense... perhaps this would be less confusing,
from a user standpoint:
MAC Address - Enter the BMC's MAC Address here if you are NOT using DHCP
to assign BMC IP Addresses
** Changed in: maas
Status: Incomplete = New
--
You received this bug notification because
You have been subscribed to a public bug:
Currently upgraded from 12.04 to 14.04 and am experiencing issues with
start openipmi via the init.d script. I did some digging around and it
appears that the package
linux-image-extra-3.13.0-24-generic
is missing the ipmi_msghandler.ko. It provides
Please attach your patch and I'll see if it adheres to Ubuntu SRU
policy.
** Package changed: linux (Ubuntu Trusty) = openipmi (Ubuntu Trusty)
** Changed in: openipmi (Ubuntu Trusty)
Status: Invalid = In Progress
--
You received this bug notification because you are a member of Ubuntu
Hi Julian,
I've got several MAAS servers that seem to suffer the same fate,
depending on what your definition of Access the internet is.
We first saw this at the Orange Box sprint in london where nodes could
be deployed via d-i which was pulling packages from MAAS's squid-deb-
proxy, IIRC,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1304613
** Changed in: maas (Ubuntu)
Status: In Progress = Fix Released
--
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/1268795
Title:
unable to automatically commission Cisco UCS
Then again, perhaps something as simple as a 'maas-enable-nat' command
for these simple cases would be sufficient so new users don't have to
also understand iptables... and makes it optional on the maas server so
you can or can not enable it... maybe it is a per-cluster-controller
thing, as my
As for your question about the region... I don't know... that's
operating at scale. The question there is probably one of hierarchy...
for example, would you have multiple, linked region controllers, or more
like a few region controllers and several cluster controllers under
each?
And in that
This is a result of a deliberate upstream change in OpenSSH 6.6, to
extend the list of supported ciphers. It is not appropriate for Ubuntu
to diverge from this default by disabling any of these ciphers.
Depecation of older ciphers should be done upstream first.
As with other servers that limit
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
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.
@smb I'm afraid I can't. The problem with the upgrade of drbd8-utils
cause downtime on your main (production) DB-cluster today.
I can look though the logs tomorrow, but it was the drbd ocf
master/slave in pacemaker that was failing, causing drbd to get
unconfigured on both nodes.
--
You
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1304518
1 - 100 of 157 matches
Mail list logo
