[Bug 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
Over a year old, never addressed. Closing. I think it eventually went away so probably fixed. ** Changed in: chkrootkit (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+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 565578] Re: chkutmp crashed with SIGSEGV in _Unwind_Backtrace()
Old bug ** Changed in: chkrootkit (Ubuntu) Status: Expired = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/565578 Title: chkutmp crashed with SIGSEGV in _Unwind_Backtrace() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/565578/+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 641657] Re: SSH connections freeze after a period of time
Maverick is dead. Closing bug properly. ** Changed in: openssh (Ubuntu) Status: Expired = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/641657 Title: SSH connections freeze after a period of time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/641657/+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
[Blueprint server-o-load-testing] Server Load Testing Suite
Blueprint changed by Jeff Lane: Whiteboard changed: Work Items: - [bladernr] Jeff to list the testing team info so interested parties can sign up and participate in making this happen: DONE - Create a list of the tests to be run (a small number of useful tests to start, we can expand afterwards).: TODO - Documentation of test cases and configs and other useful information (wiki?, testcases.qa.ubuntu.com?): TODO - Package a consistently runnable test suite: TODO + [bladernr] Jeff to list the testing team info so interested parties can sign up and participate in making this happen: DONE + [hardware-cert team] Create a list of the tests to be run (a small number of useful tests to start, we can expand afterwards).: TODO + [hardware-cert team] Documentation of test cases and configs and other useful information (wiki?, testcases.qa.ubuntu.com?): TODO + [hardware-cert team] Package a consistently runnable test suite: TODO Previous discussions: https://blueprints.launchpad.net/ubuntu/+spec/packageselection-arm-server-optimized-lamp-stack https://wiki.ubuntu.com/UDSProceedings/N/PackageSelectionAndSystemDefaults#Arm%20Server%20Optimized%20Lamp%20Stack Notes from this session: http://summit.ubuntu.com/uds-o/meeting/server-o-load-testing/ Q: Can you please try to address IPMI (Server management) as well A: To what extent? There is already an IPMI test that performs basic function testing (e.g. connect to the BMC, pull SEL events and system info to ensure that the IPMI bits are working). Definition of Done: 1: Defined list of specific hardware subsystems on servers that are to be tested 2: Defined list of specific common server applications that are to be tested 3: Scope infrastructure changes as may be needed (new hardware, etc) 4: Defined list of tests that will verify server stability and functionality 5: Defined limits on what is acceptable load minimums and maximums for testing 6: Defined list of which tests will be hardware certification tests and which will be QA style tests 7: Responsibilities for each set of tests assigned to the appropriate teams 8: Tests written if they do not currently exist, tested for usability and implemented in Checkbox 9: Separate whitelists defined in checkbox for server certification and server QA 10: New infrastructure in place and operational if necessary 11: Servers tested using full server certification and server QA whitelists 12: 11.10 is thoroughly hammered using our new combined Super Monkey Powers 13: 12.04 is the best Server LTS EVER! -- Server Load Testing Suite https://blueprints.launchpad.net/ubuntu/+spec/server-o-load-testing -- 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 828437] [NEW] chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
Public bug reported: Walked away for a while and returned to find my system almost unusable. Something was causing the DISK I/O to go through the roof, the system constantly waiting, making it, as I said, almost unusable. On some investigation, top indicated that egrep was consuming 6.7 GB of actual memory (of 8 GB total system RAM). Looking at the output of 'ps axf' showed 14 instances of chkrootkit and egrep's My system being DOS'd locally by chkrootkit... the irony is not lost on me. No idea why this happened, or even where to start wtih it, but I thought I'd at least open a bug and report what I could... but I had to reboot the system the hard way before I could even do that. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: chkrootkit 0.49-4ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Aug 17 20:34:52 2011 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chkrootkit UpgradeStatus: Upgraded to natty on 2011-06-03 (75 days ago) ** Affects: chkrootkit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+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 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+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 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
This is a batch mode output from top, showing the egrep process consuming 6.7GB of my RAM... ** Attachment added: top.log https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+attachment/2287476/+files/top.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+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 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
this is a capture of ps axf before rebooting the system to make it usable again. Notice the 14 instances of egrep spawned by chkrootkit. ** Attachment added: ps-axf.log https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+attachment/2287477/+files/ps-axf.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+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 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
Also, this might actually be an issue created by tiger, rather than chkrootkit itself... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+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 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
Serge: at the moment, no. I can't manually reproduce it. However, I left the machine sitting over night and came back this morning to find that it was stuck yet again, this time, the egrep process was using 7.1GB of 8GB, but PS only showed 2 instances running... I'm currently running tiger manually to see if it's tiger itself, or something related to running via CRON. after the manual run, I'll try running the commands from the cron scripts manually and see if that recreates the issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+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 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
forgot to reset to new when I added my update. ** Changed in: chkrootkit (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+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 1210307] [NEW] package tgt 1:1.0.37-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: Did a general dist-upgrade on saucy. I have TGT installed for some work with devstack. For some reason, tgt failed to upgrade and that caused apt to throw an error. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: tgt 1:1.0.37-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Thu Aug 8 08:49:58 2013 DuplicateSignature: package:tgt:1:1.0.37-0ubuntu1:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2012-03-15 (511 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120307) MarkForUpload: True SourcePackage: tgt Title: package tgt 1:1.0.37-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to saucy on 2013-06-22 (47 days ago) modified.conffile..etc.init.tgt.conf: [deleted] mtime.conffile..etc.tgt.targets.conf: 2013-05-10T14:34:21.654054 ** Affects: tgt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1210307 Title: package tgt 1:1.0.37-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1210307/+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 1210307] Re: package tgt 1:1.0.37-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
* Stopping target framework daemon tgtd ESC[80G ^MESC[74G[ESC[31mfailESC[39;49m] invoke-rc.d: initscript tgt, action stop failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... * Stopping target framework daemon tgtd ESC[80G ^MESC[74G[ESC[31mfailESC[39;49m] invoke-rc.d: initscript tgt, action stop failed. dpkg: error processing /var/cache/apt/archives/tgt_1%3a1.0.38-0ubuntu1_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 1 There appears to be no log for tgt... the only references I could find are the above in apt/term.log and the following from syslog: Sep 5 10:55:56 klaatu tgtd: semkey 0x610ff449 Sep 5 10:55:56 klaatu tgtd: tgtd daemon started, pid:14792 Sep 5 10:55:56 klaatu tgtd: tgtd logger started, pid:14793 debug:0 Sep 5 10:55:56 klaatu kernel: [ 7247.887727] tgtd (14792): /proc/14792/oom_adj is deprecated, please use /proc/14792/oom_score_adj instead. Sep 5 10:55:57 klaatu tgtd: iser_ib_init(3349) Failed to initialize RDMA; load kernel modules? Sep 5 10:55:57 klaatu tgtd: work_timer_start(150) use signal based scheduler Sep 5 10:55:57 klaatu tgtd: bs_init(316) use signalfd notification ** Changed in: tgt (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1210307 Title: package tgt 1:1.0.37-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1210307/+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 1266840] [NEW] maas-dns failed to install completely on Trusty
Public bug reported: Installed maas packages on a fresh trusty install like so: $ sudo apt-get install maas maas-region-controller maas-cluster- controller maas-dhcp maas-dns Installation proceeded successfully until maas-dns. maas-dns errored out: Setting up maas (1.4+bzr1789+dfsg-0ubuntu1) ... Processing triggers for libc-bin ... Errors were encountered while processing: maas-dns E: Sub-process /usr/bin/dpkg returned an error code (1) After apt-get exited, I re-ran the comand and this time the configuration of maas-dns seems to have successfully completed and exited, but there was a failure when trying to restart bind9: bladernr@critical-maas:~$ sudo apt-get install maas maas-region-controller maas-cluster-controller maas-dns maas-dhcp [sudo] password for bladernr: Reading package lists... Done Building dependency tree Reading state information... Done maas is already the newest version. maas-cluster-controller is already the newest version. maas-dhcp is already the newest version. maas-dns is already the newest version. maas-region-controller is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up maas-dns (1.4+bzr1789+dfsg-0ubuntu1) ... * Stopping domain name service... bind9 waiting for pid 22203 to die [ OK ] * Starting domain name service... bind9 [fail] invoke-rc.d: initscript bind9, action restart failed. Looking in the apt term.log, I noticed this traceback the first time I tried installing maas-dns: Setting up maas-dns (1.4+bzr1789+dfsg-0ubuntu1) ... Traceback (most recent call last): File /usr/bin/django-admin, line 5, in module management.execute_from_command_line() File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line 399, in execute_from_command_line utility.execute() File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line 392, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File /usr/lib/python2.7/dist-packages/django/core/management/base.py, line 242, in run_from_argv self.execute(*args, **options.__dict__) File /usr/lib/python2.7/dist-packages/django/core/management/base.py, line 285, in execute output = self.handle(*args, **options) File /usr/lib/python2.7/dist-packages/maasserver/management/commands/set_up_dns.py, line 54, in handle upstream_dns = Config.objects.get_config(upstream_dns) File /usr/lib/python2.7/dist-packages/maasserver/models/config.py, line 93, in get_config return self.get(name=name).value File /usr/lib/python2.7/dist-packages/django/db/models/manager.py, line 151, in get return self.get_queryset().get(*args, **kwargs) File /usr/lib/python2.7/dist-packages/django/db/models/query.py, line 301, in get num = len(clone) File /usr/lib/python2.7/dist-packages/django/db/models/query.py, line 77, in __len__ self._fetch_all() File /usr/lib/python2.7/dist-packages/django/db/models/query.py, line 854, in _fetch_all self._result_cache = list(self.iterator()) File /usr/lib/python2.7/dist-packages/django/db/models/query.py, line 220, in iterator for row in compiler.results_iter(): File /usr/lib/python2.7/dist-packages/django/db/models/sql/compiler.py, line 710, in results_iter for rows in self.execute_sql(MULTI): File /usr/lib/python2.7/dist-packages/django/db/models/sql/compiler.py, line 780, in execute_sql cursor = self.connection.cursor() File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, line 159, in cursor cursor = util.CursorWrapper(self._cursor(), self) File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, line 129, in _cursor self.ensure_connection() File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, line 124, in ensure_connection self.connect() File /usr/lib/python2.7/dist-packages/django/db/utils.py, line 99, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, line 124, in ensure_connection self.connect() File /usr/lib/python2.7/dist-packages/django/db/backends/__init__.py, line 112, in connect self.connection = self.get_new_connection(conn_params) File /usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py, line 116, in get_new_connection return Database.connect(**conn_params) File /usr/lib/python2.7/dist-packages/psycopg2/__init__.py, line 179, in connect connection_factory=connection_factory, async=async) django.db.utils.OperationalError: FATAL: password authentication failed for user maas FATAL: password authentication failed for user maas dpkg:
[Bug 1266840] Re: maas-dns failed to install completely on Trusty
Looked into syslog when manually restarting bind9 and it seems to hang on the maas zone file: Jan 7 11:28:16 critical-maas named[29464]: starting BIND 9.9.3-rpz2+rl.13214.22-P2-Ubuntu-1:9.9.3.dfsg.P2-4ubuntu2 -u bind Jan 7 11:28:16 critical-maas named[29464]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--with-atf=no' '--enable-ipv6' '--enable-filter-' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' Jan 7 11:28:16 critical-maas named[29464]: Jan 7 11:28:16 critical-maas named[29464]: BIND 9 is maintained by Internet Systems Consortium, Jan 7 11:28:16 critical-maas named[29464]: Inc. (ISC), a non-profit 501(c)(3) public-benefit Jan 7 11:28:16 critical-maas named[29464]: corporation. Support and training for BIND 9 are Jan 7 11:28:16 critical-maas named[29464]: available at https://www.isc.org/support Jan 7 11:28:16 critical-maas named[29464]: Jan 7 11:28:16 critical-maas named[29464]: adjusted limit on open files from 4096 to 1048576 Jan 7 11:28:16 critical-maas named[29464]: found 4 CPUs, using 4 worker threads Jan 7 11:28:16 critical-maas named[29464]: using 4 UDP listeners per interface Jan 7 11:28:16 critical-maas named[29464]: using up to 4096 sockets Jan 7 11:28:16 critical-maas named[29464]: loading configuration from '/etc/bind/named.conf' Jan 7 11:28:16 critical-maas named[29464]: /etc/bind/named.conf.local:9: open: /etc/bind/maas/named.conf.maas: file not found Jan 7 11:28:16 critical-maas named[29464]: loading configuration: file not found Jan 7 11:28:16 critical-maas named[29464]: exiting (due to fatal error) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1266840 Title: maas-dns failed to install completely on Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1266840/+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 1266893] [NEW] unable to complete getting the ephemeral images
Public bug reported: My setup: Trusty on an IBM Thinkpad x201. Onboard Gigabit is static on 10.0.0.0 (The private MAAS lan) Internet connectivity is via an 802.11n WiFi dongle My internet connection is a 10Mbit ADSL line I have installed and configured maas. The next step, per the instructions here: maas.ubuntu.com/docs/instal.html#import-the-boot-images is this: $ maas-cli maas nde-groups import-boot-images While doing this, I observed that it first called maas-import-pxe-files which ran to completion pulling all the PXE files and putting them in /var/lib/maas/tftp/* Next, it calls maas-import-ephemerals This ran and did NOTHING. It just sat there, no network traffic in or out, no disk activity, no data written to /var/lib/maas/ephemeral. I left it sitting for over an hour and it never actually started downloading any images . I finally killed off the process and ran maas-import-ephemerals manually. This time, it did begin downloading images, converting them and copying them to /var/lib/maas/ephemerals. But then it just stopped as though it had lost the connection th wherever it's downloading from, or something. It never exited, it just ... paused and never restarted. I let THIS sit for an hour and noticed that there was absolutely NO further related network activity, disk activity or aything. So I finally killed that process off as well. Next, I tried breaking it down into smaller chunks like so: $ sudo maas-import-ephemerals release=RELEASE Doing it this way, I was able to fully download Saucy, Raring, Quantal and Precise. Currently, trying with trusty does nothing (it doesn't seem to do anything at all. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas 1.4+bzr1789+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 7 13:08:02 2014 InstallationDate: Installed on 2014-01-07 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140106) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1266893 Title: unable to complete getting the ephemeral images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1266893/+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 1266840] Re: maas-dns failed to install completely on Trusty
https://bugs.launchpad.net/maas/+bug/1035998/comments/2 Reading that comment, it suggests that the named.conf.maas file should be empty by design so I created one like so: sudo touch /etc/named/maas/named.conf.maas and restarted bind and apache. Then, I deleted my node and retried and it successfully commissioned and declared. From there, I was able to access it via the UI and click Commission Node and the node turned on and successfully booted the commissioning image. (It was failing before because DNS was never started, causing the commissioning image to hang) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1266840 Title: maas-dns failed to install completely on Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1266840/+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 1268713] [NEW] import-boot-images doesn't seem to do anything on latest trusty builds
Public bug reported: Following the docs, I did the following on a system running the latest Trusty image with the latest MAAS packages for trusty: $ maas-cli maas node-groups import-boot-images On Saucy or earlier (and I believe on earlier versions of Trusty), this would launch the olders scripts maas-import-pxe-files and maas-import- ephemerals Today, it does nothing but exit. Nothign appears in the pserv log, nothing in maas.log. There is nothing I can find written anywhere that indicates this command is doing anything other than printing the message that the files will be imported and then exiting. There is no data being written to the /var/lib/maas/ dirs that hold ephemerals and PXE files and nothing appears in PS to be related to this. I finally manually ran the older commands to get the files imported. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas 1.4+bzr1789+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 13 15:06:07 2014 InstallationDate: Installed on 2014-01-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140113) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Summary changed: - import-boot-images doesn't seem to do anything + import-boot-images doesn't seem to do anything on latest trusty builds -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1268713 Title: import-boot-images doesn't seem to do anything on latest trusty builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268713/+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 1268783] [NEW] traceback in celery-region log when maas controls DNS and tries to write dns config
Public bug reported:
Using latest trusty bits I manually created a node in the MAAS UI. On
setting the node, MAAS successfully powered the node on via IPMI. The
node booted and got an IP address but then failed to PXE due to PXE
timeout errors. While all this is going on, each retry prompted a new
DHCP lease which seems to have triggered a DNS update. The celery
region log showed this each time DNS config was attempted:
[2014-01-13 18:26:20,751: INFO/MainProcess] Got task from broker:
provisioningserver.tasks.write_full_dns_config[f67e9cfd-34e5-4cf8-abf1-b01d4ea01919]
[2014-01-13 18:26:20,791: INFO/MainProcess] Task
provisioningserver.tasks.write_full_dns_config[f67e9cfd-34e5-4cf8-abf1-b01d4ea01919]
succeeded in 0.0343019962311s: None
[2014-01-13 18:26:20,797: INFO/MainProcess] Got task from broker:
provisioningserver.tasks.rndc_command[0f41c14f-5d56-4811-9743-359451260a06]
[2014-01-13 18:26:20,834: ERROR/MainProcess] Task
provisioningserver.tasks.rndc_command[0f41c14f-5d56-4811-9743-359451260a06]
raised exception: UnpickleableExceptionWrapper('provisioningserver.utils',
'ExternalProcessError', (), 'ExternalProcessError()')
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/celery/execute/trace.py, line 181, in
trace_task
R = retval = fun(*args, **kwargs)
File /usr/lib/python2.7/dist-packages/provisioningserver/tasks.py, line
186, in rndc_command
execute_rndc_command(arguments)
File /usr/lib/python2.7/dist-packages/provisioningserver/dns/config.py,
line 152, in execute_rndc_command
call_and_check(rndc_cmd, stdout=devnull)
File /usr/lib/python2.7/dist-packages/provisioningserver/utils.py, line
119, in call_and_check
return subprocess.check_call(command, *args, **kwargs)
File /usr/lib/python2.7/subprocess.py, line 540, in check_call
raise CalledProcessError(retcode, cmd)
ExternalProcessError: ExternalProcessError()
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: maas 1.4+bzr1789+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
Uname: Linux 3.13.0-2-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jan 13 18:35:55 2014
InstallationDate: Installed on 2014-01-13 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140113)
PackageArchitecture: all
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1268783
Title:
traceback in celery-region log when maas controls DNS and tries to
write dns config
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268783/+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 1268795] [NEW] unable to automatically commission Cisco UCS server due to BMC user permissions
Public bug reported: I have connected a Cisco UCS C220 M3 system to my MAAS server. I have tried and succeeded in enlisting the server both automatically by powering the server on manually, and via the UI by feeding maas the server CIMC information and have MAAS automatically power the server on via IPMI and enlist. BUT once I get to a declared system, I am unable to commission it via the UI. When the system is enlisted, MAAS appears to create a maas user in slot 10 of the CIMC user table. BUT rather than making this user a User or Admin, it is set to Read Only Because of this, the maas user in the CIMC does not have permission to power the server up or down and thus can't commission. If I manually power the server on, it then PXE bootes the commissioning image, does it's stuff and then shuts down. At this point, the server is indeed marked as Ready and can be used in the MAAS cluster. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas 1.4+bzr1789+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 13 19:25:55 2014 InstallationDate: Installed on 2014-01-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140113) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1268795 Title: unable to automatically commission Cisco UCS server due to BMC user permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268795/+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 1269046] [NEW] Nodes created manually and then enlisted are forgotten by MAAS
Public bug reported: On my MAAS box running trusty: In the MAAS UI, we created a node entry for a server, choosing IPMI and passing the login credentials, IP for the BMC and the MAC address. On saving the node, MAAS issued the IPMI command to turn the server on. The server successfully powered on and PXE booted the enlistment image. Once enlistment was complete, the server powered off. On refreshing the MAAS UI, however, the original node we created manually was shown still in the Commissioning state. A NEW node was also listed, showing it was in the Delcared state. What seems to have happened is that MAAS, instead of filling data for the node we created manually, just created a brand new node instead, and ignored ours. The original manual node can be safely deleted. POSSIBLE CAUSE: When we created the node originally in the UI, we passed it the MAC address for the BMC port. The newly created node, however, lists the MAC addresses for all onboard ethernet ports, NOT the management port. If the MAC address part of the Add Node page means MAC for the ethernet device that PXE boots, the page is misleading and needs to be corrected. As it stands, I thought that MAC entry was supposed to be for the BMC MAC address. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas 1.4+bzr1789+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 14 10:51:05 2014 InstallationDate: Installed on 2014-01-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140113) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1269046 Title: Nodes created manually and then enlisted are forgotten by MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1269046/+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 1268795] Re: unable to automatically commission Cisco UCS server due to BMC user permissions
Yep, that was the workaround I used. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1268795 Title: unable to automatically commission Cisco UCS server due to BMC user permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268795/+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 1270165] [NEW] Stop action does not power systems down
Public bug reported: I had three servers connected to my MAAS server. All three were successfully enlisted, commissioned and in the Ready state. I did a juju bootstrap which grabbed one server, powered it on and installed and completed Juju's bootstrap bringup. This was confirmed by running juju status. I next wanted to confirm I could install a system directly from MAAS by simply issuing the Start node action. So I selected one free node and clicked the Start node button in the nodes details page. This turned the node on, and it did indeed install the prescribed OS version. Now, I wanted to release those for use elsewhere, so in the Nodes page, I selected my juju bootstrap node and my recently installed generic node (both in the Alloctated to ubuntu state, ubuntu is the username) and then in the Bulk Actions dropdown selected Stop selected nodes and clicked the Go button. At this point, the MAAS UI refreshed and showed the systems back in the Ready unallocated state, indicating that I could proceed to re-enlist them. However, neither of the nodes actually powered off. This means I will be unable to re-use those nodes without manually powering them off. To check this, I left them in their Powered On but Ready in MAAS state and attempted to Start one wiht a different Ubuntu version chosen for it. As predicted, the node did not reboot, reset or anything, meaning it was still running in it's previous state, regardless of what MAAS or I wanted it to do. I had to manually reset teh system to get it to come back up and PXE boot the new OS from MAAS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas 1.4+bzr1817+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 16 09:49:57 2014 InstallationDate: Installed on 2014-01-13 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140113) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1270165 Title: Stop action does not power systems down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1270165/+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 110992] Re: ipmi modules need to manually inserted and device created
Why is this still even an issue? Verified that on the latest Lucid SRU, ipmi_si and ipmi_msghandler load at boot but ipmi_devintf does not. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/110992 Title: ipmi modules need to manually inserted and device created -- 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 110992] Re: ipmi modules need to manually inserted and device created
Ok... so further investigation: Fresh Natty install on an IBM server with BMC using the latest ISOs as of 8 March. Looking in /lib/modules/2.6.38-5-generic/kernel/drivers/char/ipmi/ shows that the drivers are present. No IPMI packages are installed: First I install ipmitool: ubuntu@ubuntu:~$ sudo apt-get install ipmitool Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: openipmi The following NEW packages will be installed: ipmitool 0 upgraded, 1 newly installed, 0 to remove and 13 not upgraded. Need to get 418 kB of archives. After this operation, 1,118 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu/ natty/universe ipmitool amd64 1.8.11-2ubuntu3 [418 kB] Fetched 418 kB in 0s (431 kB/s) ySelecting previously deselected package ipmitool. (Reading database ... 30797 files and directories currently installed.) Unpacking ipmitool (from .../ipmitool_1.8.11-2ubuntu3_amd64.deb) ... Processing triggers for ureadahead ... ureadahead will be reprofiled on next reboot Processing triggers for man-db ... Setting up ipmitool (1.8.11-2ubuntu3) ... ipmievd: using pidfile /var/run/ipmievd.pid0 Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory Unable to open interface invoke-rc.d: initscript ipmievd, action start failed. Unable to start ipmievd during installation. Trying to disable. Also note that installing ipmitool does not install any other packages at all. These errors happened because /dev/ipmi0 is not created... that requires ipmi_devmntf to be loaded. One would think that since I just installed ipmitool, which includes ipmievd to pass BMC messages on to syslog, that as soon as I reboot, the modules would be loaded, /dev/ipmi0 would be created and everthing would be copacetic. So after installing ipmitool and verifying that ipmievd was not running, /dev/ipmi0 was not there, and the modules were not loaded, I rebooted the server to see what would happen. ipmi modules are NOT loaded, ipmievd is not started, and /dev/ipmi0 is not created, thus, nothing. Now I install the openipmi package (which is NOT pulled in by installing ipmitool): ubuntu@ubuntu:~$ sudo apt-get install openipmi Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libopenipmi0 libperl5.10 libsensors4 libsnmp-base libsnmp15 Suggested packages: lm-sensors snmp-mibs-downloader The following NEW packages will be installed: libopenipmi0 libperl5.10 libsensors4 libsnmp-base libsnmp15 openipmi 0 upgraded, 6 newly installed, 0 to remove and 13 not upgraded. Need to get 2,288 kB of archives. After this operation, 6,595 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://10.189.84.1/enablement/cdimage.ubuntu.com/ubuntu-server/daily/current/natty-server-amd64/ natty/main libopenipmi0 amd64 2.0.18-0ubuntu3 [559 kB] Get:2 http://10.189.84.1/enablement/cdimage.ubuntu.com/ubuntu-server/daily/current/natty-server-amd64/ natty/main libperl5.10 amd64 5.10.1-17ubuntu3 [1,200 B] Get:3 http://10.189.84.1/enablement/cdimage.ubuntu.com/ubuntu-server/daily/current/natty-server-amd64/ natty/main libsensors4 amd64 1:3.2.0-1 [32.8 kB] Get:4 http://10.189.84.1/enablement/cdimage.ubuntu.com/ubuntu-server/daily/current/natty-server-amd64/ natty/main libsnmp-base all 5.4.3~dfsg-2ubuntu1 [214 kB] Get:5 http://10.189.84.1/enablement/cdimage.ubuntu.com/ubuntu-server/daily/current/natty-server-amd64/ natty/main libsnmp15 amd64 5.4.3~dfsg-2ubuntu1 [1,336 kB] Get:6 http://10.189.84.1/enablement/cdimage.ubuntu.com/ubuntu-server/daily/current/natty-server-amd64/ natty/main openipmi amd64 2.0.18-0ubuntu3 [146 kB] Fetched 2,288 kB in 0s (26.5 MB/s) Selecting previously deselected package libopenipmi0. (Reading database ... 30810 files and directories currently installed.) Unpacking libopenipmi0 (from .../libopenipmi0_2.0.18-0ubuntu3_amd64.deb) ... Selecting previously deselected package libperl5.10. Unpacking libperl5.10 (from .../libperl5.10_5.10.1-17ubuntu3_amd64.deb) ... Selecting previously deselected package libsensors4. Unpacking libsensors4 (from .../libsensors4_1%3a3.2.0-1_amd64.deb) ... Selecting previously deselected package libsnmp-base. Unpacking libsnmp-base (from .../libsnmp-base_5.4.3~dfsg-2ubuntu1_all.deb) ... Selecting previously deselected package libsnmp15. Unpacking libsnmp15 (from .../libsnmp15_5.4.3~dfsg-2ubuntu1_amd64.deb) ... Selecting previously deselected package openipmi. Unpacking openipmi (from .../openipmi_2.0.18-0ubuntu3_amd64.deb) ... Processing triggers for man-db ... Processing triggers for ureadahead ... ureadahead will be reprofiled on next reboot Setting up libopenipmi0 (2.0.18-0ubuntu3) ... Setting up libperl5.10 (5.10.1-17ubuntu3) ... Setting up libsensors4 (1:3.2.0-1) ... Setting up libsnmp-base (5.4.3~dfsg-2ubuntu1) ... Setting up libsnmp15
[Bug 110992] Re: ipmi modules need to manually inserted and device created
Also, by pulling in openipmi I mean that perhaps the control file for the ipmitool package could change from suggesting openipmi to recommending openipmi -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/110992 Title: ipmi modules need to manually inserted and device created -- 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 661591] Re: checkbox threw an error during a network test
** Changed in: checkbox-certification Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in ubuntu. https://bugs.launchpad.net/bugs/661591 Title: checkbox threw an error during a network test -- 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 641657] [NEW] SSH connections freeze after a period of time
Public bug reported: Maverick with latest updates as of 17 Sept 2010 I've noticed since upgrading from 10.04.1 to Maverick that SSH sessions now seem to freeze after a period of time. I am able to ssh to a remote server (I'm sshing to my personal server and to some work servers in one of the DCs) and do things. However, after letting the connection sit idle for a bit it just freezes and I have to kill the terminal it's in, or kill the ssh process that's running. I never saw this issue until upgrading to Maverick. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: openssh-client 1:5.5p1-4ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Uname: Linux 2.6.35-20-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Sep 17 17:59:42 2010 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: openssh ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- SSH connections freeze after a period of time https://bugs.launchpad.net/bugs/641657 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 641657] Re: SSH connections freeze after a period of time
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/641657/+attachment/1599958/+files/Dependencies.txt -- SSH connections freeze after a period of time https://bugs.launchpad.net/bugs/641657 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 641657] Re: SSH connections freeze after a period of time
Hi Steve, Actually, I'm seeing it on any remote SSH connection (either to a Canonical DC or to my own shared server). I'm in Taipei at the moment so I'll try again here just to see if there's something wonky on my end (router, or switch maybe) causing the SSH connection do hang... As for the rest, I haven't done an strace on it, nor a -vv... but I'll keep that in mind too. It doesn't respond, that I know of to the escape char, but to be perfectly honest, I'm not sure I tried '~' anyway... I keep trying telnet chars by habit... so another thing to thing to try. I'm going to leave this as incomplete for the moment and I'll try to get an strace from a failing condition and try some other stuff (like from this different location) and see what happens. -- SSH connections freeze after a period of time https://bugs.launchpad.net/bugs/641657 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 661591] [NEW] checkbox threw an error during a network test
Public bug reported: Binary package hint: ntp Not sure which test... it appears to be the ntp test that caused checkbox to start a bug report. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: ntpdate 1:4.2.4p8+dfsg-1ubuntu6 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CheckboxCommand: network_ntp_test --server $NTP_SERVER CheckboxData: Usage: network_ntp_test [OPTIONS] network_ntp_test: error: --server option requires an argument CheckboxDescription: Test to see if we can sync local clock to an NTP server CheckboxTest: network_ntp_test Date: Sat Oct 16 01:09:16 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 SourcePackage: ntp ** Affects: checkbox-certification Importance: Undecided Assignee: Jeff Lane (bladernr) Status: New ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug checkbox-bug maverick -- checkbox threw an error during a network test https://bugs.launchpad.net/bugs/661591 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 661591] Re: checkbox threw an error during a network test
** Also affects: checkbox-certification Importance: Undecided Status: New ** Changed in: checkbox-certification Assignee: (unassigned) = Jeff Lane (bladernr) -- checkbox threw an error during a network test https://bugs.launchpad.net/bugs/661591 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 661591] Re: checkbox threw an error during a network test
** Changed in: ntp (Ubuntu) Status: New = Incomplete ** Changed in: ntp (Ubuntu) Status: Incomplete = Opinion ** Changed in: ntp (Ubuntu) Status: Opinion = Invalid -- checkbox threw an error during a network test https://bugs.launchpad.net/bugs/661591 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 661591] Re: checkbox threw an error during a network test
** Changed in: checkbox-certification Importance: Undecided = High -- checkbox threw an error during a network test https://bugs.launchpad.net/bugs/661591 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 661591] Re: checkbox threw an error during a network test
Job description was incorrectly calling network_ntp_test script. Fixed that. ** Changed in: checkbox-certification Status: New = Fix Committed -- checkbox threw an error during a network test https://bugs.launchpad.net/bugs/661591 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 1294332] [NEW] MAAS fails to manage power for system with Intel Integrated BMC
Public bug reported: I have a system with an intel iBMC onboard. MAAS can successfully create the maas user and add/change the password, and it also has the correct administrator priviliges. MAAS also created the user in slot 6, the first available, rather than choking on slot 4 or 10. HOWEVER, any time I try to use MAAS to actually power the machine on, I see a traceback in the celery log and the system fails to come on. I CAN, however, control the system via IPMI directly (ipmitool) to bring it up or down. MAAS sets the power for this system to IPMI 2.0 Here's the traceback from celery.log, not that it's terribly informative: [2014-03-18 15:32:34,605: ERROR/MainProcess] Task provisioningserver.tasks.power_off[868fef2b-8335-449d-a18f-8ef8307bdce2] raised unexpected: PowerActionFail() Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/celery/app/trace.py, line 218, in trace_task R = retval = fun(*args, **kwargs) File /usr/lib/python2.7/dist-packages/celery/app/trace.py, line 398, in __protected_call__ return self.run(*args, **kwargs) File /usr/lib/python2.7/dist-packages/provisioningserver/tasks.py, line 161, in power_off issue_power_action(power_type, 'off', **kwargs) File /usr/lib/python2.7/dist-packages/provisioningserver/tasks.py, line 141, in issue_power_action pa.execute(**kwargs) File /usr/lib/python2.7/dist-packages/provisioningserver/power/poweraction.py, line 132, in execute rendered = self.render_template(template, **kwargs) File /usr/lib/python2.7/dist-packages/provisioningserver/power/poweraction.py, line 107, in render_template raise PowerActionFail(self, error) PowerActionFail I also attempted to set the power type to PMI 1.5 and that too produced the same traceback and failure to power on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas 1.5+bzr1977-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 18 15:28:09 2014 InstallationDate: Installed on 2014-01-13 (64 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140113) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1294332 Title: MAAS fails to manage power for system with Intel Integrated BMC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1294332/+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 1294332] Re: MAAS fails to manage power for system with Intel Integrated BMC
I also manually tried using the ipmipower command in addition to ipmitool: ubuntu@critical-maas:~$ ipmipower -h 10.0.0.125 -u maas -p TRRnqoEl9ccQy7 --off 10.0.0.125: ok ubuntu@critical-maas:~$ ipmipower -h 10.0.0.125 -u maas -p TRRnqoEl9ccQy7 --on-if-off --cycle 10.0.0.125: ok both of these commands were successfully executed from CLI. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1294332 Title: MAAS fails to manage power for system with Intel Integrated BMC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1294332/+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 1294332] Re: MAAS fails to manage power for system with Intel Integrated BMC
Since apport didn't gather any maas logs, here they are... ** Attachment added: maas-logs.tar.gz https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1294332/+attachment/4031166/+files/maas-logs.tar.gz -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1294332 Title: MAAS fails to manage power for system with Intel Integrated BMC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1294332/+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 1304518] [NEW] Confusing wording in the IPMI section of node power data
Public bug reported: New to the power management part of node info is this text: MAC address - the IP is looked up with ARP and is used if IP address is empty. This is better when the BMC uses DHCP. What is better when the BMC uses DHCP? Does using DHCP make using ARP better? or more accurate? I can't really seem to grok what this explanation of MAC Address actually means. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas 1.5+bzr2227-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Tue Apr 8 12:09:59 2014 InstallationDate: Installed on 2014-01-13 (84 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140113) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1304518 Title: Confusing wording in the IPMI section of node power data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1304518/+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 1304613] [NEW] nodes can't get out to the internet beyond the maas server by default
Public bug reported: by default, there's no way for a node started by maas to talk to the internet. There is also no way on the maas dashboard that I can see that allows me to control this sort of network behaviour either. For now, we are using a shell script to start NAT rules in iptables so that a node can actually talk to the internet. Scenario one: node commissioned and started, uses d-i to do a basic install. This works fine however, if you have the pressed do something like add a PPA for some different packages during late_command, you can never complete installation because add-apt-repository can't talk to the outside. And if you add the repo manually, I do not believe you can actually pull the packages from ppa.launchpad.net. Scenario two: node commissioned and started, using fast-path install. After fast-path is done and note reboots, you ssh into the node and want to add the PPA manually and install packages. This is impossible because again, add-apt-repository fails to get stuff from launchpad.net. Solution to both, for now, is to set up NAT with the following rules: echo 1 /proc/sys/net/ipv4/ip_forward /sbin/iptables -t nat -A POSTROUTING -o $EXTERNAL -j MASQUERADE /sbin/iptables -A FORWARD -i $EXTERNAL -o $INTERNAL -m state --state RELATED,ESTABLISHED -j ACCEPT /sbin/iptables -A FORWARD -i $INTERNAL -o $EXTERNAL -j ACCEPT ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas 1.5+bzr2227-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Tue Apr 8 15:11:12 2014 InstallationDate: Installed on 2014-01-13 (85 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140113) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1304613 Title: nodes can't get out to the internet beyond the maas server by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1304613/+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 1309761] [NEW] MAAS installing older 14.04 image instead of newer one
Public bug reported: I have a NUC with the current version of 14.04 and MAAS installed on it. Today, I completely removed the contents of boot-resources and re- imported the various boot/image files to remove old daily images and older versions I didn't need. If you look at the current image streams dir at maas-images.ubuntu.com, you'll see that there are actually two image versions for trusty: Index of /images/ephemeral-v2/releases/trusty/amd64 NameLast modified SizeDescription Parent Directory - 20140410/ 10-Apr-2014 22:22- 20140416.1/ 17-Apr-2014 18:22- di/ 17-Apr-2014 18:22- The older 0410 image is the RC image and the newer 0416.1 image is the release version of 14.04. Because of this, the current snapshot has both images available: ubuntu@critical-maas:/var/lib/maas/boot-resources/current/amd64/generic/trusty$ ls -l * rc: total 1812444 -rw-r--r-- 2 root root 24654011 Apr 18 12:57 boot-initrd -rw-r--r-- 2 root root5774304 Apr 18 12:57 boot-kernel -rw-r--r-- 2 root root 21256334 Apr 18 12:58 di-initrd -rw-r--r-- 2 root root5776216 Apr 18 12:57 di-kernel -rw-r--r-- 2 root root 1476395008 Apr 18 12:56 root-image -rw-r--r-- 2 root root 322069555 Apr 18 12:57 root-tgz release: total 1812428 -rw-r--r-- 2 root root 24663072 Apr 18 12:50 boot-initrd -rw-r--r-- 2 root root5777056 Apr 18 12:49 boot-kernel -rw-r--r-- 2 root root 21256771 Apr 18 12:50 di-initrd -rw-r--r-- 2 root root5778968 Apr 18 12:50 di-kernel -rw-r--r-- 2 root root 1476395008 Apr 18 12:49 root-image -rw-r--r-- 2 root root 322042698 Apr 18 12:49 root-tgz And MAAS shows both the RC and Release images available as bootable for Trusty (**See attached screen shot**) However, in the MAAS ui, the ONLY option for setting the installation image is Trusty there is no setting for choosing between RC and Release images for Trusty. And MAAS is choosing to install the older version when booting. I noticed quickly during boot that my node is getting the rc image via iscsi... but have no way of capturing that other than maybe a crappy cell phone image..., so the following will have to suffice: Installing using the fast path, MAAS is choosing the older 0410 RC images over the 0416.1 Release images, and we get a system installed with the Development version of Trusty instead, as bore out by the kernel version and /etc/lsb-release. Here's some data from a node installed via FastPath: ubuntu@supermicro:~$ uname -a Linux supermicro 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@supermicro:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION=Ubuntu Trusty Tahr (development branch) This is immediately following a fast-path install of Trusty. I'm now trying to do a d-i install, which worked before I deleted and re-imported but that is now failing with the No kernel modules found message and looking at alternate consoles, that too appears to be the 3.13.0-23 boot image, not the 3.13.0-24 image... so that could be the issue there... not sure though. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: maas 1.5+bzr2252-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Fri Apr 18 16:58:55 2014 InstallationDate: Installed on 2014-01-13 (95 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140113) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: maas-re-import.png https://bugs.launchpad.net/bugs/1309761/+attachment/4088105/+files/maas-re-import.png -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1309761 Title: MAAS installing older 14.04 image instead of newer one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1309761/+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 1309761] Re: MAAS installing older 14.04 image instead of newer one
I went through and deleted the rc directory from *current, and also deleted the individual images themselves (had to compare inode numbers in rc/ to the images in cache and deleted the images individually by inode. Then I did an install and it installed the correct image by default: ubuntu@supermicro:~$ uname -a Linux supermicro 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@supermicro:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1309761 Title: MAAS installing older 14.04 image instead of newer one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1309761/+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 1309761] Re: MAAS installing older 14.04 image instead of newer one
So it would seem to confirm that MAAS is choosing the older 20140410 images over the 20140416.1 images when installing. This is my bootresources.yaml: (The only changes I made were commenting out older versions I didn't want to pull down) ubuntu@critical-maas:/var/lib/maas/boot-resources$ cat /etc/maas/bootresources.yaml ## ## Boot image download configuration. ## # # Items in this configuration: # # boot - the root for these settings. # # storage - location on the filesystem where boot images are stored. # # These images can get quite large: some files are hundreds of megabytes, # and you may need multiple copies for different architectures, OS releases, # etc. # # sources - one or more sources of downloadable boot images. # # Each source downloads from one simplestreams URL, though it is possible to # have multiple sources using the same URL. # # path - for each source, the path to its (online) Simplestreams data. # # keyring - for each source, a GPG keyring to verify images' signatures. # # selections - for each source, one or more sets of constraints for images. # # From each source, only those images are imported which match at least one of # the source's selections. A selection can specify an OS release, a CPU # architecture, and so on. # # Be careful: the items in a selection will multiply. For example if you # specify architectures i386 and amd64, and subarchitectures generic, # hwe-s, and hwe-t, the import script will need to import 6 images, for # each possible combination. If you only want some of those combinations, # keep them as separate sources and/or selections. boot: sources: - keyring: /usr/share/keyrings/ubuntu-cloudimage-keyring.gpg path: http://maas.ubuntu.com/images/ephemeral-v2/releases/ selections: #- arches: # - amd64 # release: lucid # subarches: # - generic #- arches: # - amd64 # release: precise # subarches: # - generic #- arches: # - amd64 # release: quantal # subarches: # - generic #- arches: # - amd64 # release: raring # subarches: # - generic - arches: - amd64 release: saucy subarches: - generic - arches: - amd64 release: trusty subarches: - generic #- arches: # - armhf # release: precise # subarches: # - generic #- arches: # - armhf # release: quantal # subarches: # - generic #- arches: # - armhf # release: raring # subarches: # - generic #- arches: # - armhf # release: saucy # subarches: # - generic #- arches: # - armhf # release: trusty # subarches: # - generic #- arches: # - armhf # release: precise # subarches: # - highbank #- arches: # - armhf # release: quantal # subarches: # - highbank #- arches: # - armhf # release: raring # subarches: # - highbank #- arches: # - armhf # release: trusty # subarches: # - highbank #- arches: # - i386 # release: lucid # subarches: # - generic #- arches: # - i386 # release: precise # subarches: # - generic #- arches: # - i386 # release: quantal # subarches: # - generic #- arches: # - i386 # release: raring # subarches: # - generic - arches: - i386 release: saucy subarches: - generic - arches: - i386 release: trusty subarches: - generic storage: /var/lib/maas/boot-resources/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1309761 Title: MAAS installing older 14.04 image instead of newer one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1309761/+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 1304518] Re: Confusing wording in the IPMI section of node power data
Julian: THAT makes more sense... perhaps this would be less confusing, from a user standpoint: MAC Address - Enter the BMC's MAC Address here if you are NOT using DHCP to assign BMC IP Addresses ** Changed in: maas Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1304518 Title: Confusing wording in the IPMI section of node power data To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1304518/+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 1304613] Re: nodes can't get out to the internet beyond the maas server by default
Hi Julian, I've got several MAAS servers that seem to suffer the same fate, depending on what your definition of Access the internet is. We first saw this at the Orange Box sprint in london where nodes could be deployed via d-i which was pulling packages from MAAS's squid-deb- proxy, IIRC, however they couldn't pull packages afterwards from ppa.launchpad.net or the internet in general (e.g. I couldn't ssh to a node and they wget a file from somewhere else). A good example of this was when we tried usign juju to deploy certain charms that pull from places like github, the charms would fail because those sites were unreachable from the node itself (but not from the MAAS Server). So we configured NAT to allow the nodes to pass through to the internet to reach anywhere. In our immediate case with certification, we have several NUCs that are configured as MAAS servers for deploying both the OS and certification tools. So here is IP Tables after a fresh reboot of my NUC running the latest 14.04 MAAS: ubuntu@critical-maas:~$ sudo iptables -L [sudo] password for ubuntu: Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination ubuntu@critical-maas:~$ sudo iptables -L -t nat Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain INPUT (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination ubuntu@critical-maas:~$ ubuntu@critical-maas:~$ COLUMNS=150 dpkg -l |grep maas ii maas1.5+bzr2252-0ubuntu1 all MAAS server all-in-one metapackage ii maas-cli1.5+bzr2252-0ubuntu1 all MAAS command line API tool ii maas-cluster-controller 1.5+bzr2252-0ubuntu1 all MAAS server cluster controller ii maas-common 1.5+bzr2252-0ubuntu1 all MAAS server common files ii maas-dhcp 1.5+bzr2252-0ubuntu1 all MAAS DHCP server ii maas-dns1.5+bzr2252-0ubuntu1 all MAAS DNS server ii maas-region-controller 1.5+bzr2252-0ubuntu1 all MAAS server complete region controller ii maas-region-controller-min 1.5+bzr2252-0ubuntu1 all MAAS Server minimum region controller ii maas-test 0.1+bzr147+150+10~pp all Utility to test hardware compatibility with MAAS ii python-django-maas 1.5+bzr2252-0ubuntu1 all MAAS server Django web framework ii python-maas-client 1.5+bzr2252-0ubuntu1 all MAAS python API client ii python-maas-provisioningserver 1.5+bzr2252-0ubuntu1 all MAAS server provisioning libraries Now I have the server installed and try a couple things to see if my node can talk to the internet: ubuntu@supermicro:~$ host ubuntu.com ubuntu.com has address 91.189.94.156 ubuntu.com mail is handled by 10 mx.canonical.com. ubuntu@supermicro:~$ sudo ping -c 10 www.ubuntu.com PING www.ubuntu.com (91.189.89.103) 56(84) bytes of data. --- www.ubuntu.com ping statistics --- 10 packets transmitted, 0 received, 100% packet loss, time 9071ms I am able to install something: ubuntu@supermicro:~$ sudo apt-get install ksh Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: ksh 0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded. Need to get 1,583 kB of archives. After this operation, 3,229 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com//ubuntu/ trusty/universe ksh amd64 93u+20120801-1 [1,583 kB] Fetched 1,583 kB in 7s (223 kB/s) Selecting previously unselected package ksh. (Reading database ... 69996 files and directories currently installed.) Preparing to unpack .../ksh_93u+20120801-1_amd64.deb ... Unpacking ksh (93u+20120801-1) ... Processing triggers for man-db (2.6.7.1-1) ... Setting up ksh (93u+20120801-1) ... update-alternatives: using /bin/ksh93 to provide /bin/ksh (ksh) in auto mode but is that going through the squid deb proxy? Because I am unable to manually touch archive.ubuntu.com: --2014-04-22 18:38:29-- http://archive.ubuntu.com/ubuntu/pool/universe/k/ksh/ksh_93u+20120801-1_amd64.deb Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.92.200, 91.189.91.13, 91.189.91.14, ... Connecting to archive.ubuntu.com
[Bug 1304613] Re: nodes can't get out to the internet beyond the maas server by default
Then again, perhaps something as simple as a 'maas-enable-nat' command for these simple cases would be sufficient so new users don't have to also understand iptables... and makes it optional on the maas server so you can or can not enable it... maybe it is a per-cluster-controller thing, as my understanding is that the region controller just handles certain things whie the clusters do the bulk of the work for the nodes... I dont have the hardware really to set up a different cluster controller... for now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1304613 Title: nodes can't get out to the internet beyond the maas server by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1304613/+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 1304613] Re: nodes can't get out to the internet beyond the maas server by default
As for your question about the region... I don't know... that's operating at scale. The question there is probably one of hierarchy... for example, would you have multiple, linked region controllers, or more like a few region controllers and several cluster controllers under each? And in that case, perhaps you'd want to be able to arbitrarily set this assuming each region and cluster controller is a physical machine: Region1 -- Dashboard -- cluster 1 |-- cluster 2 |-- cluster 3 |-- cluster 4 |---node 1 |---node 2 |---node X So perhaps you would want to be able to, via the dashboard, or some other means say, Cluster 1 shoud be segregated and never pass packets out, but cluster 4 are all web-servers and associated servers and DO need to be able to send and recieve from the internet and cluster 3 contains the things teh web servers need on the back end (SQL, etc) so Cluster 3 should only talk to cluster 4 and NEVER talk to the internet. Or I don't know, that's really a VERY ugly example. My original point was just that, by default on my very simple use case (and also as seen with the Orange Boxes), the deployed nodes can't talk to the internet without some manual futzing behind the scenes, and there's no simple way to fix that if you don't know iptables scripting and what bits to flip. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1304613 Title: nodes can't get out to the internet beyond the maas server by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1304613/+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 1304518] Re: Confusing wording in the IPMI section of node power data
Yeah, that could work. ** Changed in: maas Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1304518 Title: Confusing wording in the IPMI section of node power data To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1304518/+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 1359409] Re: ipmi-locate only works on ia64
FWIW, this does not seem to be universal to UEFI systems. I've performed enlistment and commissioning on several IBM systems in full UEFI mode that behaved just fine (and a couple new density systems that showed the same sort of issue Narninder mentions here). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1359409 Title: ipmi-locate only works on ia64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1359409/+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 1274527] Re: MAAS doesn't put its DNS server in resolv.conf
Additionally, do we not also use juju, region and cluster on the same NUC inside the Orange Box? So it seems like it would be important from the OB perspective to fix this as well. Just an additional use case. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1274527 Title: MAAS doesn't put its DNS server in resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1274527/+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 1274527] Re: MAAS doesn't put its DNS server in resolv.conf
Hrmmm... it just bit me while trying to test out the checkbox charm on bare metal from my private maas server. and it's not just a matter of juju. for example, MAAS is successfully updating the zone files: npdxh IN CNAME 10-0-0-123 and I can't ssh to my node by hostname: ubuntu@critical-maas:/etc/bind/maas$ ssh npdxh ssh: Could not resolve hostname npdxh: Name or service not known so I have to know the IP address. The NODE, does at least resolve DNS on the MAAS network properly: ubuntu@npdxh:~$ host npdxh npdxh.master is an alias for 10-0-0-123.master. 10-0-0-123.master has address 10.0.0.123 And I'm sure we all already know that much. IN any case, this is an annoyance, it's fixable, but really, the MAAS region controller (and cluster in this case since they're all one system for me) should be able to resolve its own DNS entries. From a more important use case, for certification purposes, if I am going to get testers to use juju and the checkbox charms for testing, I can not also require them to provide separate systems to serve as region or cluster or juju systems just for DNS resolution to work. Nor does it look good to tell engineers at partner sites to manually work around this. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1274527 Title: MAAS doesn't put its DNS server in resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1274527/+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 1274527] Re: MAAS doesn't put its DNS server in resolv.conf
Maybe I misunderstand the region controller concept or my understanding of the MAAS ecosystem is outdated. AIUI there is a region controller that communicates with multiple cluster controllers that further manage multiple nodes: /-- cluster foo - node1.foo, node2.foo, node3.foo ... nodeX.foo / region -- cluster bar - node1.bar, node2.bar, node3.bar ... nodeX.bar \ \-- cluster baz - node1.baz, node2.baz, node3.baz, ... nodeX.baz Is that incorrect? That's what I meant when I said region controller my point was just in agreement that whatever entity controls DNS for the MAAS environment should be aware and able to resolve it's own DNS within the MAAS environment. Part of my confusion is that I lack the hardware to do a config where I install maas-region-controller on one machine and maas-cluster- controller on another and then add nodes to see where things fall. It's a very complex system and there are gaps in my view of how it all plays together. Additionally this DID create an issue with juju as I did a juju bootstrap on my only maas server to bootstrap my only node. Node booted and deployed and bootstrapped BUT when I attempted a 'juju ssh 0' to ssh to the bootstrap node, that failed because juju was trying to access the FQDN of node0, NOT it's IP address. So even though MAAS set the FQDN of the node (supermicro.master in this case) the inability to resolve those names inside the MAAS environment caused juju to be unable to contact those nodes/units. This was easily resolved by editing /etc/resolv.conf on my MAAS server (it contains everything, maas-region-controller, maas-cluster-controller and ALL dependencies and ancillary packages/services AND all the juju stuff as well) and making sure my MAAS server could use it's own instance of bind for DNS resolution. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1274527 Title: MAAS doesn't put its DNS server in resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1274527/+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 1257186] Re: memory leakage messages (no talloc stackframe)
Just adding more griping :) would be nice to see this fixed in Trusty sometime before next February bladernr@klaatu:~$ ftp transit Connected to transit.lanes. 220 (vsFTPd 3.0.2) Name (transit:bladernr): bladernr 331 Please specify the password. Password: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Login failed. Remote system type is Login. -- 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/1257186 Title: memory leakage messages (no talloc stackframe) To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+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 1274527] Re: MAAS doesn't put its DNS server in resolv.conf
So this bit us again when trying to deploy LDS. The process there is: Install/configure MAAs Populate MAAS on MAAS, install juju Juju bootstrap juju-deployer install LDS then go to LDS and it does more stuff. In this case it really caused pain in several cases where juju would say bootstrap failed (because it was unable to resolve a node name, since juju bootstrap checks the node hostname rather than the node IP) even though bootstrap was successful. I'm sure we probably retried bootstrap at least 2 - 3 times thinking it had failed when in reality all that had happened was DNS issues causing the health check to fail. Also, when trying to deploy stuff to 74 nodes, not being able to access the node via hostname from the maas server REALLY SUCKED. It is a pain to have to click through system pages to find an IP address because you're unable to ssh node-host-name.maas from MAAS. It's not a trivial solution, Julian points that out well, but it IS one that makes debugging and sometimes deployments more painful than they should be, especially when you're using more than a handful of nodes. That said, I understand that MAAS is designed to be run distributed across several bits at scale, but we're taking about DNS. Perhaps DNS should be controlled at the region controller level then (If it's not already, I confess that I don't know where in the stack bind sits in relation to region-controller, cluster-controller, haproxy, PostgreSQL and so forth), with each cluster controller updating the region DNS data, and every cluster passing the region controller as the DNS server to all nodes as well as using the region controller as the cluster's primary DNS. Or at least something like that. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1274527 Title: MAAS doesn't put its DNS server in resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1274527/+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 181636] firefox crashes when loading groups.google.com
Public bug reported: Binary package hint: firefox Firefox 2.0.0.11 running on Ubuntu Gutsy (7.10) 32bit. Every time I attempt to load http://groups.google.com Mozilla crashes. I think the problem may be one of the applets loading on the groups.google page, but I never really get a chance to see for sure. In any case, EVERY single attempt to load that page results in failure and Firefox dying. I tried on a different machine running RHEL 5 and Firefox 2.0.0.7 and that loads it just fine. I then updated 2.0.0.7 on that box to 2.0.0.11 and restarted firefox. That worked as well on that machine. So I dont know what the deal is, but on my Ubuntu machine, I can not load the page without FF crashing... :( ProblemType: Bug Architecture: i386 Date: Wed Jan 9 18:09:06 2008 DistroRelease: Ubuntu 7.10 NonfreeKernelModules: ath_hal Package: firefox 2.0.0.11+2nobinonly-0ubuntu0.7.10 PackageArchitecture: i386 SourcePackage: firefox Uname: Linux Rogue 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- firefox crashes when loading groups.google.com https://bugs.launchpad.net/bugs/181636 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 181636] Re: firefox crashes when loading groups.google.com
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/11236312/Dependencies.txt ** Attachment added: ExtensionSummary.txt http://launchpadlibrarian.net/11236313/ExtensionSummary.txt ** Attachment added: pluginreg.dat.txt http://launchpadlibrarian.net/11236314/pluginreg.dat.txt ** Attachment added: profiles.ini.txt http://launchpadlibrarian.net/11236315/profiles.ini.txt -- firefox crashes when loading groups.google.com https://bugs.launchpad.net/bugs/181636 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 862446] Re: Upgrade from Natty to Oneiric deleted my custom launchers
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/862446 Title: Upgrade from Natty to Oneiric deleted my custom launchers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/862446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 862446] Re: Upgrade from Natty to Oneiric deleted my custom launchers
I should add that I am afraid to update my primary system now because I have far more customizations on that system than I do on this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/862446 Title: Upgrade from Natty to Oneiric deleted my custom launchers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/862446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 862446] [NEW] Upgrade from Natty to Oneiric deleted my custom launchers
Public bug reported: I just upgraded my travel laptop from Natty w/ Unity to Oneiric and I am right disappointed, sadly. This system is one I use for travel to various offices as well as events like Sprints and UDS. After installing Natty, I had removed most of the default launchers because I don't use them. I had created launchers in the dock for Thunderbird, Chrome, Mumble and a few other very commonly used apps for me. After updating to Oneiric, the panel has been reset to the Oneiric default, and all my launchers are gone. So I must now recreate all the launchers I had created in Natty. This is one of those things I should not have to do. Some changes I expect between Natty and Oneiric, but changing something like the launchers in the dock I did NOT expect to happen. Then again, this is the second time I've upgraded from one release to the next and had to re-create custom settings. In Maverick - Natty upgrade, I lost my custom colors, font sizes and other display options. Now in Natty - Oneiric, I've lost my custom background, lost my custom launchers and so on. Upgrading to Oneiric should NOT destroy customizations like that. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.18.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,vpswitch,move,resize,regex,mousepoll,grid,place,session,gnomecompat,animation,snap,wall,imgpng,unitymtgrabhandles,workarounds,fade,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Thu Sep 29 10:25:51 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:215a] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110915.1) MachineType: LENOVO 3626R3U ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=4757e1d7-4888-4a33-bfbe-8ec8fd9d19bc ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET46WW (1.16 ) dmi.board.name: 3626R3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET46WW(1.16):bd06/07/2010:svnLENOVO:pn3626R3U:pvrThinkPadX201:rvnLENOVO:rn3626R3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3626R3U dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 oneiric running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/862446 Title: Upgrade from Natty to Oneiric deleted my custom launchers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/862446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 862813] [NEW] Power Managment settings are being ignored
Public bug reported: My current power settings are as follows: On Battery: Suspend when inactive for 30 minutes; Suspend when lid is closed When Plugged In: Dont suspend when inactive; dont suspend when lid is closed However, even though my Thinkpad x201 is plugged in, the settings are being ignored and the system is suspending the system after periods of inactivity. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-power-manager 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Thu Sep 29 17:33:26 2011 GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GnomeSessionSuspendInhibited: Unknown InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110915.1) MachineType: LENOVO 3626R3U ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=4757e1d7-4888-4a33-bfbe-8ec8fd9d19bc ro quiet splash vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET46WW (1.16 ) dmi.board.name: 3626R3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET46WW(1.16):bd06/07/2010:svnLENOVO:pn3626R3U:pvrThinkPadX201:rvnLENOVO:rn3626R3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3626R3U dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO gnome-power-bugreport: Error: [Errno 2] No such file or directory ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/862813 Title: Power Managment settings are being ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/862813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 862813] Re: Power Managment settings are being ignored
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/862813 Title: Power Managment settings are being ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/862813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 862813] Re: Power Managment settings are being ignored
I should add that this is a regression from Natty. I just upgraded this machine from Natty to Oneiric this morning, and this problem has only occurred since then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/862813 Title: Power Managment settings are being ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/862813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 862813] Re: Power Managment settings are being ignored
Started to mark this as High, because it's a regression and pretty annoying, however, I'll leave that to someone else to decide ultimately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/862813 Title: Power Managment settings are being ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/862813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 852159] Re: [Thinkpad x201] Regression - Wireless networking doesn't work in Oneiric, but does in Natty
Mathieu: Yes, I just did an update on the x201 and rebooted and now NM connects properly. So whatever was done resolved the issue for me. ** Changed in: network-manager (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/852159 Title: [Thinkpad x201] Regression - Wireless networking doesn't work in Oneiric, but does in Natty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/852159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 852159] Re: [Thinkpad x201] Regression - Wireless networking doesn't work in Oneiric, but does in Natty
I'll leave it to you guys to close this if you wish... I feel a bit slimy marking my own bugs invalid (unless they were never really bugs to begin with)... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/852159 Title: [Thinkpad x201] Regression - Wireless networking doesn't work in Oneiric, but does in Natty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/852159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855689] Re: Checkbox references pre-Unity UI
Targeting to 0.12.8 for now, however as this requires a lot of exceptions, we may have to let this slide until after Oneiric. ** Changed in: checkbox (Ubuntu) Status: New = Confirmed ** Also affects: checkbox Importance: Undecided Status: New ** Changed in: checkbox Status: New = Confirmed ** Changed in: checkbox (Ubuntu) Status: Confirmed = Triaged ** Changed in: checkbox (Ubuntu) Status: Triaged = Confirmed ** Changed in: checkbox Status: Confirmed = Triaged ** Changed in: checkbox Importance: Undecided = Medium ** Changed in: checkbox Milestone: None = 0.12.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855689 Title: Checkbox references pre-Unity UI To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox/+bug/855689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855689] Re: Checkbox references pre-Unity UI
*** This bug is a duplicate of bug 823370 *** https://bugs.launchpad.net/bugs/823370 works for me, I thought that may be the case :) ** This bug has been marked a duplicate of bug 823370 [SD/MMC/MSP/*] Test descriptions need to be updated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855689 Title: Checkbox references pre-Unity UI To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox/+bug/855689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773558] Re: [ThinkPad T420] Wireless hotkey does not turn BlueTooth back on
Chris, I'm dumping this on you :) I think we can just close this as it appears to be a feature rather than a bug. Confusing by design, I'd say... In any case, I thought I'd leave the final call to you as to whether you want to close this or not. ** Changed in: linux (Ubuntu) Assignee: Jeff Lane (bladernr) = Chris Van Hoof (vanhoof) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773558 Title: [ThinkPad T420] Wireless hotkey does not turn BlueTooth back on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/773558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855689] Re: Checkbox references pre-Unity UI
*** This bug is a duplicate of bug 823370 *** https://bugs.launchpad.net/bugs/823370 And I finally found the original bug for this -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855689 Title: Checkbox references pre-Unity UI To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox/+bug/855689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 856576] Re: oneconf-query crashed with IOError in translation(): [Errno 2] No translation file found for domain: 'oneconf'
This appears to happen after installing packages. Doesn't seem to matter what package, just the act of installing a package triggers oneconf-query to crash... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/856576 Title: oneconf-query crashed with IOError in translation(): [Errno 2] No translation file found for domain: 'oneconf' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oneconf/+bug/856576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 853799] Re: remove memory test from ubuntu friendly whitelist (default)
** Changed in: ubuntu-friendly Status: New = Fix Committed ** Changed in: ubuntu-friendly Assignee: (unassigned) = Jeff Lane (bladernr) ** Changed in: ubuntu-friendly Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/853799 Title: remove memory test from ubuntu friendly whitelist (default) To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox/+bug/853799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855841] Re: [storage_devices]Bonnie++ not installed by checkbox, so test fails w/ command not found
** Changed in: checkbox Status: In Progress = Fix Released ** Changed in: checkbox (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855841 Title: [storage_devices]Bonnie++ not installed by checkbox, so test fails w/ command not found To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox/+bug/855841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 944939] Re: [Lenovo e320] Checkbox fails to detect the SD and SDHC - Manual test works fine
On 03/03/2012 01:42 PM, Brendan Donegan wrote: I'm curious to know what kind of icon displays on the launcher when the card is inserted? Is it an SD card icon or a plain old disk icon? If it's an SD card icon that would be good, as at least *someone* knows how to tell that an SD card reader is on the SCSI bus. If it's a plain old disk then maybe we're scuppered and need to rethink this test. ** Changed in: checkbox (Ubuntu) Status: Triaged = Incomplete I wonder if this is one of those systems that would cause other failures like the storage_test script picking up the empty SD slot as a full block device... we hates these machines... hates them we do. -- Jeff Lane - Hardware Certification Engineer and Test Tools Developer Ubuntu Ham: W4KDH Freenode IRC: bladernr or bladernr_ gpg: 1024D/3A14B2DD 8C88 B076 0DD7 B404 1417 C466 4ABD 3635 3A14 B2DD -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/944939 Title: [Lenovo e320] Checkbox fails to detect the SD and SDHC - Manual test works fine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/944939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 947366] Re: [Lenovo e320] - CPU Test Fails
Did this submit results? Where can I look at the results of this test to see what the output was? This is actually probably not a big deal, as this test is known to be a bit ... flaky. ** Changed in: checkbox (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947366 Title: [Lenovo e320] - CPU Test Fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/947366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925280] Re: Software RAID fails to rebuild after testing degraded cold boot
OK... so I retried... Here is mdstat after installing and booting, and waiting to ensure all syncing had completed: Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md1 : active raid1 sda2[0] sdb2[1] 19529656 blocks super 1.2 [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 48826296 blocks super 1.2 [2/2] [UU] md2 : active raid1 sda3[0] sdb3[1] 175779768 blocks super 1.2 [2/2] [UU] unused devices: none Next, I shut down the system and remove disk 1. On reboot, I run mdstat and note the degraded array with missing members: Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md1 : active (auto-read-only) raid1 sda2[0] 19529656 blocks super 1.2 [2/1] [U_] md0 : active raid1 sda1[0] 48826296 blocks super 1.2 [2/1] [U_] md2 : active raid1 sda3[0] 175779768 blocks super 1.2 [2/1] [U_] unused devices: none Then I shut down and re-insert drive 2: Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md1 : active raid1 sda2[0] sdb2[1] 19529656 blocks super 1.2 [2/2] [UU] md0 : active raid1 sda1[0] 48826296 blocks super 1.2 [2/1] [U_] md2 : active raid1 sda3[0] 175779768 blocks super 1.2 [2/1] [U_] unused devices: none Then I try manually adding the disks per the test case: bladernr@ubuntu~$ sudo mdadm --add /dev/md0 /dev/sdb1 mdadm: /dev/sdb1 reports being an active member for /dev/md0, but a --re-add fails. mdadm: not performing --add as that would convert /dev/sdb1 in to a spare. mdadm: To make this a spare, use mdadm --zero-superblock /dev/sdb1 first. bladernr@ubuntu:~$ sudo mdadm --re-add /dev/md0 /dev/sdb1 mdadm: --re-add for /dev/sdb1 to /dev/md0 is not possible. I got the same for /dev/md2 when trying to re-add /dev/sdb3, so I zero the superblocks, which is essentially blanking the disk and adding it as though it were a brand new disk into the array. bladernr@ubuntu~$ sudo mdadm --zero-superblock /dev/sdb3 bladernr@ubuntu~$ sudo mdadm --zero-superblock /dev/sdb1 bladernr@ubuntu~$ sudo mdadm --add /dev/md0 /dev/sdb1 mdadm: added /dev/sdb1 bladernr@ubuntu~$ sudo mdadm --add /dev/md2 /dev/sdb3 mdadm: added /dev/sdb3 bladernr@ubuntu:~$ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md1 : active raid1 sda2[0] sdb2[1] 19529656 blocks super 1.2 [2/2] [UU] md0 : active raid1 sdb1[2] sda1[0] 48826296 blocks super 1.2 [2/1] [U_] [==..] recovery = 11.9% (5819456/48826296) finish=11.9min speed=59970K/sec md2 : active raid1 sdb3[2] sda3[0] 175779768 blocks super 1.2 [2/1] [U_] resync=DELAYED unused devices: none according to the test case, the most I should have to do is just plug the disk back in and reboot the server which should cause mdadm to automatically re-add the disk and start re-syncing. The most I should have to do is just use the --add command to add the disk back in (or re- add) manually. What I am actually having to do is essentially destroy the partitions for the ext4 LUNs and add them back in as brand new disks. This again, did not happen to the SWAP md device which DID boot degraded, and then re-connected automatically when I put the disk back in. ** Changed in: mdadm (Ubuntu) Status: Incomplete = Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete = New ** Changed in: mdadm (Ubuntu) Status: Confirmed = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925280 Title: Software RAID fails to rebuild after testing degraded cold boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925280] Re: Software RAID fails to rebuild after testing degraded cold boot
Not sure if I should set this to Confirmed or back to New now that I've replied, so setting back to New. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925280 Title: Software RAID fails to rebuild after testing degraded cold boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 900815] Re: After recent update, keys appear to stick or the key-repeat threshold is way too short
@seb128 wish I could tell you, but I have no idea... a lot of things have been updated since I did the Natty - Oneiric upgrade all I really know for certain is that at some point either because of the upgrade, or after an update following the upgrade, I started seeing this issue. Unfortunately, it looks a lot like a run-away interrupt or typematic rate problem, but it's wildly unpredictable, so not something I can reliably reproduce either... :( ** Changed in: unity Status: Expired = New ** Changed in: unity (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/900815 Title: After recent update, keys appear to stick or the key-repeat threshold is way too short To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/900815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876613] Re: [Thinkpad T510] Plugging in DisplayPort causes Unity to crash
Adding Marc Legris... Marc, if you can reproduce this, can you add the xsession-errors log for Bryce? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876613 Title: [Thinkpad T510] Plugging in DisplayPort causes Unity to crash To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/876613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922722] [NEW] 10.04 installer is missing enic network driver
Public bug reported: While attempting to do certification testing on hardware with Cisco VIC Ethernet NICs installed, I noticed that the 10.04.3 installer does not load the enic module. This means I am unable to configure network devices inside the installer, and I am pretty sure this would also impact the ability to perform network installs. Once the system is manually installed, however, the enic module is loaded at boot. From there I can simply add config info to /etc/network/interfaces and /etc/resolv.conf, do an 'ifup eth0' and networking functions as expected from that point onwards. So the installer kernel just needs to have enic added to it. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-33-server 2.6.32-33.70 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-33.70-server 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-server x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory CurrentDmesg: [ 236.156105] enic: eth0: Link UP [ 236.161336] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 236.163850] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 246.566307] eth0: no IPv6 routers present Date: Fri Jan 27 12:11:31 2012 InstallationMedia: Ubuntu-Server 10.04.3 LTS Lucid Lynx - Release amd64 (20110719.2) MachineType: Cisco Systems Inc N20-B6625-2 PciMultimedia: ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-33-server root=UUID=fb997ed0-1193-42fd-9927-5231b87b3b8a ro quiet ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux dmi.bios.date: 08/12/2011 dmi.bios.vendor: Cisco Systems, Inc. dmi.bios.version: S5500.2.0.1d.0.081220111423 dmi.board.asset.tag: Unknown dmi.board.name: N20-B6625-2 dmi.board.vendor: Cisco Systems Inc dmi.board.version: 73-13137-01 dmi.chassis.asset.tag: Unknown dmi.chassis.type: 18 dmi.chassis.vendor: Cisco Systems Inc dmi.chassis.version: 68-3231-01 dmi.modalias: dmi:bvnCiscoSystems,Inc.:bvrS5500.2.0.1d.0.081220111423:bd08/12/2011:svnCiscoSystemsInc:pnN20-B6625-2:pvr:rvnCiscoSystemsInc:rnN20-B6625-2:rvr73-13137-01:cvnCiscoSystemsInc:ct18:cvr68-3231-01: dmi.product.name: N20-B6625-2 dmi.sys.vendor: Cisco Systems Inc ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid needs-upstream-testing networking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922722 Title: 10.04 installer is missing enic network driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/922722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922722] Re: 10.04 installer is missing enic network driver
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922722 Title: 10.04 installer is missing enic network driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/922722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922722] Re: 10.04 installer is missing enic network driver
Additionally, I should add that the apport trace was captured on one of the impacted machines, but uploaded via apport from my workstation due to firewall restrictions where the machines are located. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922722 Title: 10.04 installer is missing enic network driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/922722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924437] Re: Welcome screen release notes link points to ubuntu.com
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924437 Title: Welcome screen release notes link points to ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924437] [NEW] Welcome screen release notes link points to ubuntu.com
Public bug reported: I imagine this is probably just a filler until release notes are finalized on the web but I wanted to make sure it was brought up. On the Welcome Screen (at least so far on the Edubuntu i386 DVD) for Alpha 2, the Release Notes link points to www.ubuntu.com rather than pointing to any page with release notes on thism. Additionally, shouldn't the release notes be on the ISO rather than on a web site. Otherwise, how would someone installing *buntu without an internet connection ever have a chance to read any warnings in the release notes? So from my perspective, I would expect the release notes to be a file on the ISO that is opened by that link, rather than a blurb on the internet that I may not be able to access while installing. Or at the very least, the link needs to point to release notes when they're finalized, rather than the landing page at www.ubuntu.com. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.9.15 ProcVersionSignature: Ubuntu 3.2.0-12.20-generic-pae 3.2.2 Uname: Linux 3.2.0-12-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 CasperVersion: 1.302 Date: Tue Jan 31 18:52:02 2012 LiveMediaBuild: Edubuntu 12.04 Precise Pangolin - Alpha i386 (20120131) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise running-unity ubiquity-2.9.15 ubiquity-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924437 Title: Welcome screen release notes link points to ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924455] [NEW] Failed to create swap space during partitioning
Public bug reported: Running the installer for Edubuntu Alpha 2 32bit on a VirtBox VM. VM has a 12.9GB disk. Installer correctly decided on a partitioning scheme and when it attempted to create partitions, returned a failure (and popped an error dialog up) stating that it failed to create swap space. There was no indication in the installer as tperhpas one of the attached logs will shed light on why the swap creation failed. I clicked OK in the error dialog and proceeded with the instalation. This brought me right back to the partitoning screen. Initially, my only option was to erase and install, because the disk was already partitioned out with two installations. So I chose erase and install, prompting the failure. After clicking OK on the error dialog mentioned above, I was brought right back to the installer, this time providing the options for side by side, upgrade, erase and install and advanced. So on this second run through the partitioner, I chose again, erase and install. This again told me that the entire 12.9 GB disk would be used. So I clicked Install Now to being the partitioning and installation. Here's the error from the dialog box, which appeared the second time as well: The creation of swap space in partition #5 of SCSI1 (0,0,0) (sda) failed ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.9.15 ProcVersionSignature: Ubuntu 3.2.0-12.20-generic-pae 3.2.2 Uname: Linux 3.2.0-12-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 CasperVersion: 1.302 Date: Tue Jan 31 19:07:53 2012 LiveMediaBuild: Edubuntu 12.04 Precise Pangolin - Alpha i386 (20120131) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 iso-testing precise running-unity ubiquity-2.9.15 ubiquity-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924455 Title: Failed to create swap space during partitioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924455] Re: Failed to create swap space during partitioning
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924455 Title: Failed to create swap space during partitioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924455] Re: Failed to create swap space during partitioning
Addition: Just tried the AMD64 Edubuntu DVD and it did NOT fail while creating Swap. The 32bit ISO failed 3/3 tries. AMD64, on a 10.7GB disk worked the first time (32bit VM has a 12.9GB disk.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924455 Title: Failed to create swap space during partitioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924511] [NEW] ubiquity tells me my computer name already exists on the network when it doesnt
Public bug reported: Whatever ubiquity is doing when it tries to find out if a chosen hostname already exists, it's not working very well. Ubiquity tells me that the hostname already exists on the network regardless of whether I'm actually ON a network, or whether that name already exists. It shows me big, warning red letters until it starts verifying my user name as I type that, at which point the hostname turns from a red warning to a green checkbox. BUT the warning is confusing. If I didn't know better, I could easily stand there and re-enter hostnames over and over trying to get one that doesn't generate that warning. In fact, I gave it 4 different hostnames (test, edubuntu, edubuntu-64-1 and edubuntu-64) all of which caused the red Name Exists warning to appear, until I started typing in a different field. This is very confusing to the users, and I imagine is not liminted to Edubuntu, but to ubiquity in general. I'm attaching before and after screenshots to highlight this. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.9.15 ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2 Uname: Linux 3.2.0-12-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CasperVersion: 1.302 Date: Tue Jan 31 15:45:08 2012 LiveMediaBuild: Edubuntu 12.04 Precise Pangolin - Alpha amd64 (20120131) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug iso-testing precise running-unity ubiquity-2.9.15 ubiquity-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924511 Title: ubiquity tells me my computer name already exists on the network when it doesnt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924511] Re: ubiquity tells me my computer name already exists on the network when it doesnt
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924511 Title: ubiquity tells me my computer name already exists on the network when it doesnt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924511] Re: ubiquity tells me my computer name already exists on the network when it doesnt
Screenshot showing one of the host-names I tried that generated the name already exists on network error ** Attachment added: ubiquity-name-exists1.png https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924511/+attachment/2703890/+files/ubiquity-name-exists1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924511 Title: ubiquity tells me my computer name already exists on the network when it doesnt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924511] Re: ubiquity tells me my computer name already exists on the network when it doesnt
THe warning persists for every name I try, until I just give up and move to the username field and start typing there. As soon as I enter something in the username field, the hostname warning changes to a green checkmark. ** Attachment added: ubiquity-name-exists2.png https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924511/+attachment/2703891/+files/ubiquity-name-exists2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924511 Title: ubiquity tells me my computer name already exists on the network when it doesnt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924538] Re: Failed to install all packages selected in Edubuntu according to error popup
Here's the apt history.log ** Attachment added: history.log https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924538/+attachment/2703999/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924538 Title: Failed to install all packages selected in Edubuntu according to error popup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924538] Re: Failed to install all packages selected in Edubuntu according to error popup
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924538 Title: Failed to install all packages selected in Edubuntu according to error popup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924538] [NEW] Failed to install all packages selected in Edubuntu according to error popup
Public bug reported: Doing an install of 64bit Edubuntu Precise Alpha 2 on a VBox VM. During the install, I chose defaults for pretty much everything. This means that during package selection, I did NOT choose the Gnome Fallback desktop, I did NOT install 3rd party stuff or updates, and I DID leave selected all the various Edubuntu package options. At the end of install, I got a popup dialog that said that some packages had failed to install, but no More link or any way to really see which packages had failed. I'm hoping they'll end up in the attached logs. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.9.15 ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2 Uname: Linux 3.2.0-12-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CasperVersion: 1.302 Date: Tue Jan 31 16:35:14 2012 LiveMediaBuild: Edubuntu 12.04 Precise Pangolin - Alpha amd64 (20120131) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity ubiquity-2.9.15 ubiquity-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924538 Title: Failed to install all packages selected in Edubuntu according to error popup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/924538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924565] [NEW] Touchpad on Alienware M15x goes nuts, needs psmouse-ectomy to quiet down
Public bug reported: This is pretty much guaranteed to happen at some point after each reboot. The touchpad will behave (it's not really used as I almost always use an attached Logitech USB Wireless Mouse) as it should for a while and then at some point the pointer starts going crazy, jumping left and right over and over. There doesn't seem to be any specific trigger, it just happens, and there doesn't appear to be any specific time frame either. Sometimes it happens within an hour of a reboot, sometimes it can take a day or more. But once it happens and the pointer starts jumping left and right on it's own, the only cure is to rmmod psmouse. I can reload psmouse and be OK for a while, but invariably, the twitchy pointer returns. This is a regression in one of the recent kernels for Oneiric. I have had Ubuntu on this system since Karmic and have never experienced this issue until a couple months or so ago with an Oneiric update. In fact, I do not recall experiencing this with the original Oneiric released bits. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-14-generic 3.0.0-14.23 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bladernr 2754 F pulseaudio /dev/snd/controlC0: bladernr 2754 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf0f2 irq 48' Mixer name : 'IDT 92HD83C1X5' Components : 'HDA:111d7604,102802a2,00100104' Controls : 16 Simple ctrls : 10 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16' Mixer name : 'Nvidia GPU 0a HDMI/DP' Components : 'HDA:10de000a,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Tue Jan 31 18:04:39 2012 HibernationDevice: RESUME=UUID=f4e6db09-5257-40b2-ba2a-0718fc0b3f0d InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) MachineType: Alienware M15x ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic root=UUID=acc23352-13ab-4854-b1d7-a1099a5bf3a5 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-14-generic N/A linux-backports-modules-3.0.0-14-generic N/A linux-firmware1.60 SourcePackage: linux UpgradeStatus: Upgraded to oneiric on 2011-11-14 (78 days ago) dmi.bios.date: 08/24/2010 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.vendor: Alienware dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd08/24/2010:svnAlienware:pnM15x:pvrA08:rvnAlienware:rn:rvrA08:cvnAlienware:ct8:cvrA08: dmi.product.name: M15x dmi.product.version: A08 dmi.sys.vendor: Alienware ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924565 Title: Touchpad on Alienware M15x goes nuts, needs psmouse-ectomy to quiet down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/924565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924565] Re: Touchpad on Alienware M15x goes nuts, needs psmouse-ectomy to quiet down
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924565 Title: Touchpad on Alienware M15x goes nuts, needs psmouse-ectomy to quiet down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/924565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922722] Re: 10.04 installer is missing enic network driver
Hi Joey, My guess is that it's never been included. That being said, 10.04.3 is the only Lucid I've ever been able to try on this hardware as I've only just recently gotten access to it. I do know that the driver is supported by 11.10, so at some point between the two it was introduced to the installer kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922722 Title: 10.04 installer is missing enic network driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/922722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925157] Re: checkbox-gtk (system testing), fails to send report, also report cannot be opened from checkbox
Hi, Can you also attach the following files: ~/.checkbox/submission.xml ~/.checkbox/checkbox.log Thanks ** Changed in: checkbox (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925157 Title: checkbox-gtk (system testing), fails to send report, also report cannot be opened from checkbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/925157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925280] [NEW] Software RAID fails to rebuild after testing degraded cold boot
Public bug reported: Attempting the RAID install test with Precise server AMD64. Hardware config is a 1U server with 2 SATA drives wth the following partitions: sda: 500GB SATA sda1: 50GB RAID sda2: 20GB RAID sda3: 180GB RAID sdb: 250GB SATA sdb1: 50GB RAID sdb2: 20GB RAID sdb3: 180GB RAID Using the instructions found here: http://testcases.qa.ubuntu.com/Install/ServerRAID1 I created the three partitions for each physical disk. I then created three RAID deviecs, md0 - md2 as follows: md0: 50GB RAID1 using sda1 and sdb1 for / md1: 20GB RAID1 using sda2 and sdb2 for swap md2: 180GB RAID1 using sda3 and sdb3 for /home I then completed the install and reboot. On the initial boot, I verified that all three RAID devices were present and active: bladernr@ubuntu:~$ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 sda1[0] sdb1[1] 48826296 blocks super 1.2 [2/2] [UU] md2: active raid1 sda3[0] sdb3[1] 175838136 blocks super 1.2 [2/2] [UU] md1: active raid1 sda2[0] sdb2[1] 19529656 blocks super 1.2 [2/2] [UU] I then powered the machine down per the test case instructions, removed disk 2 (sdb) and powered back up. On reboot, I verified that the array was active and degraded and powered the system back down, again per the test instructions. I re-inserted drive2 (sdb) and powered the system up again. After logging in, I rechecked /dev/mdstat, expecting to see both drives for each md device and a resync in progress. Instead, I found that the second drive was missing from md0 and md2 while md1 (the swap LUN) was fine. bladernr@ubuntu:~$ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 sda1[0] 48826296 blocks super 1.2 [2/1] [U_] md2: active raid1 sda3[0] 175838136 blocks super 1.2 [2/1][U_] md1: active raid1 sda2[0] sdb2[1] 19529656 blocks super 1.2 [2/2] [UU] The instructions indicated that I may have to re-add the drives that are missing manually, so I attemted this: bladernr@ubuntu:~$ sudo mdadm --add /dev/md0 /dev/sdb1 mdadm: /dev/sdb1 reports being an active member for /dev/md0, but a --re-add fails. mdadm: not performing --add as that would convert /dev/sdb1 in to a spare. mdadm: To make this a spare, use mdadm --zero-superblock /dev/sdb1 first. I also tried using --re-add: bladernr@ubuntu~$ sudo mdadm --re-add /dev/md0 /dev/sdb1 mdadm: --re-add for /dev/sdb1 to /dev/md0 is not possible So here's some info from mdadm: /dev/md0: Version : 1.2 Creation Time : Wed Feb 1 20:53:34 Raid Level : raid1 Array Size : 48826296 (46.56 GiB 50.00GB) Used Dev Size : 48826296 (46.56 GiB 50.00GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Wed Feb 1 23:54:04 2012 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : ubuntu:0 (local to host ubuntu) UUID : 118d60db:4ddc5cf2:040c4cb2:bd896eaf Events : 118 NumberMajorMinorRaidDevices State 0 8 1 0 active sync/dev/sda1 1 0 0 1 removed So according to the test instructions, this test is a failure because I can't rebuild the array (nor is it automatically rebuilt). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-12-generic 3.2.0-12.21 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic x86_64 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Feb 1 23:35 seq crw-rw---T 1 root audio 116, 33 Feb 1 23:35 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 1.91-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Date: Wed Feb 1 23:38:28 2012 HibernationDevice: RESUME=UUID=e573077c-98b5-42e5-9f37-b8efaa2ba74a InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Alpha amd64 (20120201.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Supermicro X7DVL PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-12-generic root=UUID=a84486b9-e72d-4134-82a8-263f91d7d894 ro RelatedPackageVersions: linux-restricted-modules-3.2.0-12-generic N/A linux-backports-modules-3.2.0-12-generic N/A linux-firmware1.68 RfKill: Error: [Errno 2] No such file or
[Bug 925280] Re: Software RAID fails to rebuild after testing degraded cold boot
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925280 Title: Software RAID fails to rebuild after testing degraded cold boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925280] Re: Software RAID fails to rebuild after testing degraded cold boot
I finally found a solution. I had to zero the superblocks on the missing partitions: sudo mdadm --zero-superblock /dev/sdb1 sudo mdamd --zero-superblock /dev/sdb3 sudo mdadm --manage /dev/md0 --add /dev/sdb1 sudo mdadm --manage /dev/md2 --add /dev/sdb3 This now shows md0 currently in recovery and md2 as rsync=DELAYED. So either the instructions are incorrect, or there is an issue in how these devices are handled. This test really should not have degraded the array (or disks) to the extent that I had to zero the second disk to re-add. Also it's worrysome that this only occurred on the ext4 LUN and did not affect the swap LUN. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925280 Title: Software RAID fails to rebuild after testing degraded cold boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
