[Bug 833994] Re: debian-installer does not support https when using with preseed files
Verified. Thanks! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler-enlist in Ubuntu. https://bugs.launchpad.net/bugs/833994 Title: debian-installer does not support https when using with preseed files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler-enlist/+bug/833994/+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 833994] Re: debian-installer does not support https when using with preseed files
Hi Lezgin, This is already in 14.04. You can test right away. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler-enlist in Ubuntu. https://bugs.launchpad.net/bugs/833994 Title: debian-installer does not support https when using with preseed files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler-enlist/+bug/833994/+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 1029977] Re: dnsmasq-base should ship the dnsmasq dbus configuration file
Looks good to me. The version of dnsmasq-base in proposed starts dnsmasq correctly with 'sudo dnsmasq --enable-dbus'. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1029977 Title: dnsmasq-base should ship the dnsmasq dbus configuration file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1029977/+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 738219] Re: autofs should always start before at and cron
** Changed in: autofs (Ubuntu) Assignee: Clint Byrum (clint-fewbar) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/738219 Title: autofs should always start before at and cron To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/738219/+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 1004775] Re: NetworkManager restarts dnsmasq and adds host route on every IPv6 route lookup
I think this should be marked "Fixed Released" for Precise now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1004775 Title: NetworkManager restarts dnsmasq and adds host route on every IPv6 route lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1004775/+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 752316] Re: Package vlan should be included in nova-compute's dependencies
The problem is that VLAN is the default network mode in OpenStack. We ought to support the default settings "out of the box". -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/752316 Title: Package vlan should be included in nova-compute's dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/752316/+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 280421] Re: ethtool not available in post-ifup script
Sorry for the delay. This fix looks good to me and the customer has also verified. Thanks, everyone! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ethtool in Ubuntu. https://bugs.launchpad.net/bugs/280421 Title: ethtool not available in post-ifup script -- 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 777193] Re: ethtool settings may not apply on boot with separate /usr
*** This bug is a duplicate of bug 280421 *** https://bugs.launchpad.net/bugs/280421 Except my customer is running Lucid. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ethtool in Ubuntu. https://bugs.launchpad.net/bugs/777193 Title: ethtool settings may not apply on boot with separate /usr -- 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 777193] Re: ethtool settings may not apply on boot with separate /usr
** Description changed: Binary package hint: ethtool Description: Ubuntu 10.04 LTS Release: 10.04 ethtool: - Installed: 6+20091202-1 - Candidate: 6+20091202-1 + Installed: 6+20091202-1 + Candidate: 6+20091202-1 System has ethtool setting in /etc/network/interfaces, in this case: HARDWARE_DMA_RING_ rx 512 The default setting is 256. You can check the setting with `ethtool -g eth0`. Expected behavior: on startup (actually on any ifup), /etc/network/if- up.d/ethtool should run, read /etc/network/interfaces and apply ethtool settings if they are there. Observed behavior: on this system, it's clear that /etc/network/if- up.d/ethtool is executed before /usr is mounted, therefore the setting does apply as the ethtool binary is on /usr. The setting applies fine if you do an ifdown and ipup manually after startup. + Public bug filed by GSS (Mark Russell): + https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/777193 + + PUB: 777193 + REF: 500D00EtXNP I will attach logs showing what's happening. ** Description changed: Binary package hint: ethtool Description: Ubuntu 10.04 LTS Release: 10.04 ethtool: Installed: 6+20091202-1 Candidate: 6+20091202-1 System has ethtool setting in /etc/network/interfaces, in this case: HARDWARE_DMA_RING_ rx 512 The default setting is 256. You can check the setting with `ethtool -g eth0`. Expected behavior: on startup (actually on any ifup), /etc/network/if- up.d/ethtool should run, read /etc/network/interfaces and apply ethtool settings if they are there. Observed behavior: on this system, it's clear that /etc/network/if- up.d/ethtool is executed before /usr is mounted, therefore the setting does apply as the ethtool binary is on /usr. The setting applies fine if you do an ifdown and ipup manually after startup. Public bug filed by GSS (Mark Russell): https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/777193 + I will attach logs showing what's happening. + PUB: 777193 REF: 500D00EtXNP - I will attach logs showing what's happening. ** Description changed: Binary package hint: ethtool Description: Ubuntu 10.04 LTS Release: 10.04 ethtool: Installed: 6+20091202-1 Candidate: 6+20091202-1 System has ethtool setting in /etc/network/interfaces, in this case: HARDWARE_DMA_RING_ rx 512 The default setting is 256. You can check the setting with `ethtool -g eth0`. Expected behavior: on startup (actually on any ifup), /etc/network/if- up.d/ethtool should run, read /etc/network/interfaces and apply ethtool settings if they are there. Observed behavior: on this system, it's clear that /etc/network/if- up.d/ethtool is executed before /usr is mounted, therefore the setting does apply as the ethtool binary is on /usr. The setting applies fine if you do an ifdown and ipup manually after startup. Public bug filed by GSS (Mark Russell): https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/777193 I will attach logs showing what's happening. - - PUB: 777193 - REF: 500D00EtXNP -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ethtool in Ubuntu. https://bugs.launchpad.net/bugs/777193 Title: ethtool settings may not apply on boot with separate /usr -- 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 777193] Re: ethtool settings may not apply on boot with separate /usr
In this log first we show a couple of changes put into /etc/network/if- up.d/ethtool for logging information. It consists of echoing the time and checking mount a few times during the script. Then the results. ** Attachment added: "ethtool-start.log" https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/777193/+attachment/2112204/+files/ethtool-start.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ethtool in Ubuntu. https://bugs.launchpad.net/bugs/777193 Title: ethtool settings may not apply on boot with separate /usr -- 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 777193] [NEW] ethtool settings may not apply on boot with separate /usr
Public bug reported: Binary package hint: ethtool Description: Ubuntu 10.04 LTS Release: 10.04 ethtool: Installed: 6+20091202-1 Candidate: 6+20091202-1 System has ethtool setting in /etc/network/interfaces, in this case: HARDWARE_DMA_RING_ rx 512 The default setting is 256. You can check the setting with `ethtool -g eth0`. Expected behavior: on startup (actually on any ifup), /etc/network/if- up.d/ethtool should run, read /etc/network/interfaces and apply ethtool settings if they are there. Observed behavior: on this system, it's clear that /etc/network/if- up.d/ethtool is executed before /usr is mounted, therefore the setting does apply as the ethtool binary is on /usr. The setting applies fine if you do an ifdown and ipup manually after startup. I will attach logs showing what's happening. ** Affects: ethtool (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ethtool in Ubuntu. https://bugs.launchpad.net/bugs/777193 Title: ethtool settings may not apply on boot with separate /usr -- 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 741754] Re: multipath load not balancing across two iscsi connections
This was intended as a private bug, but I marked it incorrectly. It will be tracked internally in another bug. When we determine the actual root cause, a public bug will be opened with the results or this one will be reactivated. ** Changed in: multipath-tools (Ubuntu) Status: New => Invalid ** Attachment removed: "multipath-ll-v4-twice.txt" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/741754/+attachment/1936758/+files/multipath-ll-v4-twice.txt ** Attachment removed: "output.txt" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/741754/+attachment/1936760/+files/output.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/741754 Title: multipath load not balancing across two iscsi connections -- 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 741754] Re: multipath load not balancing across two iscsi connections
** This bug has been flagged as a security vulnerability -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/741754 Title: multipath load not balancing across two iscsi connections -- 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 741754] Re: multipath load not balancing across two iscsi connections
Output of: for i in $(find /dev -name 'sd[a-z]'); do echo "XXX Basic Inquiry: $i" sg_inq -v $i echo "XXX Serial Number page: $i" sg_vpd -p sn $i echo "XXX Device Information page: $i" sg_vpd -p di $i echo "XXX Verbose report target port group: $i" sg_rtpg -v $i done ** Attachment added: "output.txt" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/741754/+attachment/1936760/+files/output.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/741754 Title: multipath load not balancing across two iscsi connections -- 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 741754] Re: multipath load not balancing across two iscsi connections
Output of `multipath -ll -v4` when "not in balance" and "balanced". ** Description changed: Binary package hint: multipath-tools - + Details: + + Customer is running Ubuntu Server 10.04 amd64 on ESX. + Connecting via open-iscsi to a Dell EqualLogic SAN. Using two paths for each LUN. + + On startup, customer reports that the load is only going over one NIC. + It's appears random whether it's eth1 or eth2, but the load is never + distributed across both. + + After the system is up multipath will (seeminly randomly) report one of the following: + - 0 devices and paths + - some number of devices and paths + - all devices and paths + + However: multipath is not working. Although it shows all paths after + they issue a `multipath -v2` they aren't all in use. In order to make + them ACTIVE they need to unmount the filesystem, deactive the volume + group, reactivate, remount and then it works. ** Attachment added: "multipath-ll-v4-twice.txt" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/741754/+attachment/1936758/+files/multipath-ll-v4-twice.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/741754 Title: multipath load not balancing across two iscsi connections -- 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 741754] [NEW] multipath load not balancing across two iscsi connections
Private bug reported: Binary package hint: multipath-tools ** Affects: multipath-tools (Ubuntu) Importance: Undecided Status: New ** Visibility changed to: Private -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/741754 Title: multipath load not balancing across two iscsi connections -- 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 569757] Re: NIS upstart dependancy broken for lucid
atd is another one that needs to wait for ypbind. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for 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 738209] Re: autofs appears to be started before it is truly functional
You can work around this issue by adding this to the end of /etc/init/autofs.conf: post-start script sleep 5 end script -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. https://bugs.launchpad.net/bugs/738209 Title: autofs appears to be started before it is truly functional -- 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 738219] Re: autofs should always start before at and cron
You may still encounter a race condition where autofs reports itself as "started" slightly before it is really ready (see bug #738209) and still end up with the same result but that is outside the scope of this bug. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. https://bugs.launchpad.net/bugs/738219 Title: autofs should always start before at and cron -- 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 738219] Re: autofs should always start before at and cron
This "wait job" produces the correct result. Just add it to /etc/init. It will block cron and atd until autofs is running. ** Attachment added: "autofs-wait.conf" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/738219/+attachment/1922028/+files/autofs-wait.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. https://bugs.launchpad.net/bugs/738219 Title: autofs should always start before at and cron -- 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 738219] [NEW] autofs should always start before at and cron
Public bug reported: Binary package hint: autofs Description: Ubuntu 10.04.2 LTS Release: 10.04 Installed: 5.0.4-3.1ubuntu5.1 If autofs is installed and running, it needs to start before atd or cron. Example, you have an @reboot cronjob that reads or writes to an automounted directory, if the automount isn't ready before cron starts, the job will fail. ** Affects: autofs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. https://bugs.launchpad.net/bugs/738219 Title: autofs should always start before at and cron -- 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 738209] [NEW] autofs appears to be started before it is truly functional
Public bug reported: Binary package hint: autofs Description:Ubuntu 10.04.2 LTS Release:10.04 Installed: 5.0.4-3.1ubuntu5.1 Brief summary: autofs, in upstart terms, becomes "started" before it is actually ready. There seems to be a brief window immediately after "started" where if you run something expecting to be able to read or write to an automounted directory it will either fail (on a read or a write to a subdir of the mount) or write to the empty mountpoint (on a write to the root of the mount). Even though `status autofs` is "started/running" the mounts aren't ready. If you sleep for a few seconds in the post-start script it covers up for the bug in most cases (probably) but the exact number may vary by system. ** Affects: autofs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. https://bugs.launchpad.net/bugs/738209 Title: autofs appears to be started before it is truly functional -- 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
