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 notificati
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 no
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 thi
us: Confirmed => 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 t
** 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.
--
Ubun
** 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: o
** 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 ub
** 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 becau
** 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: 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
** 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: o
** 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
https://bugzilla.mindrot.org/show_bug.cgi?id=1533
** 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 => Debia
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 output
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 you
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 subs
*** 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
lyptus-cloud
options so 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
advertiseme
lyptus-cloud
options so 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
advertiseme
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 (
** 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 "Installati
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 g
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: Undec
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 /etc
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 inst
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
https://bugs.launchpad.net/bugs/410
** 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 su
I'm going to backport the parted change; sorry for the delay. Does the
vm-builder task need to stay open, in light of this?
--
[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
Ser
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 be
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 mail-transport-age
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
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 co
** 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: Triag
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 R
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 T
** 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 eucalyptu
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
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
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 eucalyptu
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
Public bug reported:
euca_conf --discover-nodes prompts for manual acceptance of node host
keys even when they were installed by the UEC installer. We probably
ought to use 'ssh -oStrictHostKeyChecking=no' in the --discover-nodes
case.
(I don't think we should turn off host key checking in the ge
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 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
** 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 notificati
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 avahi-publ
** 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 ar
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
https:/
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 h
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)
--
C
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 o
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. The
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
https://bugs.launchpad.net/bugs
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: Und
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.
** Chan
** 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 notificati
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
*** 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 eucalyptus-j
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
** 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
** 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
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 th
name from xenbr0 to br0
[ Colin Watson ]
* eucalyptus-cloud Replaces: eucalyptus-javadeps.
[ Soren Hansen ]
* Update WSDL stubs.
-- Soren Hansen Mon, 07 Sep 2009 15:24:04 +0200
--
/etc/eucalyptus/eucalyptus.conf default directive VNET_BRIDGE="xenbr0" should
really be VNET_B
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"
https://bugs.launchpad
** 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 t
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 notificat
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
What if it's already registered to another cloud controller, though?
Would --register-walrus 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 went w
** 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 th
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.
--
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
You
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 s
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
Ubuntu-server-bugs@lists.ubunt
** 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
--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 eucalyptu
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 a
If your keys are being blacklisted, then, well ... they may appear to be
working just fine, but everyone else on the planet can get the
corresponding private keys with only a little bit of effort! You really
do need to regenerate those keys. Any release of Ubuntu that's still
within its support lif
Oh, I'll also update the code in hw-detect to use block-attr rather than
vol_id, as required in karmic.
** Changed in: hw-detect (Ubuntu Hardy)
Milestone: ubuntu-8.04.3 => ubuntu-8.04.4
** Changed in: mountmedia (Ubuntu Hardy)
Milestone: ubuntu-8.04.3 => ubuntu-8.04.4
--
[Feature Reques
Thanks, looks good now. The only change I'm making is that \L in a sed
replacement expression is a GNU sed-ism, and not supportd by busybox
sed, so won't work in the installer; I'm using tr 'A-Z' 'a-z' instead.
--
[Feature Request] Add support for Dell Driver Injection Disk
https://bugs.launchpad
Might any of you have restarted sshd from within a su session? I don't
have definite proof that it's related, but I note that the quoted
blocked signal mask corresponds exactly to those signals that su blocks.
I wonder if it's due to some PAM session module ...
--
sshd zombie processes and strang
** Changed in: lsb (Ubuntu)
Assignee: Colin Watson (cjwatson) => Michael Vogt (mvo)
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix
Feel free to edit; I'm not going to waste time fine-tuning tags :-)
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in ubuntu.
--
Ubuntu-server-
I figured out what's really going on here - the debconf GNOME frontend
calls lsb_release! No wonder we've been getting so many duplicates.
** Changed in: lsb (Ubuntu)
Importance: Wishlist => High
** Changed in: lsb (Ubuntu)
Assignee: (unassigned) => Colin
Moving this over to partman-iscsi, where I think this probably belongs
now that that exists in Karmic.
** Package changed: open-iscsi (Ubuntu) => partman-iscsi (Ubuntu)
** Changed in: partman-iscsi (Ubuntu)
Importance: Undecided => Medium
** Changed in: partman-iscsi (Ubuntu)
Status: N
(I think the changes I made cover all of malaiwah's notes, too.)
--
iSCSI support (modules and configuration) missing from initramfs
https://bugs.launchpad.net/bugs/269492
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-iscsi in ubunt
/etc/iscsi/iscsi.initramfs is now automatically created by the installer
in Karmic if necessary. See bug 237460 for more details.
** Changed in: open-iscsi (Ubuntu)
Status: New => Fix Released
--
iSCSI support (modules and configuration) missing from initramfs
https://bugs.launchpad.net/b
Blueprint changed by Colin Watson:
Whiteboard changed:
2009-01-21 cjwatson: ready for review
+ 2009-08-11 cjwatson: Closing this out as the bulk of the work was completed
for 9.04, and remaining work (e.g. online help) was moved to other
specifications and bugs.
--
Requirements of Ubuntu
So this set of patches isn't ideal in some ways; in particular it
configures /etc/network/interfaces statically, which has the set of
problems I described in comment 6. However, I think it will at least
make things basically work and people can always edit
/etc/network/interfaces by hand if need be
** Also affects: partman-iscsi (Ubuntu)
Importance: Undecided
Status: New
--
Root on iscsi is not supported
https://bugs.launchpad.net/bugs/237460
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-iscsi in ubuntu.
--
Ubuntu-
** Changed in: open-iscsi (Ubuntu)
Status: Fix Released => Triaged
** Changed in: open-iscsi (Ubuntu)
Milestone: jaunty-updates => None
** Changed in: open-iscsi (Ubuntu)
Status: Triaged => Fix Released
** Changed in: open-iscsi (Ubuntu)
Assignee: (unassigned)
** Also affects: openssh (Ubuntu Karmic)
Importance: Low
Status: Confirmed
** Changed in: openssh (Ubuntu Karmic)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
force-command unable to pass arguments along to internal-sftp
https://bugs.launchpad.net/bugs/362511
You recei
This is not fixed; please don't close it. It happens that the hardcoded
location is currently sane, but it's still hardcoded.
See comment #10, where I wrote exactly the same thing. I'm confused
about why I need to restate myself ...
Loye: A hardlink is not possible since /usr/bin/X11 is a symlink
On my system (this is by no means necessarily complete):
./postfix.config:27:my $distribution = lc(`lsb_release -is 2>/dev/null`);
./samba.postinst:125: && [ "`lsb_release -s -i`" = "Ubuntu" ]
samba depends on lsb-base so it's probably OK. postfix has no way of
doing so here - the only way t
** Package changed: openssh (Ubuntu) => sqlalchemy (Ubuntu)
--
exception from sqlalchemy
https://bugs.launchpad.net/bugs/396202
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-
On Thu, Jul 16, 2009 at 01:52:43AM -, Kevin Otte wrote:
> What needs to be done to make the open-iscsi-udeb load earlier in the
> install sequence so its block devices are available to disk-detect?
disk-detect actually loads open-iscsi-udeb itself, so it probably isn't
that simple ...
> As fo
I've uploaded a fix for lvm2. I don't think initramfs-tools itself
requires any changes, so I'm marking that task Invalid.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
--
initramfs-tools lvm2-hookscript won't include lvm.conf and claim devices it
shouldn't
https://bugs
Oh, you may find this thread useful:
http://lists.mindrot.org/pipermail/openssh-unix-
dev/2009-July/027726.html
Short version: neither Red Hat's security team nor the OpenSSH
developers are aware of anything concrete as yet, and neither is in
possession of any non-public information on the subj
To my knowledge we don't know anything much about the alleged problem
other than rumours, so it's impossible to say as yet whether it's
resolved. We'll respond quickly to any actual information.
--
Is there a security ssh issue in ubuntu?
https://bugs.launchpad.net/bugs/397474
You received this b
(err, yes, obviously that approach only works with netboot not CD)
--
iSCSI install fails under hardy
https://bugs.launchpad.net/bugs/236640
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-iscsi in ubuntu.
--
Ubuntu-server-bugs mail
open-iscsi-udeb isn't in the installer initrd, but instead is retrieved
from the archive at run-time; so booting the installer with apt-
setup/proposed=true (once this has built and published) should be
sufficient.
--
iSCSI install fails under hardy
https://bugs.launchpad.net/bugs/236640
You rece
Accepted into hardy-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
iSCSI in
601 - 700 of 821 matches
Mail list logo
