I'm afraid I was unable to reproduce this, so we're probably doing
something different. Could you please describe exactly how you're
starting ssh?
--
Lucid: Recent update to ssh mean ssh-askpass-gnome fails to recognize the
correct password
https://bugs.launchpad.net/bugs/535123
You received
I mean, you gave me the options - I'm more interested in whether you're
starting it from a terminal, Places - Connect to Server..., whether
this message actually appears when you run ssh-add, or what.
--
Lucid: Recent update to ssh mean ssh-askpass-gnome fails to recognize the
correct password
Also, are you using the real ssh-agent, or some inferior substitute
(e.g. gnome-keyring-daemon)?
--
Lucid: Recent update to ssh mean ssh-askpass-gnome fails to recognize the
correct password
https://bugs.launchpad.net/bugs/535123
You received this bug notification because you are a member of
I'm aware of OpenSSH 5.4p1, but I don't think it's suitable for ramming
past feature freeze; it's quite a big new feature release and I don't
think that these features are essential for Lucid - I'd rather have the
devil we know. I will upgrade to 5.4p1 in Lucid+1.
--
[LUCID] OpenSSH 5.4p1
I understand your concern, but I would rather that 10.04 LTS lacked
these features than that we introduced them and they were then found to
be broken in some way. There'll be more releases ...
--
Update to OpenSSH 5.4p1
https://bugs.launchpad.net/bugs/535029
You received this bug notification
Yes, I think you're probably right. I was considering a few possible
alternatives and this seems the least bad.
--
hardy: openssh-server oom_adj can lead to denial of service
https://bugs.launchpad.net/bugs/293000
You received this bug notification because you are a member of Ubuntu
Server
I understood the oom_adj patch perfectly, having written it. Apparently
I misunderstood how Upstart's 'oom' stanza worked though ...
Thanks for the analysis; I'll look into this.
** Tags added: regression-potential
--
hardy: openssh-server oom_adj can lead to denial of service
You can work around this by running 'stty iutf8' on the server each time
you ssh somewhere. Unfortunately fixing this requires an extension to
the SSH protocol - see http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=337041 for the gory details - so it won't be a
quick process.
** Bug watch
On Thu, Feb 11, 2010 at 12:42:35AM -, J. Javier Maestro wrote:
Can't anyone follow the suggestion of creating an extra openssh-
smartcard-opensc and openssh-smartcard-pkcs11 that would use the opensc
flag or the pkcs11 patch mentioned in this bug?
If there is no serious reason to avoid
** Changed in: openssh (Ubuntu)
Importance: Undecided = Medium
** Changed in: openssh (Ubuntu)
Status: New = Triaged
--
[LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
https://bugs.launchpad.net/bugs/531912
You received this bug notification because you are a
Public bug reported:
Binary package hint: samba
/etc/logrotate.d/samba produces error output, because the smbd stanza
calls 'invoke-rc.d --quiet samba reload /dev/null' in a postrotate
stanza (no stderr redirection, nor should there be). This should be
updated to use Upstart's facilities. I
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Triaged = Fix Committed
--
postfix should be preseeded appropriately when pulled in by the UEC cluster
controller installer target
https://bugs.launchpad.net/bugs/455746
You received this bug notification because you are a member of Ubuntu
I think eucalyptus-udeb should take care of this, since it's the only
thing with policy knowledge about whether it's installing a CLC rather
than something else.
** Package changed: debian-installer (Ubuntu) = eucalyptus (Ubuntu)
--
postfix should be preseeded appropriately when pulled in by
** Also affects: multipath-tools (Ubuntu)
Importance: Undecided
Status: New
--
[Patch] Multipath Tools: modify the path priority tool for Intel Modular Server
support
https://bugs.launchpad.net/bugs/520309
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: openldap (Ubuntu)
Assignee: Ubuntu Development Team (ubuntu-dev) = (unassigned)
** Changed in: update-manager (Ubuntu)
Assignee: Ubuntu Development Team (ubuntu-dev) = (unassigned)
--
package update-manager 1:0.93.18 failed to install/upgrade: ErrorMessage:
SystemError
this is working correctly - can this be pushed to karmic-updates
--
Strange behavior of libkrb5 since karmic ...
https://bugs.launchpad.net/bugs/489418
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in ubuntu.
--
Public bug reported:
Binary package hint: bacula
Hi,
Can you please upgrade the package to the latest official stable version
?
Here is the Changelog from http://www.bacula.org/en/?page=news
Changes since 3.0.3a (the last Bacula Project release):
konqueror (and KDE in general) uses libssh for its sftp kioslave, not
openssh. Reassigning.
** Package changed: openssh (Ubuntu) = libssh (Ubuntu)
** Summary changed:
- SFTP failure - kubuntu - KDE4.4 RC2
+ doesn't support AES CTR modes
--
doesn't support AES CTR modes
How are you connecting to the other machine? If it's by ssh in a
terminal, then this might be openssh's fault (although I have precisely
no idea how; this just doesn't fit any reasonable model of how ssh works
...). However, I think it's more likely that you're using some KDE
feature for
I was a bit puzzled by this until I realised that our current wget
package doesn't actually support SOCKS, so this test could never work.
(Feel free to mark this bug as also affecting Ubuntu wget; it used to
support this, but I don't know what would be involved in reintroducing
it.)
With OpenSSH
See also:
http://www.mail-archive.com/w...@sunsite.dk/msg10824.html
--
“dynamic” application-level port forwarding non-functional
https://bugs.launchpad.net/bugs/391874
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
Promoted, now that it's seeded.
** Changed in: irqbalance (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
MIR for irqbalance
https://bugs.launchpad.net/bugs/488835
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance
Promoted, now that it's seeded.
** Changed in: tickcount (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
[MIR] tickcount
https://bugs.launchpad.net/bugs/489264
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tickcount in
If you enter your login password, does it work? If so, then this
certainly is not a problem with ssh-keygen, but rather some problem with
getting ssh or sshd configured correctly - it's not that your login
password is attached to your key somehow, but rather that ssh is falling
back to requesting
If upstream are so convinced that this is a bad idea, then I doubt they
would have made PermitRootLogin default to yes! I do not intend to
deviate from upstream in the Debian or Ubuntu packaging on this matter.
If you want this changed, convince upstream.
We wrote down our thoughts on this in
Hi,
1st of all thank for your quick answer ...
I have downloaded your debdiff, applied, builded, upgraded, tested and
finally, all I can say IT WORK !!!
Keep up the good work !!!
A++
--
Latest Stable is 2.1.1
https://bugs.launchpad.net/bugs/509078
You received this bug notification because
r348 upstream was supposed to remove this requirement. Please revert
this - it's a serious bug for vm-builder to be making decisions about
which boot loader is installed on the host system.
--
python-vm-builder lacks grub dependency
https://bugs.launchpad.net/bugs/331595
You received this bug
Definitely not ready to go yet though; note e.g. the sh -x in there for
testing. I don't have time to work on this further so anyone else
should feel free to pick it up given this basis.
--
grub2 support for guests = karmic
https://bugs.launchpad.net/bugs/509609
You received this bug
Public bug reported:
Binary package hint: openvpn
Hi,
Can you please upgrade the package to the latest official stable version
?
Here is the Changelog from http://openvpn.net/index.php/open-
source/downloads.html :
OpenVPN 2.1.1 -- released on 2009.12.11 (Change Log)
Changes include:
*
As described upstream, this appears to be the fault of seahorse, not
openssh.
** Changed in: openssh (Ubuntu)
Status: Confirmed = Invalid
--
ssh-add -D deleting all identities does not work. Also, why are all identities
auto-added?
https://bugs.launchpad.net/bugs/505278
You received
= Triaged
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
--
sshd stop on two SIGHUP
https://bugs.launchpad.net/bugs/497781
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu
** Changed in: openssh (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Bug watch added: Debian Bug tracker #530692
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530692
** Also affects: openssh
** Changed in: openssh (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
--
Banner displays two \
https://bugs.launchpad.net/bugs/425346
You received this bug notification because you are a member of Ubuntu
** Changed in: openssh (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
--
GSSAPI Cascading Credentials support
https://bugs.launchpad.net/bugs/416958
You received this bug notification because you
** Changed in: openssh (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
--
CVE-2008-5161: OpenSSH CBC plaintext recovery
https://bugs.launchpad.net/bugs/379329
You received this bug notification because you
** Changed in: openssh (Ubuntu)
Status: Confirmed = Fix Committed
--
force-command unable to pass arguments along to internal-sftp
https://bugs.launchpad.net/bugs/362511
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in
** Changed in: openssh (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Bug watch added: Debian Bug tracker #514313
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514313
** Also affects: openssh (Debian
** Changed in: openssh (Ubuntu)
Status: Fix Committed = Fix Released
--
pam_mount unable to unmount needs root priv
https://bugs.launchpad.net/bugs/117736
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
** Bug watch added: Debian Bug tracker #505378
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505378
** Changed in: openssh (Debian)
Importance: Undecided = Unknown
** Changed in: openssh (Debian)
Status: New = Unknown
** Changed in: openssh (Debian)
Remote watch: None = Debian
** Bug watch added: Gentoo Bugzilla #244222
http://bugs.gentoo.org/show_bug.cgi?id=244222
** Also affects: gentoo via
http://bugs.gentoo.org/show_bug.cgi?id=244222
Importance: Unknown
Status: Unknown
** Also affects: openssh via
The -s argument shouldn't matter, for what it's worth. The important
thing is just that it has type=walrus.
When the node installation fails, could you switch to tty2 and run
'EUCA_FIND_COMPONENT_DEBUG=1 euca_find_component walrus', and copy the
output here? You might have to transcribe the
I built new packages based on Evan's debdiff and have deployed them.
This removed all the impact we were seeing with single password errors causing
account lockout.
This bug has massive impact on user experience and I would encourage the
update to be released.
--
Strange behavior of libkrb5
I haven't noticed this being a problem with Karmic's qemu-kvm
0.11.0-0ubuntu6.3. Feel free to close this out if you think it's
appropriate. Thanks.
--
requires -cpu qemu32 on i386 host to boot karmic PAE kernels
https://bugs.launchpad.net/bugs/393671
You received this bug notification because
Instead of -n $2, just use the le-nl operator in place of le.
--
[lucid] libvirt-bin fails to install (sed: can't read
/etc/apparmor.d/usr.bin.virt-aa-helper)
https://bugs.launchpad.net/bugs/493582
You received this bug notification because you are a member of Ubuntu
Server Team, which is
that cloud-output.log is affected by LOGLEVEL (LP: #458001)
[ Colin Watson ]
* Move cluster private interface selection forward to just after network
configuration (LP: #455816).
* Add the CC's IP address as an explicit TXT record in the Avahi
advertisement, and make use
that cloud-output.log is affected by LOGLEVEL (LP: #458001)
[ Colin Watson ]
* Move cluster private interface selection forward to just after network
configuration (LP: #455816).
* Add the CC's IP address as an explicit TXT record in the Avahi
advertisement, and make use
*** This bug is a duplicate of bug 407428 ***
https://bugs.launchpad.net/bugs/407428
** This bug has been marked a duplicate of bug 407428
worker signal mask inherited by children
--
bad signal mask of ssh sessions
https://bugs.launchpad.net/bugs/412972
You received this bug notification
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: eucalyptus (Ubuntu)
Assignee: Mathias Gug (mathiaz) = Colin Watson (cjwatson)
--
When installing a UEC cluster, the prompt for the private interface is
displayed after the Installation complete dialog
Reopening for Lucid as we want to fix this a different way there (with
an explicit TXT record).
** Changed in: eucalyptus (Ubuntu)
Status: Fix Released = Triaged
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Changed in: eucalyptus (Ubuntu
Steve, I chose -54 because that's the version in Debian which
transformed grub into a dummy transitional package. Theoretically at
some point we might get round to merging that.
I'm afraid there's not a whole lot we can do about the fact that the
added Conflicts is confusing for people with both
Actually slightly fiddly to fix because part of this code also needs to
go after another script that's after that question - it'll probably need
to be split into two files.
** Package changed: debian-installer (Ubuntu) = eucalyptus (Ubuntu)
** Changed in: eucalyptus (Ubuntu)
Importance:
On Fri, Oct 09, 2009 at 08:08:30AM -, Achim Bohnet wrote:
You showed us that you have no .bash_profile and .bash_profile, now do
you have a ~/.profile?
If yes: is .bashrc sourced in .profile? if not: add it (see
/etc/skel/.profile how to do it)
if you have no .profile, copy
I can understand why br0 would need to be static rather than dhcp. I
don't understand why the static network configuration needs to go on br0
rather than on eth0, though; this just seems weird, especially with
'bridge_ports eth0'. Can you explain this for the hard of thinking?
--
uec node cd
You already have grub installed in the chroot at this point, as far as I
can see. Why not just call grub in the chroot, rather than relying on
whatever's installed in the host system?
--
VMBuilder doesn't work with grub2
https://bugs.launchpad.net/bugs/410886
You received this bug notification
** Changed in: parted (Ubuntu Karmic)
Assignee: (unassigned) = Colin Watson (cjwatson)
--
[karmic] parted can't create swap partitions in vm images
https://bugs.launchpad.net/bugs/399428
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
lp:~cjwatson/vmbuilder/chroot-grub changes vmbuilder to call grub in the
chroot. There's a certain amount of faff involved to let the chroot see
the disk images so that it can install grub to them, but it's not all
that bad.
--
VMBuilder doesn't work with grub2
I think that's actually a bug. grub and grub2 are meant to conflict.
--
VMBuilder doesn't work with grub2
https://bugs.launchpad.net/bugs/410886
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
--
Ubuntu-server-bugs
This was fixed in r605 and thus in eucalyptus 1.6~bzr854-0ubuntu6,
although we forgot to mention it in the changelog so the bug didn't get
automatically closed.
** Changed in: eucalyptus (Ubuntu)
Status: Fix Committed = Fix Released
--
eucalyptus-cloud should depend on
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Confirmed = Fix Committed
--
euca_find_cluster should probably prefer IPv4 addresses
https://bugs.launchpad.net/bugs/436200
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Is an action in the next release cycle good enough? We need to do
something about this bug for *this* release cycle, surely.
--
mysql-server has been kept back with dist-upgrading
https://bugs.launchpad.net/bugs/413789
You received this bug notification because you are a member of Ubuntu
Server
I think this is now closeable - local node discovery is done, and we've
added a fair amount of debconf configuration. If there turns out to be
more to do on the latter, it will be more effectively tracked in
separate bug reports.
** Changed in: eucalyptus (Ubuntu)
Status: Confirmed = Fix
** Changed in: eucalyptus (Ubuntu)
Status: New = Triaged
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Low
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = Fix Committed
The reason I used a separate configuration file for CC_NAME was that it
was entirely packaging-specific, and it saved any more fiddling around
with a conffile than was absolutely necessary. I still think it's
appropriate for CC_NAME to be there. For all the VNET_* stuff that's
parsed by upstream
How about this patch? It's entirely untested.
** Attachment added: 435130.diff
http://launchpadlibrarian.net/32462153/435130.diff
--
Default MANAGED-NOVLAN network setting not being applied properly
https://bugs.launchpad.net/bugs/435130
You received this bug notification because you are a
Public bug reported:
We should display the admin URL somewhere when booting a UEC cloud host,
in order to reduce the need for documentation-reading to figure out how
to get at the web interface.
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Tags: eucalyptus
Public bug reported:
The first time I tried the UEC node installation (in this testing pass),
it failed to download the preseed file from the cluster because it had
got the IPv6 address and I don't have IPv6 routing set up between my
VMs. I think it would be best if we fixed euca_find_cluster to
Public bug reported:
Registering components with the cloud currently requires --local-sync,
or else you get some ssh host key prompts. We already arrange for the
cloud's ssh key to be allowed to authenticate to itself; we should also
put its own host key in /etc/ssh/known_hosts, to make component
Should we just use VNET_PUBINTERFACE here, at least for now?
--
Autoregister runs euca_conf with localhost but that is refused in 1.6~bzr808
https://bugs.launchpad.net/bugs/434593
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus
I think we can assume that by definition the network interface
configured in netcfg is public-facing; it's used to do things like 'apt-
get update', after all. If there are multiple network interfaces, we can
ask later on which one should be used to communicate with nodes.
We don't tell
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = Fix Committed
--
Eucalyptus, avahi-publish component discovery, and eucalyptus configuration not
functional if front-end machine has more than one interface
https://bugs.launchpad.net/bugs/425933
You received this bug
I'm wondering if the proper solution to this is to remove mysql-dfsg-5.0
from the archive to clue apt into the fact that its binaries should get
a lower score than the binaries from mysql-dfsg-5.1. It's no longer in
unstable ...
There are *lots* of reverse dependencies, though.
--
mysql-server
Michael, is there anything else we can do about this that will convince
apt to do the right thing?
** Changed in: mysql-dfsg-5.1 (Ubuntu Karmic)
Assignee: Canonical Foundations Team (canonical-foundations) = Michael
Vogt (mvo)
--
mysql-server has been kept back with dist-upgrading
** Changed in: netcfg (Ubuntu Karmic)
Status: Invalid = Won't Fix
** Changed in: netcfg (Ubuntu)
Status: Invalid = Triaged
--
eucalyptus node install results in broken /etc/network/interfaces
https://bugs.launchpad.net/bugs/430820
You received this bug notification because you are
It should match euca_conf. For cluster registration that's CC_PORT; for
walrus/sc registration it's apparently hardcoded to 8773.
--
Cloud installer / Cluster install hangs at reboot after install
https://bugs.launchpad.net/bugs/430758
You received this bug notification because you are a member
Doesn't look fixed to me ...
** Changed in: eucalyptus (Ubuntu)
Status: Fix Released = Triaged
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
--
Cloud installer / Cluster
Ideally, I think netcfg should make sure that netcfg/choose_interface is
always set even if there's only one interface. Still, we can work around
this in eucalyptus-udeb.
** Also affects: netcfg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netcfg (Ubuntu)
Importance:
Etienne, can you file a separate bug about setting eth0 to manual, with
more details? Dustin says he didn't have to do that and is routing table
looks OK, so maybe this is a more isolated problem.
--
eucalyptus node install results in broken /etc/network/interfaces
I think having 'start' restart the process if it isn't already providing
the necessary service would be reasonable enough.
I filed a separate bug about how the init scripts work recently, but
even then, presumably you'd still have to restart the frontend to get it
to run an additional service.
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
--
after UEC front-end (cluster) install, key sync stage of registration cannot
proceed without entering a password
https://bugs.launchpad.net/bugs/429087
You received this bug notification because you
** Changed in: eucalyptus (Ubuntu)
Status: New = Fix Committed
--
after UEC front-end (cluster) install, key sync stage of registration cannot
proceed without entering a password
https://bugs.launchpad.net/bugs/429087
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 429086 ***
https://bugs.launchpad.net/bugs/429086
This was also reported as bug 429086, and is now fixed.
** This bug has been marked a duplicate of bug 429086
[karmic UEC] file /usr/share/eucalyptus/antlr.jar belongs to
eucalyptus-cloud and
I think I have everything in place now, but in my testing the cloud
controller was falling over in various ways when I tried to register
components. I'm not at all convinced that that wasn't an artifact of my
test environment, so I would appreciate somebody with a more competent
environment giving
** Changed in: eucalyptus (Ubuntu Karmic)
Milestone: None = ubuntu-9.10-beta
--
Eucalyptus, avahi-publish component discovery, and eucalyptus configuration not
functional if front-end machine has more than one interface
https://bugs.launchpad.net/bugs/425933
You received this bug
Public bug reported:
The eucalyptus-{cloud,walrus,sc} init scripts are very confusing. They
all operate on more or less the one daemon process, copying different
.jar files into place as appropriate. Starting each of the components
involves repeatedly restarting the Java front-end.
It would be a
Soren says that this should be fixed in newer versions in Karmic, at
least for the moment, and indeed adb_ccInstanceType_set_networkIndex is
definitely defined now. Apparently updates to our generated stubs are
still manual, so we need to explicitly notice changes and regenerate the
patch.
**
What if it's already registered to another cloud controller, though?
Would --register-walrus local-ip forcibly re-register with a local
cloud? We wouldn't want that, I think.
We'd want some way to distinguish failed to register because already
registered from failed to register because something
Any thoughts on the network that should be used? Presumably it should be
in RFC1918-space? Do we need to ask the administrator for network
parameters?
--
When installing a node controller, a bridge device should be created
https://bugs.launchpad.net/bugs/424541
You received this bug notification
Based on https://help.ubuntu.com/community/Eucalyptus%2Bbridge I think
I'll assume that DHCP will work. If it won't, somebody should shout to
let me know.
--
When installing a node controller, a bridge device should be created
https://bugs.launchpad.net/bugs/424541
You received this bug
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = Fix Committed
--
When installing a node controller, a bridge device should be created
https://bugs.launchpad.net/bugs/424541
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
This seems to have been fixed a while back; the packaged default for
VNET_BRIDGE is now br0.
** Changed in: eucalyptus (Ubuntu)
Status: New = Fix Released
--
/etc/eucalyptus/eucalyptus.conf default directive VNET_BRIDGE=xenbr0 should
really be VNET_BRIDGE=br0
name from xenbr0 to br0
[ Colin Watson ]
* eucalyptus-cloud Replaces: eucalyptus-javadeps.
[ Soren Hansen ]
* Update WSDL stubs.
-- Soren Hansen so...@ubuntu.com Mon, 07 Sep 2009 15:24:04 +0200
--
/etc/eucalyptus/eucalyptus.conf default directive VNET_BRIDGE=xenbr0 should
really
I'd really appreciate it if somebody could eyeball this branch and let
me know whether it looks sane:
http://bazaar.launchpad.net/~cjwatson/eucalyptus/register-walrus-
sc/revision/539
--
Eucalyptus component registration process is manual
https://bugs.launchpad.net/bugs/425922
You received
Much better, thanks.
--
qemu-img should give reasons for failing
https://bugs.launchpad.net/bugs/418112
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
I've just merged --discover-nodes support. The debconf questions are
among the next couple of things on my list.
--
[FFE] local node discovery, debconf improvements
https://bugs.launchpad.net/bugs/424368
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I think cluster registration is actually already handled (see tools
/eucalyptus-cc.in:register_local_cloud in the Ubuntu branch), but some
more similar work needs to be done on the other components.
--
Eucalyptus component registration process is manual
https://bugs.launchpad.net/bugs/425922
Do you have any idea how we can tell in a script whether the Walrus and
storage controller components are already registered? For the cluster
controller, we check for the existence of /var/lib/eucalyptus/keys
/cluster-pk.pem; but it isn't obvious to me how to do the same for the
Walrus and SC.
--
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: Soren Hansen (soren) = Colin Watson (cjwatson)
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = Fix Committed
--
Temporary file vulnerability in euca_conf
https://bugs.launchpad.net/bugs/424459
You received this bug
** Package changed: netcfg (Ubuntu Karmic) = eucalyptus (Ubuntu Karmic)
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: Canonical Foundations Team (canonical-foundations) = Colin
Watson (cjwatson)
--
When installing a node controller, a bridge device should be created
https
--discover-nodes prototype:
https://code.launchpad.net/~cjwatson/eucalyptus/discover-nodes
--
[FFE] local node discovery, debconf improvements
https://bugs.launchpad.net/bugs/424368
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Wow, yes, excellent catch. udevd.c:worker_new() blocks a load of signals
and nothing puts them back.
Bug tennis :-)
** Package changed: openssh (Ubuntu) = udev (Ubuntu)
** Changed in: udev (Ubuntu)
Milestone: karmic-alpha-5 = karmic-alpha-6
--
sshd zombie processes and strange behavior
601 - 700 of 815 matches
Mail list logo
