/gomaasapi

Make interface_set optional in device_2_0 #45

Closed
wants to merge 1 commit into
from

Conversation

Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@babbageclunk @dimitern @howbazaar
@babbageclunk
Member

babbageclunk commented Apr 21, 2016

Devices with no interface_set attributes have been observed in testing with KVM-based MAAS 2 clusters.
@babbageclunk
Make interface_set optional in device_2_0 
Devices with no interface_sets have been observed in testing with
KVM-based MAAS 2.
548b4eb
@dimitern
Contributor

dimitern commented Apr 21, 2016

LGTM
@howbazaar
Owner

howbazaar commented Apr 22, 2016

See. https://bugs.launchpad.net/maas/+bug/1567213

MAAS 2.0 should now have it, and will by the full release.
@babbageclunk
Member

babbageclunk commented Apr 22, 2016

Yeah, Dimiter thought that might have been the case, that's why I held off
on landing it - doing the upgrade now, hit a few snags.

On Fri, 22 Apr 2016, 05:14 Tim Penhey, notifications@github.com wrote:

See. https://bugs.launchpad.net/maas/+bug/1567213

MAAS 2.0 should now have it, and will by the full release.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#45 (comment)
@babbageclunk
Member

babbageclunk commented Apr 22, 2016

This isn't needed, devices always have interface_set now.

@babbageclunk babbageclunk closed this Apr 22, 2016

@babbageclunk babbageclunk deleted the babbageclunk:interface-set-optional branch Apr 25, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment