Test suite results on Fedora 20
by Amit Saha
I ran the test suite from the current release-0.14 branch on an updated Fedora 20 install.
Overall results
===============
905 tests, 4 failures, 1 error, 3 skips in 2817.6s
Errors
======
This shouldn't have happened. Need to dig deeper.
ERROR: bkr.inttest.client.test_distro_trees_verify:DistroTreesVerifyTest.test_verify_distro
vi +17 src/bkr/inttest/client/test_distro_trees_verify.py # setUp
session.expunge(lca)
vi +149 /usr/lib64/python2.7/site-packages/sqlalchemy/orm/scoping.py # do
return getattr(self.registry(), name)(*args, **kwargs)
vi +1294 /usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py # expunge
orm_util.state_str(state))
InvalidRequestError: Instance <LabControllerDistroTree at 0x7d3a050> is not present in this Session
-------------------- >> begin captured logging << --------------------
bkr.inttest.data_setup: DEBUG: Created distro Distro(name=u'DansAwesomeLinux6.9-19')
bkr.inttest.data_setup: DEBUG: Created distro tree DistroTree(distro=Distro(name=u'DansAwesomeLinux6.9-19'), variant=u'Server', arch=i386)
--------------------- >> end captured logging << ---------------------
/usr/lib64/python2.7/site-packages/sqlalchemy/orm/dependency.py:460: SAWarning: Object of type <MachineRecipe> not in session, add operation along 'DistroTree.recipes' will not proceed
prop=self.prop)
/usr/lib64/python2.7/site-packages/sqlalchemy/orm/dependency.py:460: SAWarning: Object of type <GuestRecipe> not in session, add operation along 'DistroTree.recipes' will not proceed
prop=self.prop)
Failures
========
These don't happen on Fedora 18, and I believe have a common root cause. Not sure what atm.
FAIL: bkr.inttest.server.tools.test_log_delete:RemoteLogDeletionTest.test_301_redirect
vi +194 src/bkr/inttest/server/tools/test_log_delete.py # test_301_redirect
self.assertEquals(log_delete.log_delete(), 0) # exit status
AssertionError: 1 != 0
-------------------- >> begin captured stdout << ---------------------
127.0.0.1 - - [07/Nov/2013 20:41:08] "DELETE /redirect/301/recipe HTTP/1.1" 301 0
127.0.0.1 - - [07/Nov/2013 20:41:08] "GET /recipe HTTP/1.1" 301 0
Traceback (most recent call last):
File "/usr/lib64/python2.7/wsgiref/handlers.py", line 85, in run
self.result = application(self.environ, self.start_response)
File "/root/beaker/IntegrationTests/src/bkr/inttest/server/tools/../../archive_server.py", line 43, in wsgi
return wsgiref.util.FileWrapper(open(localpath, 'r'))
IOError: [Errno 21] Is a directory: '/tmp/beaker-test-log-deleteLto8eu/recipe/'
127.0.0.1 - - [07/Nov/2013 20:41:08] "GET /recipe/ HTTP/1.1" 500 59
FAIL: bkr.inttest.server.tools.test_log_delete:RemoteLogDeletionTest.test_302_redirect
vi +201 src/bkr/inttest/server/tools/test_log_delete.py # test_302_redirect
self.assertEquals(log_delete.log_delete(), 0) # exit status
AssertionError: 1 != 0
-------------------- >> begin captured stdout << ---------------------
127.0.0.1 - - [07/Nov/2013 20:41:10] "DELETE /redirect/301/recipe HTTP/1.1" 301 0
127.0.0.1 - - [07/Nov/2013 20:41:10] "GET /recipe HTTP/1.1" 301 0
Traceback (most recent call last):
File "/usr/lib64/python2.7/wsgiref/handlers.py", line 85, in run
self.result = application(self.environ, self.start_response)
File "/root/beaker/IntegrationTests/src/bkr/inttest/server/tools/../../archive_server.py", line 43, in wsgi
return wsgiref.util.FileWrapper(open(localpath, 'r'))
IOError: [Errno 21] Is a directory: '/tmp/beaker-test-log-deletexLnlrI/recipe/'
127.0.0.1 - - [07/Nov/2013 20:41:10] "GET /recipe/ HTTP/1.1" 500 59
127.0.0.1 - - [07/Nov/2013 20:41:10] "DELETE /redirect/302/recipe HTTP/1.1" 302 0
127.0.0.1 - - [07/Nov/2013 20:41:10] "GET /recipe HTTP/1.1" 301 0
Traceback (most recent call last):
File "/usr/lib64/python2.7/wsgiref/handlers.py", line 85, in run
self.result = application(self.environ, self.start_response)
File "/root/beaker/IntegrationTests/src/bkr/inttest/server/tools/../../archive_server.py", line 43, in wsgi
return wsgiref.util.FileWrapper(open(localpath, 'r'))
FAIL: bkr.inttest.server.tools.test_log_delete:RemoteLogDeletionTest.test_deletion
vi +186 src/bkr/inttest/server/tools/test_log_delete.py # test_deletion
self.assertEquals(log_delete.log_delete(), 0) # exit status
AssertionError: 1 != 0
-------------------- >> begin captured stdout << ---------------------
127.0.0.1 - - [07/Nov/2013 20:41:13] "DELETE /recipe HTTP/1.1" 301 0
Traceback (most recent call last):
File "/usr/lib64/python2.7/wsgiref/handlers.py", line 85, in run
self.result = application(self.environ, self.start_response)
File "/root/beaker/IntegrationTests/src/bkr/inttest/server/tools/../../archive_server.py", line 43, in wsgi
return wsgiref.util.FileWrapper(open(localpath, 'r'))
IOError: [Errno 21] Is a directory: '/tmp/beaker-test-log-deletexQISKS/recipe/'
127.0.0.1 - - [07/Nov/2013 20:41:13] "GET /recipe/ HTTP/1.1" 500 59
And of course the omnipresent:
FAIL: bkr.inttest.server.test_jobs:TestJobsController.test_job_xml_can_be_roundtripped
vi +72 src/bkr/inttest/server/test_jobs.py # test_job_xml_can_be_roundtripped
Best,
Amit.
10 years, 5 months
Beaker tasks in a separate repository?
by Amit Saha
I am beginning to think why don't we maintain the Beaker tasks in a separate repository?
Each task has and will have their own version/release info, so there won't be a "release"
of the tasks per se.
We have made task upgrades in the past at various points during the release cycle, so there
doesn't seem to be any pressing reason not to do this.
Thoughts?
Best,
-Amit.
--
Amit Saha <http://echorand.me>
Infrastructure Engineering and Development
Red Hat, Inc.
10 years, 5 months
Beaker 0.14.2 to be deployed next Thursday, 7th November
by Nick Coghlan
All,
The upstream release of Beaker v0.14.2 has been published today on
beaker-project.org [1].
Assuming the final pre-deployment checks go well, we anticipate that
this release will be deployed to the main Red Hat Beaker instance
next Thursday the 7th November at midnight UTC.
= What's coming up in this release? =
The most significant updates included in Beaker 0.14.2 are:
* addon repos will be imported correctly for post-Alpha 3 RHEL7 builds
* the btrfs technical preview in RHEL6 will once again be supported
* provisioned EFI systems will always be reconfigured to boot from the
network interface, even if the installed distribution switches them to
local boot by default
* the default authentication configuration will be used on all
distributions, not just on RHEL6. The new "auth" ks_meta setting will
allow this to be configured directly in the recipe XML
* the inventory task will once again handle s390x and ppc64 systems
* group owners will be identified on the group page for all users,
making it easier to request membership of appropriate groups
* some situations that would previously cause a recipe to hang
indefinitely will correctly cause it to Abort
A description of the changes in the release can be found in the updated
Beaker 0.14 release notes [2].
The complete list of all changes made since Beaker v0.14.1 is also
available [3].
= Beaker 0.15 status update =
After the attempted deployment of Beaker 0.15 revealed some significant
gaps in our regression and acceptance testing for Beaker, we took the
time to critically assess the functional differences between Beaker 0.14
and 0.15 revealed by the upgrade, and determined that additional time
was needed to ensure that the new access control model in Beaker 0.15
was certain to meet the needs of *all* of our internal users. While the
upstream Beaker v0.15.1 release resolved the most significant
regressions in capability (and is thus suitable for deployment in most
environments), we have determined that there is still at least one
remaining case where command-line based automation that worked correctly
in Beaker v0.14 is currently not supported in Beaker v0.15.1.
Accordingly, the Beaker v0.15.1 upstream release will *not* be deployed
internally at Red Hat.
While we continue to work on ensuring Beaker v0.15.2 restores command
line access to the affected functionality (or an acceptable equivalent),
we have reactivated the Beaker v0.14 maintenance branch and backported
the applicable fixes and minor features from Beaker v0.15 and v0.15.1
that met the criteria for inclusion in a maintenance release.
Another Beaker v0.14.3 maintenance release is anticipated after this
one, with Beaker v0.15.2 likely to be deployed following the
completion of the RHEL6.5 formal testing period.
= Thanks to... =
All of our users who provided detailed failure reports in Bugzilla
during the ~24 hour period that Beaker v0.15 was live, allowing us
to identify the gaps between the functionality offered by the
relatively ad hoc access control mechanism in Beaker v0.14 and the
more formalised (and configurable) access control mechanism in
Beaker v0.15. This feedback also identified several specific issues
with the updated web interface that weren't evident in the test
data that we were using at the time.
Jiri Jaburek for working out that there was still an unacceptable gap
between Beaker v0.14 and even Beaker v0.15.1 when it came to managing
manual system reservations through the command line interface.
= Get in touch =
If you have any questions about Red Hat's Beaker installation, contact
beaker-user-list(a)redhat.com or join #beaker on internal IRC.
The activities of the core Beaker development team are managed through
HSS Confluence and JIRA Agile [4].
For questions about the upstream Beaker project, contact
beaker-devel(a)lists.fedorahosted.org or join #beaker on FreeNode.
If you're interested in helping to improve Beaker more directly, refer
to the upstream developer guide [5] and technical road map [6].
Regards,
Nick.
[1] http://beaker-project.org/releases/
[2] http://beaker-project.org/docs/whats-new/release-0.14.html#beaker-0-14-2
[3] http://beaker-project.org/releases/beaker-0.14.2-ChangeLog
[4] https://docs.engineering.redhat.com/x/D4C_/
[5] http://beaker-project.org/dev/guide/
[6] http://beaker-project.org/dev/tech-roadmap.html
--
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane
Testing Solutions Team Lead
Beaker Development Lead (http://beaker-project.org/)
10 years, 5 months
Beaker 0.14.2 released!
by Nick Coghlan
On behalf of the Beaker development team, I'm pleased to announce that
Beaker v0.14.2 is now available from beaker-project.org [1].
Users may(!) have noticed that there were some unfortunate problems with
the new access control model and web UI updates in Beaker v0.15. While
the Beaker v0.15.1 release resolved the significant regressions in
capability (and is thus suitable for deployment in most environments),
there is still at least one remaining case where command-line based
automation that worked correctly in Beaker v0.14 is currently not
supported in Beaker v0.15.1.
Accordingly, while we continue to work on ensuring Beaker v0.15.2
provides a suitable replacement for that functionality, we have
reactivated the Beaker v0.14 maintenance branch and backported the
applicable fixes and minor features from Beaker v0.15 and v0.15.1 that
met the criteria for inclusion in a maintenance release.
A description of the backported changes can be found in the updated
Beaker 0.14 release notes [2].
The detailed list of all changes made since Beaker v0.14.1 is also
available [3].
Regards,
Nick.
[1] http://beaker-project.org/releases/
[2] http://beaker-project.org/docs/whats-new/release-0.14.html#beaker-0-14-2
[3] http://beaker-project.org/releases/beaker-0.14.2-ChangeLog
--
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane
Testing Solutions Team Lead
Beaker Development Lead (http://beaker-project.org/)
10 years, 5 months