[Bug 1173952] Re: Suspend and hibernate not working in 13.04/13.10 with alx module
Id did not happen with 13.04, but now after automated update to 14.04 LTS. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1173952 Title: Suspend and hibernate not working in 13.04/13.10 with alx module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173952/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1028470] Re: apache2+ssl hangs on high load
The issue is in part kernel related this commit (introduced in 3.2.9) http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=28d82dc1c4edbc352129f97f4ca22624d1fe61de introduced a epoll path limit of 1000 (1000 process listening on the same socket). This commit (3.2.17) http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=93dc6107a76daed81c07f50215fa6ae77691634f restore the old behavior for non nested epoll path (so you can use unlimited apache process) Apache shouldn't hang but updating your kernel will solve the issue. I've opened an apache ticket (https://issues.apache.org/bugzilla/show_bug.cgi?id=54502) ** Bug watch added: Apache Software Foundation Bugzilla #54502 http://issues.apache.org/bugzilla/show_bug.cgi?id=54502 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1028470 Title: apache2+ssl hangs on high load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1028470/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 56679] Re: provide a method to use a specified MAC-address as the installation device
** Changed in: netcfg (Ubuntu Lucid) Milestone: None => ubuntu-10.04.3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/56679 Title: provide a method to use a specified MAC-address as the installation device To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox-satellite/+bug/56679/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 628145] Re: Eucalyptus does not understand IPv6
** Tags added: ipv6 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/628145 Title: Eucalyptus does not understand IPv6 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 735369] [NEW] Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid
Public bug reported: Binary package hint: bacula-console-qt On lucid, in the Version Browser of bat, it is impossible to check the latest version of a file. This is described in the following upstream bug report: http://bugs.bacula.org/view.php?id=1550 (login using anonymous/anonymous) For convenience, here is the verbatim of the bug description: -- I often restore a single file, so I use Version Browser. 1) I browse for the file and when clicking on it, I see many different versions of it. 2) When I try to mark the file (tick the checkbox), it cannot be done 3) When I try to mark the most recent version of the file in 'Versions of File', it cannot be done 4) When I try to mark any other version of the file, it works OK 5) When there's another version of the file available (after the next backup), the version which couldn't be marked, can now be marked and the most recent can not It seems to be so for every job and every file within a job. I turned on all the debugging options of Bat, but there's nothing said when marking (or trying to) files/versions. - Response from the lead developer of Bacula: - I am unable to reproduce this. It works fine with my version of bat. You are using a bat that was most likely compiled with Qt 4.6.2, and bat is known not to work with all versions of Qt because they are, unfortunately, not compatible. You must use a bat compiled with Qt 4.3.4. All the project binaries are compiled with Qt 4.3.4 using the released depkgs-qt code. - Lucid indeed ship with Qt 4.6.2. I can confirm that bat does not show this problem on maverick, which ship Qt 4.7.0. To confirm the problem is related to the version of Qt being used, I backported bacula-console- qt (5.0.2) from maverick to lucid. The resulting binary showed the same bug as the bacula-console-qt package from lucid. ** Affects: bacula Importance: Undecided Status: New ** Affects: bacula (Ubuntu) Importance: Undecided Status: New ** Also affects: bacula Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. https://bugs.launchpad.net/bugs/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 615810] Re: nagios3-common and nagios3-core : grep: /etc/nagios3/cgi.cfg: No such file or directory
The error seems to be cosmetic, as the service would still start (I have not checked in depth, though). Still, the fix is trivial and really ought to be SRU'ed at some point, IMHO. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in ubuntu. https://bugs.launchpad.net/bugs/615810 Title: nagios3-common and nagios3-core : grep: /etc/nagios3/cgi.cfg: No such file or directory -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 721514] [NEW] Samba should be more selective when importing accounts
Public bug reported:
Binary package hint: samba
The Samba postinst maintainer script systematically import all account
with uid >= 1000. This is so that user account and such have
corresponding Samba account. In most case, this is a good thing and
make. However, where the machine has been configured with a network
directory as the source of user account (ie, using nss_ldap), this may
not be desirable. Especially if the network directory host a large
number of user accounts, this could be very wasteful.
The behavior of the account import is preseedable with the
samba/generate_smbpasswd debconf template. This is good, but it's an
either/or proposition.
Perhaps it would be better if we where only importing local users (those
listed in /etc/passwd)? We could do that by specifying the compat
service to getent ("-s compat") in the samba.postinst maintainer script,
such as:
if [ "${GENERATE_SMBPASSWD}" = "true" -a ! -e /var/lib/samba/passdb.tdb -a ! -e
/etc/samba/smbpasswd ]; then
getent -s compat passwd | mksmbpasswd > /etc/samba/smbpasswd
pdbedit -i smbpasswd -e tdbsam -d 0
rm /etc/samba/smbpasswd
fi
I guess the implication owuld need to be considered, and the first thing is to
decide whether there is a good reason to import the non-local account in Samba.
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
https://bugs.launchpad.net/bugs/721514
Title:
Samba should be more selective when importing accounts
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 302148] Re: Installing wine starts winbindd as a daemon
As Thierry and Anders pointed out above, this might be causing breakage. See bug #605326, for example. Considering we are installing recommended package by default, this ought to be reviewed. I think winbind should be made a Suggests of wine instead, since the NTLM authentication feature is not something most users will actually need or want. That's what Debian does too. I do not see how this could be fixed in samba. Spinning ntlm_auth in its own package would not help, as it would (likely) depends in turn on winbind. I am retargeting this bug to wine again (sorry, Scott) so it can get some discussion. ** Package changed: samba (Ubuntu) => wine (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. https://bugs.launchpad.net/bugs/302148 Title: Installing wine starts winbindd as a daemon -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 683955] Re: [SRU] Please upgrade tftpd-hpa in lucid to at least 5.0-14
As a note, you need to turn on verbosity by adding -v to TFTP_OPTIONS in /etc/default/tftpd-hpa, otherwise the daemon do not log file get. Useful to know when testing. Beside, I can confirm the proposed update fix the bug too. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tftp-hpa in ubuntu. https://bugs.launchpad.net/bugs/683955 Title: [SRU] Please upgrade tftpd-hpa in lucid to at least 5.0-14 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 604400] Re: Confusing comment in /etc/eucalyptus/eucalyptus.conf
Dave: again, sorry I can't produce the correct text, as I am not sure what the exact behavior is supposed to be. Feel free to mark as Won't Fix, if you think it does not deserve to be clarified. ** Changed in: eucalyptus (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. https://bugs.launchpad.net/bugs/604400 Title: Confusing comment in /etc/eucalyptus/eucalyptus.conf -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 684399] Re: package winbind 2:3.4 .7~dfsg-1ubuntu3.2 failed to install/upgrade: el s ubproceso script post-installation instalado devolvió el código de salida de error 1
On 10-12-03 02:08 PM, Clint Byrum wrote: > I also see in the > DpkgTerminalLog.gz that nmbd fails to stop, meaning it is not running. I > may be wrong here, but I believe nmbd is necessary for winbind. No, nmbd is not strictly required for winbindd. But the fact that nmbd fail to start is indeed symptomatic of a misconfiguration. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. https://bugs.launchpad.net/bugs/684399 Title: package winbind 2:3.4.7~dfsg-1ubuntu3.2 failed to install/upgrade: el subproceso script post-installation instalado devolvió el código de salida de error 1 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 661547] Re: Existing patch gssapi.diff makes guess_service_principal produce garbage
Unless I am mistaken, this bug render likewise-open DOA. Now that the last update to openldap in maverick-proposed has gone through, I guess it would be a good time to push this one. Not trying to push anybody around. I swear, I would do it myself if I had the credentials! :) -- Existing patch gssapi.diff makes guess_service_principal produce garbage https://bugs.launchpad.net/bugs/661547 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 654249] Re: libnss-ldap create troubles in gnome session when ldap server is unreacheable
By design, the NSS library is expecting the database to be available and fast to query. When the NSS database become unresponsive (as is the case when using libnss-ldap and the the LDAP directory become unavailable), this assumption breaks and functions such as getpwnam() blocks, which can cause any kinds of funny symptoms in the calling application. This is not really a bug, more like a design flaw in NSS, so there really isn't a good solution for that. If it was my call, I would close this bug as Invalid, even though it is a very real problem, because it is not strictly speaking a "bug", or at least not one we can solve in the context of one specific package or library. ld2ndR: the solution to your problem is to use a NSS backend that can work offline, such as SSSD, libnss-ldapd or winbind. Using nscd may help. You can also alleviate the symptoms somewhat by setting bindpolicy to soft, and timelimit and bind_timelimit to low value in /etc/ldap.conf. -- libnss-ldap create troubles in gnome session when ldap server is unreacheable https://bugs.launchpad.net/bugs/654249 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 613671] Re: "undefined method `closed?' for nil:NilClass" when signing certificate
Alexandre, I had the same problem. The root cause was that the "server" directive in the client's puppet.conf did not match the hostname that was used in the puppetmaster certificate. Check your puppetmaster certificate with "sudo puppetmaster -p " (where is the hostname of the puppetmaster; check /var/lib/puppet/ssl/certs/ if unsure), and look for the Subject line. The "server" directive has to match the value of CN there. That being said, that bug is terribly annoying and degrade the user experience significantly. Could it be possible to consider applying the patch in question in the next SRU of puppet? It looks pretty safe to me. -- "undefined method `closed?' for nil:NilClass" when signing certificate https://bugs.launchpad.net/bugs/613671 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 608930] [NEW] libnss-ldap needlessly (and indirectly) depend on libpam-ldap
Public bug reported: Binary package hint: libnss-ldap This has been researched on Lucid, but also affect earlier releases. libnss-ldap depends on ldap-auth-config, which depends on ldap-auth- client, which depends on libpam-ldap. This means that installing libnss-ldap will systematically pull in libpam-ldap. libpam-ldap automatically insert himself in the PAM stack, since it ship and install a pam-config profile, /usr/share/pam-configs/ldap. This profile get applied through an unconditional call to pam-auth-update in the libpam-ldap postinst maintainer script. As explained above, installing libnss-ldap indirectly configures PAM to use pam_ldap. However, there are scenario where you would use LDAP only for NSS and not for authentication. For example, when using Kerberos. A way to install libnss-ldap without pulling in libpam-ldap would be desirable in these cases. I am not too sure how this should be done. Perhaps wrapping the call to pam-auth-update in libpam-ldap.postinst inside a conditional check to a preseedable value, such as libpam-ldap/enable for example, which would default to true? ** Affects: libnss-ldap (Ubuntu) Importance: Undecided Status: New -- libnss-ldap needlessly (and indirectly) depend on libpam-ldap https://bugs.launchpad.net/bugs/608930 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 572410] Re: nmbd doesn't start because of missing testparm
The bug affects Kamic, which is LTS. I think it would be a good idea to fix this for karmic too, wouldn't it ? Karmic has still the 2.3.4.7 version. -- nmbd doesn't start because of missing testparm https://bugs.launchpad.net/bugs/572410 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 604400] Re: Confusing comment in /etc/eucalyptus/eucalyptus.conf
Dave: I would love to, except I am not too sure what the expected behavior is. It would be best if someone who actually knows what's going on write the text in question. -- Confusing comment in /etc/eucalyptus/eucalyptus.conf https://bugs.launchpad.net/bugs/604400 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 604400] Re: Confusing comment in /etc/eucalyptus/eucalyptus.conf
For the record, that "bug" made me lost a couple of hours, and left me quite frustrated. I think it is serious enough to deserve a "fix" (ie, clarifying the behavior in the in-line comment). -- Confusing comment in /etc/eucalyptus/eucalyptus.conf https://bugs.launchpad.net/bugs/604400 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 604400] [NEW] Confusing comment in /etc/eucalyptus/eucalyptus.conf
Public bug reported: In Lucid, in the file /etc/eucalyptus/eucalyptus.conf, the following comment can be found near the bottom: # Administrative overrides and customizations may go below, in accordance # with the manpage for eucalyptus.conf(5). Reading the above, one can be lead to think that the declaration above should *not* be edited, and that adding declaration below is how you should "override" the above-declared values. However, that is not quite correct. If, for example, you have the directive VNET_PRIVINTERFACE="eth0" declared above, and VNET_PRIVINTERFACE="eth1" declared below said comment, it's the first declaration that will be parsed and understood by Eucalyptus. As such, in the above example, the private interface would end up as being eth0, despite what the admin provided. And yes, that's after running "sudo restart eucalyptus-cc CLEAN=1". ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- Confusing comment in /etc/eucalyptus/eucalyptus.conf https://bugs.launchpad.net/bugs/604400 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 463449] Re: How to decrease cloud-debug / cloud-error log verbosity (or disable them)
H.M., fully agreed on all points. This topic have been brought up in the past two UDS; not sure what the roadmap for resolution is. -- How to decrease cloud-debug / cloud-error log verbosity (or disable them) https://bugs.launchpad.net/bugs/463449 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 579868] Re: Unable to use Eucalyptus' iptables-preload feature with UEC
Please disregard the previous command. Looking again, it seems like the iptables rules eucalyptus-cc set up are sufficient to NAT connection from NC to the outside world, so the private NC network topology is not made impossible by this bug. Still, iptables-preload sounds like a useful feature. It's a bummer it does not work on UEC due to /var/run being a tmpfs. We should change the location of the iptables-preload file so that it persist through reboot. Perhaps there is a compile-time option for this? Otherwise, I guess we could patch the path wherever it is hard-coded in the source. -- Unable to use Eucalyptus' iptables-preload feature with UEC https://bugs.launchpad.net/bugs/579868 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 579868] Re: Unable to use Eucalyptus' iptables-preload feature with UEC
This bug is affecting me too. A scenario where the iptables-preload feature would be needed is one where the NC are in a separate private network (where the CC would have its VNET_PRIVINTERFACE). If you wish to NAT traffic between the private NC network and the public one (where the Walrus presumably service reside) through the CC, you would need the iptables-preload feature. Technically, inthis topology, it would be possible to use another gateway between the private NC network and the outside, bu the CC is naturally positioned to provide this service. -- Unable to use Eucalyptus' iptables-preload feature with UEC https://bugs.launchpad.net/bugs/579868 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 591472] [NEW] When the eucalyptus-cc service is stopped, the private dhcpd3 is left running and the iptables rules are not flushed
Public bug reported: Binary package hint: eucalyptus-cc After stopping the eucalyptus-cc service, it seems like the private dhcpd3 process to serve IP to instances is left running. Moreover, the iptables rules added by Eucalyptus in MANAGED mode are not being flushed. Here is a screen dump to demonstrate the problem: ubu...@uec-cc1:~$ sudo status eucalyptus-cc eucalyptus-cc start/running, process 9172 ubu...@uec-cc1:~$ sudo stop eucalyptus-cc eucalyptus-cc stop/waiting ubu...@uec-cc1:~$ sudo status eucalyptus-cc eucalyptus-cc stop/waiting ubu...@uec-cc1:~$ sudo iptables -L -v -n Chain INPUT (policy ACCEPT 988 packets, 281K bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * * 0.0.0.0/00.0.0.0/0 ctstate ESTABLISHED 0 0 ACCEPT all -- * * 0.0.0.0/0 !172.19.0.0/16 Chain OUTPUT (policy ACCEPT 762 packets, 322K bytes) pkts bytes target prot opt in out source destination ubu...@uec-cc1:~$ sudo iptables -L -v -n -t nat Chain PREROUTING (policy ACCEPT 85 packets, 5100 bytes) pkts bytes target prot opt in out source destination 0 0 DNAT tcp -- * * 172.19.0.0/16 169.254.169.254 tcp dpt:80 to:169.254.169.254:8773 Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 12 720 MASQUERADE all -- * * !127.0.0.0/8 !172.19.0.0/16 Chain OUTPUT (policy ACCEPT 12 packets, 720 bytes) pkts bytes target prot opt in out source destination ubu...@uec-cc1:~$ ps -ef | grep euca dhcpd 8276 1 0 00:38 ?00:00:00 /usr/sbin/dhcpd3 -cf //var/run/eucalyptus/net/euca-dhcp.conf -lf //var/run/eucalyptus/net/euca-dhcp.leases -pf //var/run/eucalyptus/net/euca-dhcp.pid -tf //var/run/eucalyptus/net/euca-dhcp.trace eth0 ubuntu9353 9087 0 01:15 pts/100:00:00 grep --color=auto euca -- eucalyptus-cc package version 1.6.2-0ubuntu30 ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- When the eucalyptus-cc service is stopped, the private dhcpd3 is left running and the iptables rules are not flushed https://bugs.launchpad.net/bugs/591472 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 566792] Re: metadata service returns empty data with 200 OK
Daniel Nurmi wrote: > Scott, thank you for pursuing this issue. Indeed, the meta-data service > keys off of the public IP of the VM, since that is the only source > address that is translated when the NCs cannot directly contact the CLC > (MANAGED modes). In order for the meta-data service to work, the VM > needs to be assigned a public IP, and it looks like this operation is > failing (indicated by the fact that the public/private IPs being > reported are both from the private IP subnet). That is interesting. Does that mean the meta-data service would not work for instance started with "--addressing private"? -- metadata service returns empty data with 200 OK https://bugs.launchpad.net/bugs/566792 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 570923] [NEW] euca_conf --deregister-walrus usage summary is wrong
Public bug reported: Binary package hint: eucalyptus-common euca_conf --help usage summary for the --deregister-walrus argument is wrong. We get: --deregister-walrusremove walrus from EUCALYPTUS Assuming we currently have the Walrus service at 10.0.0.10, if we do: $ euca_conf --deregister-walrus 10.0.0.10 10.0.0.1 is not a valid eucalyptus configuration file If you just do "deregister-walrus" without argument, it works. euca2ools 1.2-0ubuntu10 in lucid. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- euca_conf --deregister-walrus usage summary is wrong https://bugs.launchpad.net/bugs/570923 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 559230] Re: multi-machine topology, cannot reach an instance from the CLC
Good news, but can we clarify the addressing part nonetheless? Ie, can VNET_PUBLICIPS and the IP of VNET_PUBINTERFACE on the CC be on the same subnet? -- multi-machine topology, cannot reach an instance from the CLC https://bugs.launchpad.net/bugs/559230 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 559230] Re: multi-machine topology, cannot reach an instance from the CLC
Just to explain a bit further. The reason I am suspecting VNET_PUBLICIPS to be wrong is that eth0 on the CC has two IP in the 10.55.55.0/24 range (see comment #11). I presume 10.55.55.8 is the CC actual IP, and comment #7 indicate that 10.55.55.100 is the IP of the instance. In this case, VNET_PUBLICIPS overlap with 10.55.55.0/24, which would screw up SNAT/DNAT on the CC. i am actually fairly sure if you try to connect using any other machine (not just the CLC), it is going to fail. -- multi-machine topology, cannot reach an instance from the CLC https://bugs.launchpad.net/bugs/559230 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 559230] Re: multi-machine topology, cannot reach an instance from the CLC
Looking at the comment history, I think it might be that the VNET_PUBLICIPS range and the address of VNET_PUBINTERFACE are in the same subnet, which cannot possibly work. Which is a known limitation related to netfilter; ask Dan about it. But without knowing what the value of VNET_PUBLICIPS on the CC is, I cannot be sure. -- multi-machine topology, cannot reach an instance from the CLC https://bugs.launchpad.net/bugs/559230 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 559230] Re: multi-machine topology, cannot reach an instance from the CLC
Just a question: why is VNET_PUBLICIPS commented in eucalyptus.conf? -- multi-machine topology, cannot reach an instance from the CLC https://bugs.launchpad.net/bugs/559230 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 546293] Re: No instances started if euca-run-instance is run with bug -n
It is probably the same root cause, though. Does "euca-run-instances -n 30 ..." works if you increase the value of VNET_ADDRSPERNET and do a clean restart? If yes, then it's not really a bug, although I guess euca2ools should say something meaningful about why no instance are being started. i am not sure what the correct behavior should be in this case. Should Eucalyptus actually run instances until it runs out of private address in the security group, or should it reject the entire request (like it seems to be doing here). My guess is that it should do the later, and return that it does not have resources to complete the request (or something along that line). The Eucalyptus people would know for sure what the intended behavior is supposed to be. -- No instances started if euca-run-instance is run with a large -n https://bugs.launchpad.net/bugs/546293 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 546293] Re: Cannot start more than 29 instances
Hi Carlos, I think you are having the problem discussed at: https://answers.launchpad.net/ubuntu/+source/eucalyptus/+question/87145 -- Cannot start more than 29 instances https://bugs.launchpad.net/bugs/546293 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 544292] Re: Increase m1.small memory to 192 MB
Why not 256MB? 192MB just seems ... terribly odd. CPU cores are usually the limiting factor anyway. Someone with limited memory on node controllers and/or specific requirements can always change the value in the web UI, if need be. -- Increase m1.small memory to 192 MB https://bugs.launchpad.net/bugs/544292 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 539791] Re: mount.cifs cannot mount a DFS share when using Kerberos authentication
Investigating the problem further, I thought the problem might have been that resolving the DFS referral returned a NetBIOS machine name, not a FQDN, for the server hosting the service (ie, WARTHOGS-ADC instead of warthogs-adc.warthogs.biz). After looking around, I followed the advice in Microsoft KB #244380 to make it so that Windows would return FQDN when resolving DFS referral, but it still would not work. Discussing the problem further with colleagues, it seems like cifs.upcall does do any DFS referral resolution, hence why mount.cifs fails to mount a DFS referral *just* when using Kerberos for authentication. I was pointed at the following linux-cifs-client mailing list thread explaining the situation: http://old.nabble.com/Handling-Kerberos-principals-that-don%27t- match-hostnames-td27055470.html In lucid, I tried adding -t to the cifs.spnego entry in /etc/request-key.conf, and it work indeed! \o/ Unfortunately, this option to cifs.upcall is not available in the version we ship in karmic, so this is a lucid-only workaround. However, i understand this is just working around the problem, which is that cifs.upcall do not support resolving DFS referral. Is this correct, or am I wrong somewhere? -- mount.cifs cannot mount a DFS share when using Kerberos authentication https://bugs.launchpad.net/bugs/539791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 539791] Re: mount.cifs cannot mount a DFS share when using Kerberos authentication
In lucid, there was the following in /var/log/debug that seems to relate to the problem at hand. ** Attachment added: "debug.txt" http://launchpadlibrarian.net/41057441/debug.txt -- mount.cifs cannot mount a DFS share when using Kerberos authentication https://bugs.launchpad.net/bugs/539791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 539791] Re: mount.cifs cannot mount a DFS share when using Kerberos authentication
We still have the same problem in lucid, using kernel 2.6.32-16-generic. Attached the relevant dmesg snippet. keyutils is 1.2-12, and likewise- open is 5.4.0.39949-3. ** Attachment added: "dmesg-lucid.txt" http://launchpadlibrarian.net/41056228/dmesg-lucid.txt -- mount.cifs cannot mount a DFS share when using Kerberos authentication https://bugs.launchpad.net/bugs/539791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 539791] Re: mount.cifs cannot mount a DFS share when using Kerberos authentication
The output of klist after running the mount.cifs command. ** Attachment added: "klist.txt" http://launchpadlibrarian.net/41051333/klist.txt -- mount.cifs cannot mount a DFS share when using Kerberos authentication https://bugs.launchpad.net/bugs/539791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 539791] Re: mount.cifs cannot mount a DFS share when using Kerberos authentication
For comparison purpose, here is the output of "smbclient -d3 -k -c showconnect //warthogs.biz/namespace1/firstshare". We can see that it work as expected. ** Attachment added: "smbclient.txt" http://launchpadlibrarian.net/41051221/smbclient.txt -- mount.cifs cannot mount a DFS share when using Kerberos authentication https://bugs.launchpad.net/bugs/539791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 539791] Re: mount.cifs cannot mount a DFS share when using Kerberos authentication
For comparison purpose, here is the output of "smbclient -d3 -k -c showconnect //warthogs.biz/namespace1/firstshare". We can see that it work as expected. -- mount.cifs cannot mount a DFS share when using Kerberos authentication https://bugs.launchpad.net/bugs/539791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 539791] Re: mount.cifs cannot mount a DFS share when using Kerberos authentication
** Attachment added: "dmesg.txt" http://launchpadlibrarian.net/41050898/dmesg.txt -- mount.cifs cannot mount a DFS share when using Kerberos authentication https://bugs.launchpad.net/bugs/539791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 539791] [NEW] mount.cifs cannot mount a DFS share when using Kerberos authentication
Public bug reported: Binary package hint: smbfs In Karmic, it is possible to mount a CIFS filesystem from a DFS referral, but it would fail when using Kerberos authentication. Witness: warthogs\ca...@karmic-desktop:~$ mount.cifs //warthogs.biz/namespace1/firstshare share --verbose -o sec=krb5 mount.cifs kernel mount options: unc=//warthogs.biz\namespace1,user=carol,,domain=WARTHOGS,ver=1,sec=krb5,uid=23801,gid=23201,prefixpath=firstshare,ip=192.168.122.200 mount error(126): Required key not available Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) In the above example, //warthogs.biz/namespace1/firstshare is a DFS referral that points to //warthogs-adc/share1. When not specifying "-o sec=krb5" (or when using "-o sec=ntlm"), the mount complete just fine. It also work is I use the direct UNC path, //warthogs-adc/share1, with "-o sec=krb5", so it does really appear that the problem manifest itself only when both conditions are true (the UNC path is a DFS referral *and* we are authenticating using Kerberos). uname -r: 2.6.31-20-generic keyutils 1.2-10 (no change to /etc/request-key.conf) likewise-open5 5.0.3991.1+krb5-0ubuntu2, AD functional level Win2k3 domain joined. I assigned the bug to smbfs, but I think it might actually be in the cifs kernel module and not in smbfs at all. I attached the relevant part of dmesg, after enabling the cifs module debug mode (echo 1 > /proc/fs/cifs/cifsFYI). ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- mount.cifs cannot mount a DFS share when using Kerberos authentication https://bugs.launchpad.net/bugs/539791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 519648] Re: After all-in-one setup node-cert.pem and node-pk.pem not found
For the record, I had a all-in-one UEC system running on jaunty in SYSTEM mode a while ago. I still have my notes somewhere, although I doubt they would be very applicable to lucid. -- After all-in-one setup node-cert.pem and node-pk.pem not found https://bugs.launchpad.net/bugs/519648 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527143] [NEW] /etc/default/openbsd-inetd missing from package
Public bug reported: Binary package hint: openbsd-inetd /etc/default/openbsd-inetd is being sourced from /etc/init.d/openbsd- inetd, but no such file is included in the openbsd-inetd package. This is not such a terrible thing, as the init script will run just fine anyway. I guess it would be nice for the package to have a placeholder init script option file in /etc/default/ (with a commented OPTIONS directive, for example), if only because it is expected from service that source one. This was witnessed on karmic, openbsd-inetd 0.20080125-2ubuntu1. ** Affects: openbsd-inetd (Ubuntu) Importance: Undecided Status: New -- /etc/default/openbsd-inetd missing from package https://bugs.launchpad.net/bugs/527143 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openbsd-inetd in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 524101] Re: optionally fetch public ssh keys from Launchpad when starting an instance
Rather, if euca-add-keypair could be pointed to an existing id file (optionally, pointing to one stored in Launchpad), that would be terrific. The fact that we have to generate a new key each time we upload an identity to EC2/Eucalyptus is terribly annoying; using an existing identity/key pair would be a huge usability improvement over ec2-api-tools. -- optionally fetch public ssh keys from Launchpad when starting an instance https://bugs.launchpad.net/bugs/524101 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 253937] Re: Local login fails without LDAP server
Derek Simkowiak wrote: > In my opinion this is an important bug. One of the major reasons for > using LDAP+nss is for high availability in corporate networks... and > this bug breaks that completely. You are starting with a wrong assumption: using nss_ldap will not provide you with any type of high-availability. In fact, it may have the opposite effect, as authentication becomes dependent on the availability of network and LDAP directory service. That being said, the bug is not really one; it is more of an architectural shortcoming. And it is not specific to Ubuntu: any Unix (including pretty much every other Linux distributions) that implement NSS as stateless library is bound to have the same problem. NSS was written as an abstraction layer that assumed the database, traditionally file such as /etc/passwd, are always available and cheap to query. These assumptions break down when the database had to be queried over the network. There is no proper fix, outside of ripping off NSS entirely for something new (which is not practical, as you can guess). All you can do is to mitigate the problem. Tweaking the various limit in /etc/ldap.conf is useless; even very short timeouts do add up. nscd, which is buggy as hell anyway, will block the second it has to query the network database because it does not keep state in the first place. The only solution that can provide some relief is to have a daemon sit between the library and the network database to cache network queries and to keep state of the network database. And continue to return results without blocking when it is not, unlike nscd. Solaris had such a thing for quite some time, with good results. In Ubuntu, the libnss-ldapd and sssd package, and the nssov slapd overlay, provide just that. I have not experienced with any of them, so I cannot make an enlightened recommendation, but they all tries to address exactly the problem being discussed here. I suggest you investigate them, and reports bug you find along the way. -- Etienne Goyer Technical Account Manager - Canonical Ltd Ubuntu Certified Instructor -LPIC-3 ~= Ubuntu: Linux for Human Beings =~ -- Local login fails without LDAP server https://bugs.launchpad.net/bugs/253937 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 475354] Re: Hostname not set correctly on UEC cloud due to IP address in local-hostname manifest data
Dan, would enabling the Eucalyptus DNS feature actually fix this problem? If so, then is there a good reason to disable it in the first place? -- Hostname not set correctly on UEC cloud due to IP address in local-hostname manifest data https://bugs.launchpad.net/bugs/475354 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 513379] Re: UEC Cluster name should have a default value
The above could have used a smiley on my part, so there: :D -- UEC Cluster name should have a default value https://bugs.launchpad.net/bugs/513379 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 513379] Re: UEC Cluster name should have a default value
Dustin Kirkland wrote: > How about "cluster1"? Which is actually a Pink Floyd reference? :-) > * http://en.wikipedia.org/wiki/Cluster_One Ok, that is passable. Could have been more geeky, though. -- UEC Cluster name should have a default value https://bugs.launchpad.net/bugs/513379 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 458203] Re: euca_conf is missing command-line completion
Dustin Kirkland wrote: > Possibly a paper-cut? Totally! Nominating. ** Also affects: server-papercuts Importance: Undecided Status: New -- euca_conf is missing command-line completion https://bugs.launchpad.net/bugs/458203 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 513379] Re: UEC Cluster name should have a default value
Boring. Why not "warthogs"? -- UEC Cluster name should have a default value https://bugs.launchpad.net/bugs/513379 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 493565] Re: Cifs mount fails when DFS referrals are used by server, keyutils needed
Thierry: I cannot think of a downside to having keyutils installed. mount.cifs can authenticate using NTLM. In fact, this is the default. Kerberos authentication for CIFS mount is only really used in Active Directory context. In that use-case, the administrator of the machine mounting a CIFS share already had to do something (join the AD and/or configure Kerberos), hence my earlier comment. However, making keyutils a Recommends of smbfs make sense to me. I would go for that, as it would simplify the process. Here's for a Server paper cut right there! -- Cifs mount fails when DFS referrals are used by server, keyutils needed https://bugs.launchpad.net/bugs/493565 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 493565] Re: Cifs mount fails when DFS referrals are used by server, keyutils needed
It is worth noting that smbfs already Suggests keyutils. I am not sure it should be made a Depends, tough. Kerberos authentication is only one possible mechanism, and already requires setting up Kerberos. Maybe the requirement for keyutils could be documented in a README.Debian? -- Cifs mount fails when DFS referrals are used by server, keyutils needed https://bugs.launchpad.net/bugs/493565 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 452323] Re: kvm disabled in bios (was: Unable to start EUC instances - no supported architecture for os type 'hvm')
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 for os type 'hvm') https://bugs.launchpad.net/bugs/452323 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.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 322511] Re: Time is being adjusted by ntpdate even if you choose to manage time manually in System > Administration > Time and Date
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 manually in System > Administration > Time and Date https://bugs.launchpad.net/bugs/322511 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 459204] Re: The text debconf template eucalyptus/publicips is wrong
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 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 459204] [NEW] The text debconf template eucalyptus/publicips is wrong
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 The range you enter is used as-is for the value of VNET_PUBLICIPS in /etc/eucalyptus/eucalyptus.conf. The result, when trying to run an instance, will give you: cloudmas...@uec-frontend:~$ euca-run-instances -t c1.medium -k warthogs-key emi-00561159 FinishedVerify: Not enough resources available: addresses (try --addressing private) Moreover, running euca-describe-address return nothing. That appears to be because Eucalyptus expect the value of VNET_PUBLICIPS to be a list of space-separated IP, not a range (at least, that is how it was in jaunty). If you change the value of VNET_PUBLICIPS to a list of space-separated IP and restart Eucalyptus, you can start instance without specifying "--addressing private", and euca-describe-addresses return the list of addresses as expected. Marking priority High, as this could result in a (apparently) non- working installation of Eucalyptus. ** Affects: eucalyptus (Ubuntu) Importance: High Status: New -- The text debconf template eucalyptus/publicips is wrong https://bugs.launchpad.net/bugs/459204 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 458484] [NEW] euca_conf --help is wrong about --delete-nodes
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: Low Status: New ** Changed in: eucalyptus (Ubuntu) Importance: Undecided => Low -- euca_conf --help is wrong about --delete-nodes https://bugs.launchpad.net/bugs/458484 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 458211] [NEW] eucalyptus.conf is confusing and underdocumented
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 configuration directive are relevant to his specific setup. For example, let's say a system administrator is configuring a machine running only the Walrus service, to be registered with a CLC running on another machine. Is it relevant for him to define VNET_PRIVINTERFACE directive and, if so, what value should he use? And so on for pretty much all directives. At the very least, a eucalyptus.conf man page explaining in which context each directive are relevant would desirable. Better yet would be to break eucalyptus.conf in service-specific configuration file that could be documented separately, either inline or in a man page. ** Affects: eucalyptus (Ubuntu) Importance: Medium Status: New ** Changed in: eucalyptus (Ubuntu) Importance: Undecided => Medium -- eucalyptus.conf is confusing and underdocumented https://bugs.launchpad.net/bugs/458211 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 458203] [NEW] euca_conf is missing command-line completion
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 => Wishlist -- euca_conf is missing command-line completion https://bugs.launchpad.net/bugs/458203 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 457864] Re: Cloud Web interface should allow overcommit on CPU
Neil Soman wrote: > You can already set this via the MAX_CORES value in eucalyptus.conf on > individual nodes. It is unclear whether using a blanket value across all > nodes via the front end config is a good idea. We provide a finer level > control at the individual node level and I don't think this will be > changing for Karmic. The problem is that you have to go and manually change MAX_CORES on all the node controllers. Moreover, you will need to restart the NC service, which could bring downtime. Being able to overcommit resource at the cluster level would greatly simplify the process. Apparently, this is important to corporate users, as I have had that question before. I think the reasoning is sound; there is no reason to arbitrarily limit the number of instances. I am certainly not expecting such a thing to be implemented for karmic, but if it could 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 notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 455293] Re: UEC management interface still has Eucalyptus as title
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 Eucalyptus as title https://bugs.launchpad.net/bugs/455293 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 453129] [NEW] copyright file is incorrect, Eucalyptus is now licensed GPLv3
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. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- copyright file is incorrect, Eucalyptus is now licensed GPLv3 https://bugs.launchpad.net/bugs/453129 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 452323] Re: Unable to start EUC instances - no supported architecture for os type 'hvm'
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 os type 'hvm' https://bugs.launchpad.net/bugs/452323 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 253937] Re: Local login fails without LDAP server
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 database, such as happen when you invoke initgroups(), would still block. As such, GDM would still take forever to start a desktop session, even if you are running nscd. In fact, nscd is of practically no help if the network directory server goes down. > But adjusting the timeout limits should also have an effect - were you > changing the 'timelimit' or the 'bind_timelimit' setting? In normal > circumstances, I would expect the 'bind_timelimit' to be the one that > applies for such failures; 'timelimit' only matters if your server *is* > alive but is taking a pathologically long time to reply to queries. Even setting bind_timelimit (with or without "bind_policy soft") will not help much, as every NSS query will still need to wait for the timeout, and all these timeout do add up pretty quickly (we measured 45 minutes to open a GNOME session with "bind_timelimit 5" on hardy). It is a pretty complex problem. I have pushed a blueprint to resolve that, reliable-nss-caching, and mathiaz packaged the sssd client from the FreeIPA project in karmic to address that issue. We need to test it and make sure it actually resolve the issue in a resilient and scalable fashion. -- Local login fails without LDAP server https://bugs.launchpad.net/bugs/253937 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 432154] Re: dynamic block device attach/detach not functional with karmic KVM
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 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.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 432154] Re: dynamic block device attach/detach not functional with karmic KVM
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 data and indices on an EBS volume. -- dynamic block device attach/detach not functional with karmic KVM https://bugs.launchpad.net/bugs/432154 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.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 431114] Re: /var/run/eucalyptus is not being set with correct permissions on machine reboot
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 Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429754] Re: Instance fail to run
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://bugs.launchpad.net/bugs/429754 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 430820] Re: eucalyptus node install results in broken /etc/network/interfaces
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 iface eth0 inet dhcp auto br0 iface br0 inet dhcp bridge_ports eth0 --- However, the following works perfectly well: --- # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual auto br0 iface br0 inet dhcp bridge_ports eth0 --- Hence, I assume having a bridge *an* one of its member interface configured for DHCP result in broken networking. Maybe I am not correct, or the behavior is different in karmic. Attached is the output of "ip addr show" and "ip route show" with the first network config. You can see there are two default routes, etc. ** Attachment added: "Output of "ip addr show" and "ip route show"" http://launchpadlibrarian.net/31911976/ip-output.txt -- eucalyptus node install results in broken /etc/network/interfaces https://bugs.launchpad.net/bugs/430820 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 430820] Re: eucalyptus node install results in broken /etc/network/interfaces
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 because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 428010] Re: Eucalyptus cloud controller stops working suddenly
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 bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 430093] [NEW] Eucalyptus "403 Forbidden" when trying to run instance after package upgrade
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 from AWS: :1:0: syntax error EC2ResponseError: 403 Forbidden Failure: 403 Forbidden Sifting through /var/log/eucalyptus, the only interesting bits I found was in cloud-output.log. Here is what I think is relevant: 10:52:46 INFO erCertificateHandler | POST http://10.153.108.210:8774/axis2/services/EucalyptusGL HTTP/1.1 10:52:47 INFO ClusterUtil | --- 10:52:47 INFO ClusterUtil | -> [ warthogs ] Cluster certificate valid=true 10:52:47 INFO ClusterUtil | -> [ warthogs ] Node certificate valid=true 10:52:47 INFO ClusterUtil | --- 10:52:47 WARN PipelineRegistry | => More than one candidate pipeline. Ignoring offer by: internal-query-pipeline-Eucalyptus of type InternalQueryPipeline 10:52:47 INFO ServiceSinkHandler | cloud/ServiceSinkHandler:admin:35ebcdcd-94c4-4fd6-8bfc-def8a65646c1:MSG_RECEIVED:1253026367.1670:DescribeAvailabilityZonesType 10:52:47 INFO ServiceSinkHandler | cloud/ServiceSinkHandler:admin:35ebcdcd-94c4-4fd6-8bfc-def8a65646c1:MSG_SERVICED:1253026367.3360:178 10:52:51 WARN PipelineRegistry | => More than one candidate pipeline. Ignoring offer by: internal-query-pipeline-Eucalyptus of type InternalQueryPipeline 10:52:51 INFO ServiceSinkHandler | cloud/ServiceSinkHandler:admin:4af50fe8-2fac-4ecc-950a-74165696f604:MSG_RECEIVED:1253026371.3970:DescribeAvailabilityZonesType 10:52:51 INFO ServiceSinkHandler | cloud/ServiceSinkHandler:admin:4af50fe8-2fac-4ecc-950a-74165696f604:MSG_SERVICED:1253026371.4380:41 10:52:52 INFO erCertificateHandler | POST http://10.153.108.210:8774/axis2/services/EucalyptusGL HTTP/1.1 10:52:53 INFO ClusterUtil | --- 10:52:53 INFO ClusterUtil | -> [ warthogs ] Cluster certificate valid=true 10:52:53 INFO ClusterUtil | -> [ warthogs ] Node certificate valid=true 10:52:53 INFO ClusterUtil | --- 10:52:58 INFO erCertificateHandler | POST http://10.153.108.210:8774/axis2/services/EucalyptusGL HTTP/1.1 10:52:59 INFO ClusterUtil | --- 10:52:59 INFO ClusterUtil | -> [ warthogs ] Cluster certificate valid=true 10:52:59 INFO ClusterUtil | -> [ warthogs ] Node certificate valid=true 10:52:59 INFO ClusterUtil | --- 10:52:59 WARN PipelineRegistry | => More than one candidate pipeline. Ignoring offer by: internal-query-pipeline-Eucalyptus of type InternalQueryPipeline com.eucalyptus.ws.AuthenticationException: User authentication failed. at com.eucalyptus.ws.handlers.HmacV2Handler.incomingMessage(HmacV2Handler.java:165) at com.eucalyptus.ws.handlers.MessageStackHandler.handleUpstream(MessageStackHandler.java:115) at com.eucalyptus.ws.server.FilteredPipeline$StageBottomHandler.handleUpstream(FilteredPipeline.java:171) at com.eucalyptus.ws.server.NioServerHandler.messageReceived(NioServerHandler.java:111) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:114) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:385) at org.jboss.netty.handler.codec.replay.ReplayingDecoder.unfoldAndfireMessageReceived(ReplayingDecoder.java:459) at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:443) at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:381) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:342) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:329) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:330) at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:282) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:203) at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:53) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) 10:53:04 INFO erCertificateHandler | POST http://10.153.108.210:8774/axis2/services/EucalyptusGL HTTP/1.1 10:53:05 INFO ClusterUtil |
[Bug 430075] Re: eucalyptus-nc fail to upgrade to 1.6~bzr746-0ubuntu1
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 running earlier version of Eucalyptus will have to reject the package maintainer's version when upgrading. It is worth nothing that the other eucalyptus- start just fine with EUCALYPTUS="not_configured", unlike eucalyptus-nc. -- eucalyptus-nc fail to upgrade to 1.6~bzr746-0ubuntu1 https://bugs.launchpad.net/bugs/430075 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 430075] Re: eucalyptus-nc fail to upgrade to 1.6~bzr746-0ubuntu1
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, despite that I did accept the package maintainer's version. Manually fixing the config file makes the eucalyptus-nc start, and I can fix the package installation with "apt-get install -f". -- eucalyptus-nc fail to upgrade to 1.6~bzr746-0ubuntu1 https://bugs.launchpad.net/bugs/430075 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429004] Re: Eucalyptus hangs & euca-upload-bundle doesn't return
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://bugs.launchpad.net/bugs/429004 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429719] Re: Registering Walrus fail
*** 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 of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429754] Re: Instance fail to run
** 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 Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429754] [NEW] Instance fail to run
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 admin admin-default INSTANCEi-430707D2 emi-073A11200.0.0.0 0.0.0.0 pending warthogs-key2009-09-14T23:52:45.132Zeki-F2801528eri-50131678 cloudmas...@uec-frontend:~$ euca-describe-instances RESERVATION r-5254095A admin default INSTANCEi-430707D2 emi-073A11200.0.0.0 0.0.0.0 pending warthogs-key0 c1.medium 2009-09-14T23:52:45.132Z warthogseki-F2801528eri-50131678 cloudmas...@uec-frontend:~$ euca-describe-instances RESERVATION r-5254095A admin default INSTANCEi-430707D2 emi-073A11200.0.0.0 0.0.0.0 terminated warthogs-key0 c1.medium 2009-09-14T23:52:45.132Z warthogseki-F2801528eri-50131678 Attached nc.log from the only node controller. There are a bunch of error in there, but I am not sure which are relevant and which are not. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- Instance fail to run https://bugs.launchpad.net/bugs/429754 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429749] [NEW] After installation, euca-run-instances fail unless you run euca-describe-groups first
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 AVAILABILITYZONE|- vm types free / max cpu ram disk AVAILABILITYZONE|- m1.small 0004 / 0004 1128 2 AVAILABILITYZONE|- c1.medium0004 / 0004 1256 5 AVAILABILITYZONE|- m1.large 0002 / 0002 251210 AVAILABILITYZONE|- m1.xlarge0002 / 0002 2 102420 AVAILABILITYZONE|- c1.xlarge0001 / 0001 4 204820 cloudmas...@uec-frontend:~$ euca-describe-images IMAGE emi-073A1120jaunty/ubuntu.9-04.x86-64.img.manifest.xml admin available public x86_64 machine IMAGE eri-50131678 jaunty-ramdisk/initrd.img-2.6.28-11-generic.manifest.xmladmin available public x86_64 ramdisk IMAGE eki-F2801528jaunty-kernel/vmlinuz-2.6.28-11-generic.manifest.xml admin available public x86_64 kernel cloudmas...@uec-frontend:~$ euca-describe-keypairs KEYPAIR warthogs-key da:c1:0e:92:07:5c:3c:d2:51:56:10:15:7b:cf:f7:c2:f3:2c:a1:da cloudmas...@uec-frontend:~$ euca-run-instances -t c1.medium -k warthogs-key emi-073A1120 RESERVATION NoneNone cloudmas...@uec-frontend:~$ euca-describe-instances cloudmas...@uec-frontend:~$ On another machine using ec2-api-tools: etie...@curst:~/AMI/euca-ubuntu-9.04-x86_64$ ec2-run-instances -t c1.medium -k warthogs-key emi-073A1120 GroupsVerify: Error locating information for etie...@curst:~/AMI/euca-ubuntu-9.04-x86_64$ ec2-describe-instances etie...@curst:~/AMI/euca-ubuntu-9.04-x86_64$ If I describe the security group, I am then able to launch an instance: cloudmas...@uec-frontend:~$ euca-describe-groups GROUP admin default default group cloudmas...@uec-frontend:~$ euca-run-instances -t c1.medium -k warthogs-key emi-073A1120 RESERVATION r-5254095A admin admin-default INSTANCEi-430707D2 emi-073A11200.0.0.0 0.0.0.0 pending warthogs-key2009-09-14T23:52:45.132Zeki-F2801528eri-50131678 cloudmas...@uec-frontend:~$ euca-describe-instances RESERVATION r-5254095A admin default INSTANCEi-430707D2 emi-073A11200.0.0.0 0.0.0.0 pending warthogs-key0 c1.medium 2009-09-14T23:52:45.132Z warthogseki-F2801528eri-50131678 cloudmas...@uec-frontend:~$ Somehow, it appears that the group information do not get initialized properly or something. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- After installation, euca-run-instances fail unless you run euca-describe-groups first https://bugs.launchpad.net/bugs/429749 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429734] [NEW] Invalid S3_URL and EC2_URL in eucarc
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://127.0.0.1:8773/services/Eucalyptus Once you login to the web UI, change the admin password and confirm the Cloud controller IP, you can redoanload the certificate bundle and the eucarc file contains appropriate URL. These values are ok if you are using the certificate bundle on the frontend machine, but not if you transfer it to a client machine. At the very least, this is confusing. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- Invalid S3_URL and EC2_URL in eucarc https://bugs.launchpad.net/bugs/429734 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429719] Re: Registering Walrus fail
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 Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429719] Re: Registering Walrus fail
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/429719 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429719] [NEW] Registering Walrus fail
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: cloudmas...@uec-frontend:~$ sudo euca_conf --no-rsync --register-walrus 10.153.108.210 1.6-devel Adding WALRUS host 10.153.108.210 http://127.0.0.1:8773/services/Configuration?AWSAccessKeyId=WKy3rMzOWPouVOxK1p3Ar1C2uRBwa2FBXnCw&Action=RegisterWalrus&Host=10.153.108.210&Name=walrus&Port=8773&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2009-09-14T18%3A21%3A11.000Z&Version=eucalyptus&Signature=MRpYbYSDb60shAr1jq4l8e4TMfRv0BHo9chQXkWrwJo= http://msgs.eucalyptus.ucsb.edu";>95c0b6f9-c15f-4192-a6bf-e961b72b313dadmineucalyptustrue Trying scp to sync keys with "" (user "eucalyptus")... scp: //var/lib/eucalyptus/keys//euca.p12: Permission denied failed. ERROR: failed to sync keys with 10.153.108.210. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- Registering Walrus fail https://bugs.launchpad.net/bugs/429719 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429087] Re: after UEC front-end (cluster) install, key sync stage of registration cannot proceed without entering a password
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 because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429590] Re: Cannot upload bundle to Walrus
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 because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429631] [NEW] Invalid S3_URL value in eucarc
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 host, so I doubt the URL is actually correct. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- Invalid S3_URL value in eucarc https://bugs.launchpad.net/bugs/429631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429612] [NEW] SOAP error when running "euca_conf --deregister-walrus"
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-frontend:~$ sudo euca_conf --deregister-walrus uec-walrus [sudo] password for cloudmaster: 1.6-devel http://127.0.0.1:8773/services/Configuration?AWSAccessKeyId=WKy3rMzOWPouVOxK1p3Ar1C2uRBwa2FBXnCw&Action=DeregisterWalrus&Name=uec-walrus&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2009-09-14T15%3A44%3A44.000Z&Version=eucalyptus&Signature=SMUya+B6QolONTA4IF7fHgXmtDj/rg/hi2Nnd2EHxEM= http://schemas.xmlsoap.org/soap/envelope/";>ConfigurationFailed to find configuration for DeregisterWalrusType named uec-walrus SUCCESS: Walrus 'uec-walrus' successfully deregistered. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- SOAP error when running "euca_conf --deregister-walrus" https://bugs.launchpad.net/bugs/429612 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 429590] [NEW] Cannot upload bundle to Walrus
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/vmlinuz-2.6.28-11-generic.manifest.xml
Are you sure you want to specify a different EC2 public certificate? [y/n]
y
Using specified EC2 public certificate: /home/etienne/.euca-lab/cloud-cert.pem.
Server.NotReady(406): The service is not ready to accept your request
Bundle upload failed.
On the Eucalyptus frontend running Walrus, I get the following error that
appears relevant in /var/log/eucalyptus/cloud-error.log:
15:17:28 [DefaultServiceExceptionStrategy:RequestQueue.2] ERROR
Message : Component that caused exception is: RequestQueue.
Message payload is of type: GetBucketAccessControlPolicyType
Type : org.mule.api.service.ServiceException
Code : MULE_ERROR--2
Payload :
http://msgs.eucalyptus.ucsb.edu";>
347d49d6-ac9b-4d27-bc70-272d78d2ea33
admin
eucalyptus
WKy3rMzOWPouVOxK1p3Ar1C2uRBwa2FBXnCw
2009-09-14T19:17:28.511Z
jaunty-kernel
JavaDoc :
http://mule.mulesource.org/docs/apidocs/org/mule/api/service/ServiceException.html
Exception stack is:
1. The service is not ready to accept your request
(edu.ucsb.eucalyptus.cloud.NotReadyException)
com.eucalyptus.ws.util.RequestQueue:92 (null)
2. Component that caused exception is: RequestQueue. Message payload is of
type: GetBucketAccessControlPolicyType (org.mule.api.service.ServiceException)
org.mule.component.DefaultLifecycleAdapter:214
(http://mule.mulesource.org/docs/apidocs/org/mule/api/service/ServiceException.html)
Root Exception stack trace:
edu.ucsb.eucalyptus.cloud.NotReadyException: The service is not ready to accept
your request
at com.eucalyptus.ws.util.RequestQueue.handle(RequestQueue.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.mule.model.resolvers.AbstractEntryPointResolver.invokeMethod(AbstractEntryPointResolver.java:147)
at
org.mule.model.resolvers.ReflectionEntryPointResolver.invoke(ReflectionEntryPointResolver.java:178)
at
org.mule.model.resolvers.DefaultEntryPointResolverSet.invoke(DefaultEntryPointResolverSet.java:50)
at
org.mule.component.DefaultLifecycleAdapter.intercept(DefaultLifecycleAdapter.java:202)
at
org.mule.component.AbstractJavaComponent.invokeComponentInstance(AbstractJavaComponent.java:82)
at
org.mule.component.AbstractJavaComponent.doOnCall(AbstractJavaComponent.java:73)
at
org.mule.component.AbstractComponent.onCall(AbstractComponent.java:87)
at
org.mule.model.seda.SedaService$ComponentStageWorker.run(SedaService.java:533)
at org.mule.work.WorkerContext.run(WorkerContext.java:310)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:636)
15:17:28 [DefaultServiceExceptionStrategy:RequestQueue.2] ERROR Message
being processed is:
org.mule.transport.DefaultMessageAdapter/org.mule.transport.defaultmessageadap...@c089e41{id=3e3ec9ee-a163
-11de-8d5d-5544238138c0,
payload=edu.ucsb.eucalyptus.msgs.GetBucketAccessControlPolicyType,
correlationId=null, correlationGroup=-1, correlationSeq=-1,
encoding=UTF-8,
exceptionpayload=org.mule.message.defaultexceptionpayl...@9cdc393}
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
Cannot upload bundle to Walrus
https://bugs.launchpad.net/bugs/429590
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 428010] Re: Eucalyptus cloud controller stops working suddenly
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 session that suffer bug #407428? -- Eucalyptus cloud controller stops working suddenly https://bugs.launchpad.net/bugs/428010 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 427236] Re: high memory usage by CC
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.1 2206416 804664 ? Sl Aug05 1392:12 /usr/sbin/apache2 -f /etc/eucalyptus/httpd-cc.conf -- high memory usage by CC https://bugs.launchpad.net/bugs/427236 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 426830] [NEW] Add a check in eucalyptus-nc to verify that the target can run KVM
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 could just run kvm-ok in the preinst, and report status in a dialog box. This would improve the out-of-the-box experience significantly, reduce the number of people who request help following installation and simplify documentation. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- Add a check in eucalyptus-nc to verify that the target can run KVM https://bugs.launchpad.net/bugs/426830 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 425915] Re: UEC installer does not set up a bridge device by default for Eucalyptus nodes (NCs)
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 Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 365349] Re: Any network mode beside SYSTEM fail because /var/run/eucalyptus/net do not exist
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 Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 411656] Re: eucalyptus-nc should depend on ssh
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 Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 364938] Re: In /etc/eucalyptus/eucalyptus.conf, VNET_DHCPDAEMON and VNET_DHCPUSER should be set to value appropriate for Ubuntu
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 appropriate for Ubuntu https://bugs.launchpad.net/bugs/364938 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 364723] Re: eucalyptus-nc service fail to start at boot, cannot connect to libvirtd
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 Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 424457] [NEW] "euca_conf --register-nodes" message is misleading
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 installed in / for key synchronization. Trying scp to sync keys with "" (user "eucalyptus")... done. -- There is two issues with this output: 1. The INFO line is misleading; what exactly does that mean? 2. In 'Trying scp to sync keys with "" (user "eucalyptus")...', I believe the empty "" should contains the node controller name or IP being joined. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- "euca_conf --register-nodes" message is misleading https://bugs.launchpad.net/bugs/424457 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 424442] [NEW] eucalyptus-nc should depend on avahi-utils
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 script. Symptoms: ubu...@uec-nc2:~$ dpkg -l eucalyptus-nc Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=-=-== ii eucalyptus-nc 1.6~bzr645-0ubuntu1 Elastic Utility Computing Architecture - Node controller ubu...@uec-nc2:~$ sudo service eucalyptus-nc restart You should have at least 32 loop devices * Restarting Eucalyptus Node Service Warning! Cannot find bridge xenbr0: instances may be without net start-stop-daemon: signal value must be numeric or name of signal (KILL, INT, ...) Try `start-stop-daemon --help' for more information. [ OK ] ubu...@uec-nc2:~$ sudo apt-get install avahi-utils [...snip...] Setting up avahi-utils (0.6.25-1ubuntu2) ... ubu...@uec-nc2:~$ sudo service eucalyptus-nc restart You should have at least 32 loop devices * Restarting Eucalyptus Node Service Warning! Cannot find bridge xenbr0: instances may be without net (The xenbr0 warning is an entirely different bug) ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- eucalyptus-nc should depend on avahi-utils https://bugs.launchpad.net/bugs/424442 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 389909] Re: Change resolve order so Nautilus can browse local network when ISP uses DNS redirection
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 a coherent policy on the subject. It would also be interesting to know what is the default behavior in Samba 4. -- Change resolve order so Nautilus can browse local network when ISP uses DNS redirection https://bugs.launchpad.net/bugs/389909 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 236640] Re: iSCSI install fails under hardy
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 used the iSCSI target to host the /home file system, and it worked fine. -- 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 mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 236640] Re: iSCSI install fails under hardy
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 Server Team, which is subscribed to open-iscsi in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
