Fabian,
The fr_CA locale is pan-Canadian, not Québc-specific. The document
being cited is from the OQLF, a Québec provincial agency. As such, we
would need to confirm using a directive from the federal to be
absolutely sure.
However, it is my understanding that week begins on Monday in the Fren
** Bug watch added: Samba Bugzilla #6682
https://bugzilla.samba.org/show_bug.cgi?id=6682
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=6682
Importance: Unknown
Status: Unknown
--
Bug in NetApp Filer SMB protocol implementation make CIFS share unmountable
Thanks Leann. The patch works, to a certain extent. We can now mount a
share from the NetApp Filer, where we could not before. However, we had
to use option "sec=krb5" with mount.cifs, where "sec=krb5i" (Kerberos
authentication with packet signing) would be preferred and works with
other kerberi
Leann, would it be too much to ask for a 32 bits build? Thanks! :)
--
Bug in NetApp Filer SMB protocol implementation make CIFS share unmountable
from Ubuntu
https://bugs.launchpad.net/bugs/479272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Understood. A kernel with the above patch applied would, at least,
allow us to confirm that the bug is really where we think it is. We can
then report our finding upstream to Samba, and collaborate to test a
permanent solution.
Thanks a lot!
--
Bug in NetApp Filer SMB protocol implementation m
Public bug reported:
Reportedly, a bug in NetApp Filer SMB protocol implementation make it
impossible to mount a CIFS share on such a server from Ubuntu using
mount.cifs and the cifs kernel module when using Kerberos
authentication. The problem is being discussed in upstream Samba bug
tracker at:
Dustin, thanks a lot for that fix! This will save tons of grieves to
lots of people down the road. I know *I* lost a couple of hours before
figuring out that VT extensions where disabled in the BIOS ... :D
--
kvm disabled in bios (was: Unable to start EUC instances - no supported
architecture
Sounds good now. I have no idea where the magic operate, as
/etc/network/if-up.d/ntpdate do not check the desktop environment
setting, but manually-set time persist across reboot now. Thanks, I
guess this can be closed.
--
Time is being adjusted by ntpdate even if you choose to manage time manu
Sorry guys, this was a user error. I was using a range in
VNET_PUBLICIPS that was not in use on the machine. Sorry for the noise!
** Changed in: eucalyptus (Ubuntu)
Status: New => Invalid
--
The text debconf template eucalyptus/publicips is wrong
https://bugs.launchpad.net/bugs/459204
Y
Public bug reported:
In karmic, eucalyptus 1.6~bzr931-0ubuntu7, the text of the
eucalyptus/publicips debconf template is wrong. It says the following:
Please specify one or more ranges of IP addresses, e.g.:
192.168.1.100-192.168.1.199
or
192.168.2.50-192.168.2.99 192.168.2.150-192.168.2.199
Public bug reported:
In karmic eucalyptus 1.6~bzr931-0ubuntu7, the output of "euca_conf
--help" is wrong about the argument to remove a node from the cluster.
It states the argument is --delete-nodes, while it should really be
--deregister-nodes.
** Affects: eucalyptus (Ubuntu)
Importance: L
Public bug reported:
The configuration file /etc/eucalyptus/eucalyptus.conf, used by all
Eucalyptus services (-cloud, -cc, -nc, etc) is very confusing and
practically undocumented. The inline comments are helpful, but they do
not provide enough context for the administrator to decide which
config
Public bug reported:
The euca_conf script, shipped in eucalyptus-common, is missing command-
line completion. This would be nice to have at some point.
** Affects: eucalyptus (Ubuntu)
Importance: Wishlist
Status: New
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided => W
uld get somewhere on Eucalyptus, that would be great.
--
Etienne Goyer
Technical Account Manager - Canonical Ltd
Ubuntu Certified Instructor
~= Ubuntu: Linux for Human Beings =~
--
Cloud Web interface should allow overcommit on CPU
https://bugs.launchpad.net/bugs/457864
You received this bug notifica
Public bug reported:
Binary package hint: debian-installer
Using karmic server daily ISO of 19-10-2009, when installing an
Eucalyptus cluster controller on a machine that have multiple network
interfaces, the dialog that prompt for which interface to use to
communicate with nodes ("Network interf
Public bug reported:
Binary package hint: debian-installer
In karmic, the d-i Eucalyptus cluster controller target bring in postfix
as a dependency of eucalyptus-cloud. The Eucalyptus CLC needs a local
SMTP server to send emails for user management (requesting account,
approving account, etc).
Neil Levine wrote:
> In fact, it should say "Ubuntu Enterprise Cloud, powered by Eucalyptus(TM)".
T,FTFY
--
Etienne Goyer
Technical Account Manager - Canonical Ltd
Ubuntu Certified Instructor
~= Ubuntu: Linux for Human Beings =~
--
UEC management interface still has Eucaly
Public bug reported:
The copyright file of eucalyptus in karmic is incorrect. It states that
Eucalyptus is under a BSD-derived license, when it is really is under
GPLv3 at this point. Please see http://www.eucalyptus.com/licenses/,
and check the header of various source files for confirmation.
Joseph Salisbury wrote:
> Hmm. I wonder if this could be related to the bios. I'll check it to
> ensure the correct settings are enabled for KVM. Could an error like
> this occur if the bios was not setup correctly?
Yes, indeed.
--
Unable to start EUC instances - no supported architecture for
Same as GriFF3n above. I do not have a 85-ifupdown.rules in either
/etc/udev/rules.d/ or /lib/udev/rules.d/.
--
ifdown: failed to open statefile /var/run/network/ifstate:
https://bugs.launchpad.net/bugs/377432
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
On 2008-08-06, Steve had this tidbit of wisdom:
> If you are only using libnss-ldap without nscd, there is nowhere in the
> model for this reachability information to be stored. If you use nscd,
> results will be cached in the event the server is down.
Well, yes and no. Enumeration of NSS databas
sub.mesa: this is a different issue. We did not had root file system
over iSCSI support in hardy at all (it is just shaping up for karmic).
--
iSCSI install fails under hardy
https://bugs.launchpad.net/bugs/236640
You received this bug notification because you are a member of Ubuntu
Bugs, which
Dustin Kirkland wrote:
> Note that I had to modprobe acpiphp. Perhaps we should consider loading
> this module in init or in modules.conf.
I have reported this issue in bug #364916.
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You r
After investigation (thanks Marc!), it seems like Eucalyptus add a
trailing newline to the output of http://169.254.169.254/2008-02-01
/meta-data/public-keys/. That confuse ec2-fetch-credentials; adding a
check for empty newline in get_ssh_keys() actually fix the bug, such as:
def get_ssh_keys():
Public bug reported:
Binary package hint: ec2-init
It seems like the command ec2-fetch-credentials do not work when being
run in a jaunty instance (ec-init version 0.3.3ubuntu12), itself running
on eucalyptus 1.5~bzr266-0ubuntu2 on jaunty. I believe, although I am
not sure, that the output of th
Not Dan, but here's my take anyway.
I would say it is fairly critical. The EBS functionality (on which the
block device attach/detach functionality depends) is a pretty important
feature. Without, data persistence is not obvious. For example, you
would run MySQL in the cloud by keeping table da
Do not forget to create /var/run/eucalyptus/net/ too (per bug #365349),
otherwise only SYSTEM mode will work.
--
/var/run/eucalyptus is not being set with correct permissions on machine reboot
https://bugs.launchpad.net/bugs/431114
You received this bug notification because you are a member of Ub
Unfortunately, I had to revert back to 1.5 for a specific project, and I
do not have the hardware to run two clusters in parallel (a stable one
on jaunty/1.5, and one for testing on karmic/1.6). I will not be able
to test any earlier than late next week. Sorry! :(
--
Instance fail to run
https
I have been told by a colleague that it render correctly in karmic,
which mean it must have been fixed. See the attached screenshot for how
it render on jaunty.
Also, I forgot to mention that it also print with the lighter lines in
the shading area, which mean it is not a problem specific to scre
** Attachment added: "Screenshot.png"
http://launchpadlibrarian.net/31931904/Screenshot.png
--
evince do not render smooth shading properly
https://bugs.launchpad.net/bugs/431088
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
** Attachment added: "flyer_en.pdf"
http://launchpadlibrarian.net/31931818/flyer_en.pdf
--
evince do not render smooth shading properly
https://bugs.launchpad.net/bugs/431088
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
Public bug reported:
Binary package hint: evince
Using evince 2.26.1-0ubuntu1 on 9.04 (jaunty), the attached file
(produced by Inkscape) do not render properly. You can notice that the
blue smooth shading (the kind of frame around the flyer content) renders
with vertical line of lighter shade.
Colin, for me on jaunty, the following /etc/network/interfaces result in
a system with broken network (ie, cannot ping or connect to anything):
---
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
ifa
You will also want to make eth0 manual ("iface eth0 inet manual"),
otherwise both the bridge and eth0 will get an IP, making the routing
table funny.
--
eucalyptus node install results in broken /etc/network/interfaces
https://bugs.launchpad.net/bugs/430820
You received this bug notification beca
Trevor,
Can you have a look at bug #430093, and see if it is the same bug that
you get? If yes, could you add a comment with relevant details (such as
the above log snippet).
Thanks!
--
Eucalyptus cloud controller stops working suddenly
https://bugs.launchpad.net/bugs/428010
You received this
Public bug reported:
On karmic, after upgrading Eucalyptus from 1.6~bzr672-0ubuntu4 to
1.6~bzr746-0ubuntu1, trying to run an instance fail with the following
error:
cloudmas...@uec-frontend:~$ euca-run-instances -t c1.medium -k warthogs-key
emi-073A1120
Warning: failed to parse error message fro
Got the same problem upgrading a Eucalyptus frontend (running -cloud,
-cc, -walrus and -sc). However, we cannot accept the package
maintainer's version, as it will overwrite the NODES value in the
configuration file, which would make the frontend consider there is no
node controller. People runni
The problem is indeed with eucalyptus. There is now a check in the init
script that will make it fail if the EUCALYPTUS value of the
configuration file is "not_configured". The config that shipped in the
last version indeed was. Somehow, the config file did not got upgraded
to the new version, d
Public bug reported:
On karmic, when upgrading Eucalyptus from 1.6~bzr672-0ubuntu4 to
1.6~bzr746-0ubuntu1, package upgrade will fail following. It seems like
the problem is really with insserv and unrelated to Eucalyptus
specifically, but I am not entirely sure.
Setting up eucalyptus-nc (1.6~bz
I had the same problem when testing earlier today. I *believe*
(although I am not sure) that happen when you have not registered the
clc on the walrus machine. Are you running walrus on a different
machine than the cloud controller?
--
Eucalyptus hangs & euca-upload-bundle doesn't return
https:
*** This bug is a duplicate of bug 423465 ***
https://bugs.launchpad.net/bugs/423465
** This bug has been marked a duplicate of bug 423465
euca.p12 owned by root
--
Registering Walrus fail
https://bugs.launchpad.net/bugs/429719
You received this bug notification because you are a member o
Public bug reported:
On karmic running Eucalyptus 1.6~bzr672-0ubuntu3, instances fail to
start. I have not been able to track down the cause. I systematically
get the following:
cloudmas...@uec-frontend:~$ euca-run-instances -t c1.medium -k warthogs-key
emi-073A1120
RESERVATION r-5254095A
** Attachment added: "nc.log"
http://launchpadlibrarian.net/31806315/nc.log
--
Instance fail to run
https://bugs.launchpad.net/bugs/429754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
Public bug reported:
On karmic running Eucalyptus 1.6~bzr672-0ubuntu3, after installing a
node controller and registeringit successfully, it is impossible to run
an instance. On the frontend:
euca-describe-availability-zones verbose
AVAILABILITYZONEwarthogs10.153.108.210
AVAILABI
Public bug reported:
On karmic using Eucalyptus 1.6~bzr672-0ubuntu3, when you use "euca_conf
--get-credentials cred.zip" to retrieve the certificate bundle on the
frontend, the eucarc file contains the following declaration:
export S3_URL=http://127.0.0.1:8773/services/Walrus
export EC2_URL=http:
The following workaround allows you to proceed with walrus registration:
sudo chown eucalyptus:eucalyptus /var/lib/eucalyptus/keys/euca.p12
--
Registering Walrus fail
https://bugs.launchpad.net/bugs/429719
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
The in question is already there, and writable only by root, hence why
scp fail:
cloudmas...@uec-frontend:~$ sudo ls -l /var/lib/eucalyptus/keys//euca.p12
-rw-r--r-- 1 root root 21546 2009-09-14 18:06 /var/lib/eucalyptus/keys//euca.p12
--
Registering Walrus fail
https://bugs.launchpad.net/bugs/4
Public bug reported:
On a brand new installation of Eucalyptus 1.6~bzr672-0ubuntu3 on karmic,
after manually copying ~eucalyptus/.ssh/id_rsa.pub to
~eucalyptus/.ssh/authorized_keys and successfully registering the
cluster, registration of the walrus component fail with the following
error:
cloud
Quick workaround on the frontend:
sudo cp ~eucalyptus/.ssh/id_rsa.pub ~eucalyptus/.ssh/authorized_keys
--
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 b
Ok, I did the registration already, and it appears to have succeeded. I
guess this bug should be closed as Invalid for now, i will try to figure
out what happened with the registration.
--
Cannot upload bundle to Walrus
https://bugs.launchpad.net/bugs/429590
You received this bug notification be
Public bug reported:
On karmic with Eucalyptus 1.6~bzr672-0ubuntu3, if you download the
certificate bundle before you register a Walrus server, the eucarc file
in the bundle declare the following variable:
export S3_URL=http://BukkitInternal:8773/services/Walrus/
BukkitInternal is not an actual
Public bug reported:
On karmic using Eucalyptus 1.6~bzr672-0ubuntu3, when trying to
deregister a Walrus server on the command-line, euca_conf reports that
the Walrus server is successfully deregistered, but some verbiage on the
command appears to indicate it was not. See below:
cloudmas...@uec-
Public bug reported:
On karmic using Eucalyptus 1.6~bzr672-0ubuntu3, when running the -walrus
on the same machine as -cloud and -cc, I get the following error trying
to upload a bundle from a client:
etie...@curst:~/AMI/euca-ubuntu-9.04-x86_64$ ec2-upload-bundle -b jaunty-kernel
-m bundles/vmlin
Public bug reported:
In eucalyptus 1.6~bzr672-0ubuntu2, it appears that the file
/usr/share/eucalyptus/antlr.jar belongs to both eucalyptus-cloud and
eucalyptus-java-common, complicating package upgrade. Witness:
cloudmas...@uec-frontend:~/deb$ sudo dpkg -i
eucalyptus-java-common_1.6~bzr672-0ub
Got the same problem on an HP Proliant DL380 G5, which had been
certified for 8.04.
cloudmas...@eucalyptus-walrus:~$ lspci | grep VGA
01:03.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)
--
Boot fails with Out of Range Pointer error
https://bugs.launchpad.net/bugs/424503
You r
I confirm I had exactly the same problem happen to me last week.
When looking at /var/log/eucalyptus/cloud-error.log, there was some
verbiage about a corrupted index or somesuch. Do you see something
similar?
Also, is it possible that you started the eucalyptus-cloud service from
within an SSH s
I see the same symptoms here. eucalyptus-cc has been running for a bit
over a month now. That is also on jaunty amd64, eucalyptus-cc
1.5~bzr266-0ubuntu2.
cloudmas...@eucalyptus-frontend:~$ ps up 2642
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
110 2642 2.7 20.
Tested 2.6.24.60 from hardy-proposed, and it work as expected in any
application I use (VLC, Cheese, arecord, etc). Camera, microphone and
LED are all functional. Thanks a lot!
--
Built-in microphone on Lenovo USB webcam doesn't work when hald is running
https://bugs.launchpad.net/bugs/310760
Y
Public bug reported:
Binary package hint: eucalyptus-nc
This is a wishlist item.
As it can be hard to track problems running instances on a node
controller caused by the node controller not supporting HVM, it would be
good if the package installer would warn of the situation. For example,
we co
*** This bug is a duplicate of bug 425915 ***
https://bugs.launchpad.net/bugs/425915
** This bug has been marked a duplicate of bug 425915
UEC installer does not set up a bridge device by default for Eucalyptus
nodes (NCs)
--
When installing a node controller, a bridge device should be c
I already reported that issue as bug #424541.
--
UEC installer does not set up a bridge device by default for Eucalyptus nodes
(NCs)
https://bugs.launchpad.net/bugs/425915
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I have not yet verified that this is still a bug in karmic, but it
should be fixed if it is.
--
Any network mode beside SYSTEM fail because /var/run/eucalyptus/net do not exist
https://bugs.launchpad.net/bugs/365349
You received this bug notification because you are a member of Ubuntu
Bugs, which
Still a problem in Karmic.
--
eucalyptus-nc should depend on ssh
https://bugs.launchpad.net/bugs/411656
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
This could be fixed relatively easily by calling euca_conf in the
postinst script of either eucalyptus-common or -cc, such as:
euca_conf --dhcpd /usr/sbin/dhcpd3
euca_conf --dhcp_user dhcpd
--
In /etc/eucalyptus/eucalyptus.conf, VNET_DHCPDAEMON and VNET_DHCPUSER should be
set to value a
This bug have been fixed in karmic. It should be SRUed for jaunty, or
marked WONTFIX, as appropriate.
--
eucalyptus-nc service fail to start at boot, cannot connect to libvirtd
https://bugs.launchpad.net/bugs/364723
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Fixing this would assume, of coure, that we also fix #364724.
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: netcfg
When installing a Eucalyptus node controller using the karmic server CD
with the cloud seed, an Ethernet bridge device should be created
automatically. Having a bridge device is a requirement of running a
Eucalyptus node controller; you systematic
Public bug reported:
Sample output of euca_conf ran on a cluster controller:
--
ubu...@t61p:~$ sudo euca_conf --register-nodes 192.168.144.65
INFO: We expect all nodes to have eucalyptus insta
Public bug reported:
When running the restart target of eucalyptus-nc 1.6~bzr645-0ubuntu1 in
karmic, the restart fail because it cannot find the avahi-publish
executable. The package should then depend on avahi-utils, and maybe
check for the presence of the avahi-publish executable in the init
sc
Chris,
Do you have a way to trigger this bug? I am interested in reproducing
it for my own edification.
--
ec2-describe-instances sometimes shows the wrong IP
https://bugs.launchpad.net/bugs/423308
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
The recipe to create an AMI at
https://help.ubuntu.com/community/Eucalyptus would also need to be
modified. As it stands, it would result in an AMI that cannot make use
of EBS.
--
When running Ubuntu as an Eucalyptus VM instance, module acpiphp is not
available to be loaded, complicating the us
Scott Moser wrote:
> The other solution would be to get acpiphp.ko into the initrd that the user is
> told to use. That can be accomplished by adding it to
> /etc/initramfs-tools/modules and running update-initramfs prior to
> 'ec2-bundle-image' and 'ec2-upload-bundle'.
But then, we would also n
AceLan,
Sorry for taking so long to get back to you. I have tested the latest
kernel found in the location provided above, and everything works
(camera, microphone and LED).
Thanks a whole bunch!
--
Built-in microphone on Lenovo USB webcam doesn't work when hald is running
https://bugs.launchp
Public bug reported:
Binary package hint: eucalyptus-nc
When registering a new node to an Eucalyptus cluster (euca_conf -addnode
), the certificate bundle is copied from the
cluster controller to the new node controller over ssh. As such, the
package eucalyptus-nc should depend on an SSH server.
Nilesh, as of your second comment, you need to change the value of
VNET_BRIDGE in /etc/eucalyptus/eucalyptus.conf on the node controllers.
--
eucalyptus-nc service fail to start at boot, cannot connect to libvirtd
https://bugs.launchpad.net/bugs/364723
You received this bug notification because y
That is what I would guessed too, and I think it would be a good
default behavior. I know some people have very strong opinion on this
issue. Should it be discussed at a Server team meeting, or even as a
session in the next UDS? That way, we could get opinion from all
stakeholders and formulate
I tested in Jaunty. The problem with the microphone is resolved indeed;
the mike continue to work after having used the camera. However, the
camera in general is not working so well; video is extremely choppy in
Cheese, and it hard freeze the machine when trying to access the camera
using the V4L
Keng-Yü,
It works! I have just tested in hardy, and both the camera and
microphone works at the same, without using the HAL policy suggested by
Leann. Basically, with the kernel you built, the camera and microphone
works in any application (arecord, VLC, etc), and keep on working across
unplug/r
The latest daily hardy server CD ISO (20090709) works just fine indeed.
When provided with the iscsi=true boot option, it will prompt for the
iSCSI target to use, the iSCSI target will show up as a block device in
the partitionner dialog, and you can use it for non-root file systems
just fine. I u
AceLan,
I am using 2.6.28-13-generic, the latest on jaunty, on my personal
laptop. But i fyou want me to test one for hardy, I canuse whichever
you want.
Thanks a lot!
--
Built-in microphone on Lenovo USB webcam doesn't work when hald is running
https://bugs.launchpad.net/bugs/310760
You recei
Colin, as the bug is in the installer part of the package, I would need
an ISO to test. Or can I test using the netboot installer?
--
iSCSI install fails under hardy
https://bugs.launchpad.net/bugs/236640
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I do not have the problem Kevin reports above; iscsi=true works just
fine for me. I tested using the karmic server CD image dated
08-Jul-2009 10:32 from the same location he does.
I am pleased to report the iSCSI installer support works just fine now for me.
The iSCSI dialog come up fine, the
Leann, I just tested with 2.6.31-2.16. I used the -generic flavour, as
there was no -server. I am not getting the oops anymore when running
iscsi_discovery. I guess that's good news!
--
[karmic] Kernel oops when running iscsi_discovery
https://bugs.launchpad.net/bugs/395323
You received this b
The kernel oops have been reported as bug #395323.
The target block device not being made available right away is not a
bug, it is the expected behavior. Sorry for the noise.
--
iSCSI install fails under hardy
https://bugs.launchpad.net/bugs/236640
You received this bug notification because you
** Attachment added: "karmic-dmesg.txt"
http://launchpadlibrarian.net/28671144/karmic-dmesg.txt
--
[karmic] Kernel oops when running iscsi_discovery
https://bugs.launchpad.net/bugs/395323
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "karmic-iscsi_discovery-output.txt"
http://launchpadlibrarian.net/28671146/karmic-iscsi_discovery-output.txt
--
[karmic] Kernel oops when running iscsi_discovery
https://bugs.launchpad.net/bugs/395323
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
On karmic, the kernel oops when running iscsi_discovery from the open-
iscsi package.
I do not get the oops on jaunty.
The iscsi_discovery command line is:
sudo iscsi_discovery 192.168.4.13
Where 192.168.4.113 is a Ubuntu machine running iscsitarget.
Attached are the
Is still still an issue an issue on hardy, which ship with open-iscsi
2.0.865? If not, then I guess we should close this bug as invalid or
wontfix.
--
Open solaris iscsi target causes panic in open-iscsi
https://bugs.launchpad.net/bugs/159682
You received this bug notification because you are a
Steve, I built open-iscsi with the above debdiff, and iscsi_discovery
does work just like the unpatched version. I found two other bugs with
it (the block device is not being made available right away, and it
cause a kernel oops in certain circumstance), but I will be reporting
these separately.
Thierry Carrez wrote:
> Not exactly, what I'm saying is that on *every* network that has a
> correct DNS setup, this change will result in a small performance hit
> and/or useless network noise. This is not a question of "large company
> networking". Everyone can setup dnsmasq for local name resolu
As I explained a couple months earlier (see comment 2), even if the path
to iscsi-iname is fixed, it still fail in the end. The installer goes
on just fine, but if you choose to configure a file system residing on
an iSCSI target to be mounted at boot time (not as the root file system,
just about
Attached is /var/log/syslog from the daily karmic server ISO (June
29th).
However, it does not include the fix Steve uploaded in comment 25 (open-
iscsi 2.0.865-1ubuntu4). As it is an installer bug, I guess it will ned
to find it's way into the daily build before I can test.
** Attachment added:
Quick test lead me to believe that open-iscsi 2.0.865-1ubuntu3.1 from
hardy-proposed work as explained by Steve. That is, the block device
appear after the bonded Ethernet is brought up. It is too late for the
file system on the iSCSI target to be mounted from /etc/fstab, but at
least we do not h
Chris Puttick wrote:
> Consider me confused on the basis of my earlier comment showing how to
> configure Hardy so that iscsi volume mounts works consistently. It
> ain't broke, why fix it?
That is because you are not accessing the iSCSI target through a bonded
Ethernet interface. With plain Ethe
Public bug reported:
On Ubuntu 8.04 hardy, kernel module "bonding" have to be manually loaded
(or added to /etc/modules) for bonded Ethernet device to come up. This
is not the case on 9.04 jaunty, where module "bonding" is loaded
automatically when the bonded interface is brought up (it is being
I also experience the same behavior using nautilus 2.22.5.1-0ubuntu2
from hardy-proposed.
--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
The proposed fix was pulled from hardy-proposed, but Steve made it
available again on his PPA at http://ppa.launchpad.net/vorlon/ppa/ubuntu
for further confirmation of the regression.
Using gvfs and gvfs-backends 0.2.5-0ubuntu8~ppa1 from there, along with
nautilus 2.22.5.1-0ubuntu1 from hardy-upda
I always test using arecord, such as:
arecord -D hw:1,0 -d 3 -f cd -t wav test.wav
Thanks, AceLan!
--
Built-in microphone on Lenovo USB webcam doesn't work when hald is running
https://bugs.launchpad.net/bugs/310760
You received this bug notification because you are a member of Ubuntu
Bugs
There is no daily of the server flavour on http://cdimage.ubuntu.com,
but here is /var/log/syslog from Jaunty server ISO, when launched with
"iscsi=true".
Steve, contrary to what we discussed earlier today, I do think finally it is
the same error we get on jaunty and hardy after all. It does ap
AceLan, it is probably easier if you have your own cam, but if bad come
to worse, just let me know and I will get you access to a machine that
have one plugged in.
Thanks a lot for looking into that!
--
Built-in microphone on Lenovo USB webcam doesn't work when hald is running
https://bugs.launc
201 - 300 of 545 matches
Mail list logo
