cloud-init

tests fail under python 3.6

Bug #1703697 reported by Joshua Powers
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
High
Unassigned
cloud-init (Ubuntu)
Fix Released
High
Scott Moser

Bug Description

Steps to reproduce:
1. lxc launch ubuntu-daily:a a
2. lxc exec a bash
3. add-apt-repository ppa:canonical-foundations/python3.6-as-default -y
4. apt-get update
5. apt-get upgrade -y
6. apt-get install tox
6. git clone https://git.launchpad.net/cloud-init
7. cd cloud-init
8. tox

Expected results:
All tests pass

Actual results:
Numerous unittest failures, see:
http://paste.ubuntu.com/25071344/

There appear to be three types of errors:

9x jsonpatch issues related: http://paste.ubuntu.com/25071366/
2x unexpected None type: http://paste.ubuntu.com/25071385/
1x incorrect assert/mock(?) http://paste.ubuntu.com/25071375/

Related bugs:
 * bug 1704024: stack trace on import with python3.6

See original description

Related branches

~smoser/cloud-init:bug/1703697-python3.6-ubuntu
Chad Smith: Approve
Server Team CI bot: Approve (continuous-integration)
Joshua Powers (community): Approve
Diff: 178 lines (+34/-38)
4 files modified
cloudinit/net/netplan.py (+2/-1)
tests/unittests/helpers.py (+20/-1)
tests/unittests/test_distros/test_create_users.py (+12/-18)
tests/unittests/test_runs/test_simple_run.py (+0/-18)
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Certainly at the least we need a new python-json-patch but that's a bit complicated thanks to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839779. Trying to figure out what to do about that.

Scott Moser (smoser)
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → High
Scott Moser (smoser)
description: updated
Revision history for this message
Scott Moser (smoser) wrote :

I filed bug 1704024 for python-jsonpatch.

Scott Moser (smoser)
summary: - tox fails under python 3.6
+ tests fail under python 3.6
Scott Moser (smoser)
Changed in cloud-init (Ubuntu):
assignee: nobody → Scott Moser (smoser)
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Scott Moser (smoser) wrote :

I've just now uploaded to artful
 cloud-init_0.7.9-210-ge80517ae-0ubuntu1.dsc
cloud-init should no longer be blocking python3.6 as default python3.

Scott Moser (smoser)
Changed in cloud-init:
status: Confirmed → Fix Committed
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

I don't know what happened but e80517ae does not have any python 3.6 changes in its ancestry and the package still ftbfs in the 3.6 ppa

Revision history for this message
Scott Moser (smoser) wrote :

This is uploaded now under 0.7.9-212-g865e941f-0ubuntu1 but in keeping with my slew of mistakes i didn't reference the bug in the changelog.

Changed in cloud-init (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Scott Moser (smoser) wrote : Fixed in Cloud-init 17.1

This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Fix Committed → Fix Released
Revision history for this message
James Falcon (falcojr) wrote :

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/2948

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.