-
Notifications
You must be signed in to change notification settings - Fork 882
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test_smartos fails in a chroot #2452
Comments
Launchpad user Scott Moser(smoser) wrote on 2014-06-02T20:57:06.546394+00:00 fixed in revno 976 |
Launchpad user Charles Plessy(plessy) wrote on 2014-06-02T21:47:11.162399+00:00 Thanks Scott ! This is very timely as Debian's cloud-init package just got http://bugs.debian.org/750314 filed because the package could not be rebuilt in a chroot. Do you by chance plan an upstream release of cloud-init in the near future ? If not, I will apply revision 976 as a patch to the Debian package. Have a nice day, -- |
Launchpad user Launchpad Janitor(janitor) wrote on 2014-06-03T21:05:50.794075+00:00 This bug was fixed in the package cloud-init - 0.7.6~bzr976-0ubuntu1 cloud-init (0.7.6~bzr976-0ubuntu1) utopic; urgency=medium
|
Launchpad user Scott Moser(smoser) wrote on 2014-08-21T16:39:35.280564+00:00 Charles, we'll get a new 0.7.6 sometime in the next few months at the latest. |
Launchpad user Scott Moser(smoser) wrote on 2014-10-10T15:38:30.379735+00:00 fixed in 0.7.6 |
This bug was originally filed in Launchpad as LP: #1316597
Launchpad details
Launchpad user Juerg Haefliger(juergh) wrote on 2014-05-06T13:12:00.293651+00:00
All tests from test_smartos.py fail in a chroot as follows (only first failure shown):
$ nosetests tests/unittests/test_datasource/test_smartos.py
FFFFFFFFFFFFFFFFFFFFF
FAIL: test_b64_keys (tests.unittests.test_datasource.test_smartos.TestSmartOSDataSource)
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/mocker.py", line 146, in test_method_wrapper
result = test_method()
File "/root/cloud-init/tests/unittests/test_datasource/test_smartos.py", line 270, in test_b64_keys
self.assertTrue(ret)
AssertionError: False is not true
-------------------- >> begin captured logging << --------------------
cloudinit.importer: DEBUG: Looking for modules ['cloudinit.mergers.m_list'] that have attributes ['Merger']
cloudinit.importer: DEBUG: Found m_list with attributes ['Merger'] in ['cloudinit.mergers.m_list']
cloudinit.importer: DEBUG: Looking for modules ['cloudinit.mergers.m_dict'] that have attributes ['Merger']
cloudinit.importer: DEBUG: Found m_dict with attributes ['Merger'] in ['cloudinit.mergers.m_dict']
cloudinit.importer: DEBUG: Looking for modules ['cloudinit.mergers.m_str'] that have attributes ['Merger']
cloudinit.importer: DEBUG: Found m_str with attributes ['Merger'] in ['cloudinit.mergers.m_str']
cloudinit.mergers: DEBUG: Merging 'dict' into 'dict' using method '_handle_unknown' of 'LookupMerger: (3)'
cloudinit.mergers: DEBUG: Merging using located merger 'DictMerger: (method=no_replace,recurse_str=False,recurse_dict=True,recurse_array=False,allow_delete=False)' since it had method '_on_dict'
cloudinit.sources.DataSourceSmartOS: DEBUG: Host does not appear to be on SmartOS
--------------------- >> end captured logging << ---------------------
This is because DataSourceSmartOS.get_data() bails out if it can't find the seed (/dev/ttyS1), which obviously doesn't exist in a pbuilder chroot. The check for /dev/ttyS1 needs to be subbed out.
The text was updated successfully, but these errors were encountered: