[Touch-packages] [Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
This failure has not been due to Juju but rather the setup of the CI
environment. We have not seen any consecutive failures of this nature,
so the issue has been resolved.
I am closing this report.
** Changed in: juju
Status: Incomplete => Fix Released
** Changed in: dbus (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed out waiting for workers zesty
because dbus is in interactive mode
Status in juju:
Fix Released
Status in juju 2.1 series:
Won't Fix
Status in dbus package in Ubuntu:
Fix Released
Bug description:
As seen at
http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e
A unit test is exclusively failing on our new zesty machine. the
previous issues is not related to the zesty falures
machine-0: has workers [agent api-address-updater api-caller
api-config-watcher disk-manager log-forwarder log-sender logging-config-updater
machine-action-runner machiner migration-fortress migration-inactive-flag
migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater
state-config-watcher storage-provisioner termination-signal-handler
unconverted-api-workers upgrade-check-flag upgrade-check-gate
upgrade-steps-flag upgrade-steps-gate upgrader]
machine-0: waiting for [unit-agent-deployer]
machine-0: unexpected []
machine-0: report:
{}
machine_test.go:1272:
WaitMatch(c, matcher.Check, coretesting.LongWait,
s.BackingState.StartSync)
engine_test.go:234:
c.Fatalf("timed out waiting for workers")
... Error: timed out waiting for workers
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1237846] Re: OSK autopilot emulator isn't able to shift into CAPSLOCK state successfully.
I am pretty sure that veebers is not working on this bug. ** Changed in: ubuntu-keyboard (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1237846 Title: OSK autopilot emulator isn't able to shift into CAPSLOCK state successfully. Status in ubuntu-keyboard package in Ubuntu: Triaged Bug description: There is an issue with how the emulator handles changing states and currently can't handle changing into CAPSLOCK mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1237846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377169] Re: Top Crasher: /usr/bin/autopilot3:TypeError:/usr/bin/autopilot3@9:main:run:run_tests:run:__call__:run:run:run:_run_one:_run_prepared_result:_report_failure:addFailure
I am pretty sure that veebers is not working on this bug. ** Changed in: autopilot (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1377169 Title: Top Crasher: /usr/bin/autopilot3:TypeError:/usr/bin/autopilot3@9:main:run:run_tests:run:__call__:run:run:run:_run_one:_run_prepared_result:_report_failure:addFailure:addFailure:addFailure:addError:_convert:status:status:_gather_test:_fail:_details_to_str:as_text:_iter_text:decode Status in autopilot package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding autopilot. This problem was most recently seen with version 1.5.0+14.10.20140812-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/f293befd9513bb3f7a21b730cf9026f38d43e8e1 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1377169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1238662] Re: [autopilot] needs tests for deployment features
I am pretty sure that veebers is not working on this bug. ** Changed in: qtcreator-plugin-ubuntu (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1238662 Title: [autopilot] needs tests for deployment features Status in qtcreator-plugin-ubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: Opinion Bug description: so with the switch to mir/unity-mir we created this bug https://bugs.launchpad.net/qtcreator-plugin-ubuntu/+bug/1238031 as that feature is fairly critical for app developers & permissions topics haven't fully settled - i would suggest we have some sort of test for this. its kind of weird cause its SDK, requiring both PC & devicemaybe they already have a test to harness ?? can you help us? (note if you want to put this in a blueprint that's ok too) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1238662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1204982] Re: refactored autopilot tests are fail prone for wrong environment setup
I am pretty sure that veebers is not working on this bug. ** Changed in: unity8 (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1204982 Title: refactored autopilot tests are fail prone for wrong environment setup Status in Autopilot: Invalid Status in unity8 package in Ubuntu: Triaged Bug description: The old autopilot tests, when you would launch "autopilot run unity8" from within the source directory in tests/autopilot/, it would always try to run the local build. If there was no local build, it would fail, saying it can't find the binary. The new ones, don't. They fall back to the installed binary even though loading local tests. This fails in like 99% of the cases. Even worse, the error messages you get just totally don't match with the code you are examining for debugging. This issue is even worse now that the tests require a make install in the builddir (not telling so btw). If the install step really really needs to be kept (which I'm strongly voting against) then there should be a big fat debug output which binary is loaded, a big fat warning if the expected local installation is not found and in no way falling back to some other unity8 binary not having to do anything with the local test suite. To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot/+bug/1204982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1229561] Re: Automated regression test for Bug #1227714 (OSK doesn't close after the application closes)
I am pretty sure that veebers is not working on this bug. ** Changed in: ubuntu-keyboard (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1229561 Title: Automated regression test for Bug #1227714 (OSK doesn't close after the application closes) Status in ubuntu-keyboard package in Ubuntu: Triaged Bug description: Automated regression test for Bug #1227714 (OSK doesn't close after the application closes). A test to show when this bug is resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1229561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1202511] Re: Clean up unity8 indicator client test suite
I am pretty sure that veebers is not working on this bug. ** Changed in: unity8 (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1202511 Title: Clean up unity8 indicator client test suite Status in unity8 package in Ubuntu: New Bug description: The unity8 indicators autopilot test suite needs a cleanup, similar to the unity8 shell tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1202511/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1260013] Re: [ap test] need to test click package app launching from dash
I am pretty sure that veebers is not working on this bug. ** Changed in: unity8 (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1260013 Title: [ap test] need to test click package app launching from dash Status in unity8 package in Ubuntu: Triaged Bug description: this is related to an issue we found in the latest attempt to promote unity8 into the image. we do have an AP test in which core/resident apps are launched from the dash, but no click packages. We need to add a test specifically for click packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1260013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1281688] Re: autopilot vis fails with: autopilot.introspection.dbus.StateNotFoundError
I am pretty sure that veebers is not working on this bug.
** Changed in: xpathselect
Assignee: Christopher Lee (veebers) => (unassigned)
** Changed in: xpathselect
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1281688
Title:
autopilot vis fails with:
autopilot.introspection.dbus.StateNotFoundError
Status in XPathSelect:
New
Status in autopilot package in Ubuntu:
New
Status in xpathselect package in Ubuntu:
Fix Released
Bug description:
When introspecting large application like qtcreator, autopilot vis
fails with:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/autopilot/vis/main_window.py", line
133, in tree_item_changed
self.detail_widget.tree_node_changed(proxy)
File "/usr/lib/python2.7/dist-packages/autopilot/vis/objectproperties.py",
line 64, in tree_node_changed
self.widget(i).new_node_selected(new_node)
File "/usr/lib/python2.7/dist-packages/autopilot/vis/objectproperties.py",
line 123, in new_node_selected
object_details = node.get_properties()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 246, in get_properties
self.refresh_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 472, in refresh_state
_, new_state = self.get_new_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 562, in get_new_state
raise StateNotFoundError(self.__class__.__name__, id=self.id)
autopilot.introspection.dbus.StateNotFoundError: State not found for class
'Core::Internal::MainWindow' and filters {'id': 3}.
TEST CASE
1. Install qtcreator
2. Run: autopilot launch qtcreator
3. Run: autopilot vis
4. In vis select qtcreator
5. Browser the widget tree
ACTUAL RESULT
Lot of widget can not be instrospected and fail with StateNotFound
EXPECTED RESULT
User can introspect the whole tree
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python-autopilot 1.4+14.04.20140213-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 18 09:19:29 2014
InstallationDate: Installed on 2013-09-03 (167 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
PackageArchitecture: all
SourcePackage: autopilot
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xpathselect/+bug/1281688/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1322199] Re: autopilot cannot fully introspect Qt applications
I am pretty sure that veebers is not working on this bug. ** Changed in: autopilot-qt Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot-qt in Ubuntu. https://bugs.launchpad.net/bugs/1322199 Title: autopilot cannot fully introspect Qt applications Status in Autopilot Qt Support: Confirmed Status in autopilot-qt package in Ubuntu: Confirmed Bug description: Currently, for Qt apps, autopilot Qt introspection library is not taking into account non-QObject objects. Some widgets store visible elements in non-QObect data structures and are not visible from autopilot even if they are visible on the screen. This is for example the case for the content of QTableWidget, QListWidget, QTreeWidget etc. These objects store data in QTableWidgetItem, QListWidgetItem and QTreeWidgetItem respectively. These data structures do not inherit QObject. Autopilot should be improved to handle non-Qobject type datatypes for any UI element. To reproduce build the examples from the package qtbase5-examples and try to introspect applications in examples/widgets/ that contains any of the widget mentioned above e.g findfiles or spreadsheet. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libautopilot-qt 1.4+14.04.20140312-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 22 16:02:37 2014 InstallationDate: Installed on 2013-09-03 (260 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) SourcePackage: autopilot-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-qt/+bug/1322199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
** Changed in: juju
Milestone: 2.2-beta3 => None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed out waiting for workers zesty
because dbus is in interactive mode
Status in juju:
Incomplete
Status in juju 2.1 series:
Won't Fix
Status in dbus package in Ubuntu:
New
Bug description:
As seen at
http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e
A unit test is exclusively failing on our new zesty machine. the
previous issues is not related to the zesty falures
machine-0: has workers [agent api-address-updater api-caller
api-config-watcher disk-manager log-forwarder log-sender logging-config-updater
machine-action-runner machiner migration-fortress migration-inactive-flag
migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater
state-config-watcher storage-provisioner termination-signal-handler
unconverted-api-workers upgrade-check-flag upgrade-check-gate
upgrade-steps-flag upgrade-steps-gate upgrader]
machine-0: waiting for [unit-agent-deployer]
machine-0: unexpected []
machine-0: report:
{}
machine_test.go:1272:
WaitMatch(c, matcher.Check, coretesting.LongWait,
s.BackingState.StartSync)
engine_test.go:234:
c.Fatalf("timed out waiting for workers")
... Error: timed out waiting for workers
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
** Changed in: juju
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed out waiting for workers zesty
because dbus is in interactive mode
Status in juju:
Incomplete
Status in juju 2.1 series:
Won't Fix
Status in dbus package in Ubuntu:
New
Bug description:
As seen at
http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e
A unit test is exclusively failing on our new zesty machine. the
previous issues is not related to the zesty falures
machine-0: has workers [agent api-address-updater api-caller
api-config-watcher disk-manager log-forwarder log-sender logging-config-updater
machine-action-runner machiner migration-fortress migration-inactive-flag
migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater
state-config-watcher storage-provisioner termination-signal-handler
unconverted-api-workers upgrade-check-flag upgrade-check-gate
upgrade-steps-flag upgrade-steps-gate upgrader]
machine-0: waiting for [unit-agent-deployer]
machine-0: unexpected []
machine-0: report:
{}
machine_test.go:1272:
WaitMatch(c, matcher.Check, coretesting.LongWait,
s.BackingState.StartSync)
engine_test.go:234:
c.Fatalf("timed out waiting for workers")
... Error: timed out waiting for workers
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
** Changed in: juju
Milestone: 2.2-beta2 => 2.2-beta3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed out waiting for workers zesty
because dbus is in interactive mode
Status in juju:
Triaged
Status in juju 2.1 series:
Won't Fix
Status in dbus package in Ubuntu:
New
Bug description:
As seen at
http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e
A unit test is exclusively failing on our new zesty machine. the
previous issues is not related to the zesty falures
machine-0: has workers [agent api-address-updater api-caller
api-config-watcher disk-manager log-forwarder log-sender logging-config-updater
machine-action-runner machiner migration-fortress migration-inactive-flag
migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater
state-config-watcher storage-provisioner termination-signal-handler
unconverted-api-workers upgrade-check-flag upgrade-check-gate
upgrade-steps-flag upgrade-steps-gate upgrader]
machine-0: waiting for [unit-agent-deployer]
machine-0: unexpected []
machine-0: report:
{}
machine_test.go:1272:
WaitMatch(c, matcher.Check, coretesting.LongWait,
s.BackingState.StartSync)
engine_test.go:234:
c.Fatalf("timed out waiting for workers")
... Error: timed out waiting for workers
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
** Changed in: juju
Milestone: 2.2-alpha1 => 2.2-rc1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed out waiting for workers zesty
because dbus is in interactive mode
Status in juju:
Triaged
Status in juju 2.1 series:
Won't Fix
Status in dbus package in Ubuntu:
New
Bug description:
As seen at
http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e
A unit test is exclusively failing on our new zesty machine. the
previous issues is not related to the zesty falures
machine-0: has workers [agent api-address-updater api-caller
api-config-watcher disk-manager log-forwarder log-sender logging-config-updater
machine-action-runner machiner migration-fortress migration-inactive-flag
migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater
state-config-watcher storage-provisioner termination-signal-handler
unconverted-api-workers upgrade-check-flag upgrade-check-gate
upgrade-steps-flag upgrade-steps-gate upgrader]
machine-0: waiting for [unit-agent-deployer]
machine-0: unexpected []
machine-0: report:
{}
machine_test.go:1272:
WaitMatch(c, matcher.Check, coretesting.LongWait,
s.BackingState.StartSync)
engine_test.go:234:
c.Fatalf("timed out waiting for workers")
... Error: timed out waiting for workers
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403955] Re: DHCP's "Option interface-mtu 9000" is being ignored on bridge interface br0
** Changed in: juju-core
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's "Option interface-mtu 9000" is being ignored on bridge
interface br0
Status in juju-core:
Won't Fix
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
In an env with jumbo frames enabled, and using MAAS as DHCP server,
the client receives the following IPv4 lease:
$ cat /var/lib/dhcp/dhclient.br0.leases
lease {
interface "br0";
fixed-address 10.230.20.26;
filename "pxelinux.0";
option subnet-mask 255.255.248.0;
option dhcp-lease-time 43200;
option routers 10.230.16.1;
option dhcp-message-type 5;
option dhcp-server-identifier 10.230.20.1;
option domain-name-servers 10.230.20.1;
option interface-mtu 9000;
option broadcast-address 10.230.23.255;
option domain-name "ctsstack.qa.1ss";
renew 3 2014/12/17 16:48:15;
rebind 3 2014/12/17 21:52:09;
expire 3 2014/12/17 23:22:09;
}
The interfaces show the following config after boot:
$ ifconfig br0
br0 Link encap:Ethernet HWaddr a0:d3:c1:01:9d:58
inet addr:10.230.20.26 Bcast:10.230.23.255 Mask:255.255.248.0
inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:530530 errors:0 dropped:0 overruns:0 frame:0
TX packets:1591569 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:68713489 (68.7 MB) TX bytes:213710979 (213.7 MB)
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr a0:d3:c1:01:9d:58
inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10539274 errors:0 dropped:3394 overruns:0 frame:454
TX packets:2627412 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2320560616 (2.3 GB) TX bytes:3562885157 (3.5 GB)
Interrupt:32
"option interface-mtu 9000;" from the lease file is being ignored by br0.
Could it be related to eth0 MTU size? If that's the case, shouldn't both
interfaces be updated?
Other info:
$ brctl show br0
bridge name bridge id STP enabled interfaces
br0 8000.a0d3c1019d58 no eth0
$ cat /etc/network/eth0.config
iface eth0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4
>From mwhudson: we don't use gccgo on arm64 any more. ** Changed in: juju-core (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gccgo-4.9 in Ubuntu. https://bugs.launchpad.net/bugs/1472650 Title: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4 Status in gcc: Unknown Status in gcc-5 package in Ubuntu: Fix Released Status in gccgo-4.9 package in Ubuntu: Invalid Status in gccgo-5 package in Ubuntu: Invalid Status in juju-core package in Ubuntu: Invalid Status in gccgo-4.9 source package in Trusty: Fix Released Status in gccgo-4.9 source package in Vivid: Invalid Status in gccgo-5 source package in Vivid: Fix Released Status in gccgo-4.9 source package in Wily: Invalid Bug description: [Impact] Various go-based packages crash on startup on arm64 when booted with a kernel where CONFIG_ARM64_PGTABLE_LEVELS=4. LXD, docker and juju are examples. Ubuntu does not ship with this config, so it is currently not impacted. However, we would like to enable this config to add new hardware support in 15.10. The 15.10 kernel will eventually be provided in trusty as an lts backport, at which point this will begin to break users. [Test Case] Boot an arm64 system with CONFIG_ARM64_PGTABLE_LEVELS=4 enabled in the kernel. Install docker.io and run "docker help". If it fails, you'll see "fatal error: runtime_lfstackpush" followed by a stack trace. If it succeeds, you'll get normal help output. [Regression Risk] The risk of regression is lessened by testing this release on existing Ubuntu kernels w/ 3 level page tables. To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1472650/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
