Add i386 deploy target to CI to ensure we correctly handle multiple architectures

[Christian Reis]

In https://github.com/Ubuntu-Solutions-Engineering/openstack-installer/issues/324 we saw a report where a user claimed i386 was not deploying correctly with MAAS -- the effect was that amd64 was always selected regardless of any changes the user made. While it's not clear there is an actual bug, we have found our CI testing only covers amd6 at the moment.

We should ensure via CI that this works and stays working; achieving i386 and amd64 coverage should be easy because they both run on the same hardware, and would provide good coverage for our multiple arch support.

[Jason Hobbs (jason-hobbs)]

Probably hard to do but it would be awesome to get ARM and p8 hardware into
the MAAS CI loop also.

On Tue, Jan 13, 2015 at 10:00 AM, Christian Reis <email address hidden> wrote:

> Public bug reported:
>
> In https://github.com/Ubuntu-Solutions-Engineering/openstack-
> installer/issues/324 we saw a report where a user claimed i386 was not
> deploying correctly with MAAS -- the effect was that amd64 was always
> selected regardless of any changes the user made. While it's not clear
> there is an actual bug, we have found our CI testing only covers amd6 at
> the moment.
>
> We should ensure via CI that this works and stays working; achieving
> i386 and amd64 coverage should be easy because they both run on the same
> hardware, and would provide good coverage for our multiple arch support.
>
> ** Affects: maas
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to MAAS.
> Matching subscriptions: maas-bugs
> https://bugs.launchpad.net/bugs/1410336
>
> Title:
> Add i386 deploy target to CI to ensure we correctly handle multiple
> architectures
>
> Status in MAAS:
> New
>
> Bug description:
> In https://github.com/Ubuntu-Solutions-Engineering/openstack-
> installer/issues/324 we saw a report where a user claimed i386 was not
> deploying correctly with MAAS -- the effect was that amd64 was always
> selected regardless of any changes the user made. While it's not
> clear there is an actual bug, we have found our CI testing only covers
> amd6 at the moment.
>
> We should ensure via CI that this works and stays working; achieving
> i386 and amd64 coverage should be easy because they both run on the
> same hardware, and would provide good coverage for our multiple arch
> support.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1410336/+subscriptions
>

[Raphaël Badin (rvb)]

We had 2 ARM nodes in the lab before it got moved… I'll check with the data engineers to see what happened to them.

[Andres Rodriguez (andreserl)]

Hi!

**This is an automated message**

We believe this is may no longer be an issue in the latest MAAS release. Due to the date of this bug report, we are marking this bug report as invalid. If you believe this is still an issue, please re-open this bug report.

Thanks