1.9.0 and 1.8.3 issues

Just a reminder that we have two sets of important issues that I'd still
appreciate help on.

The first is for Foreman 1.8.3, which may well be the last in the series
unless there are further important regressions or security issues.

Those can be found at: http://bit.ly/1MfBtQm

Marek - I know you've been triaging some network issues, are there any
more you'd like to add to that list?

The second is for Foreman 1.9.0, which is a nice, short list at the
moment with just two unfixed issues. So far it looks like we won't have
a further release candidate, and can potentially release 1.9.0 in the
next couple of weeks.

That's here: http://bit.ly/1FyhCnI

Cheers,

··· -- Dominic Cleal Red Hat Engineering

Hello

I think there's no regression introduced in 1.8 branch related to networking.
It would be nice to fix some issues [1][2] in interface parsing but as far as
I can tell they are present at least since 1.7.

[1] Bug #10805: VLAN interface attached to bond is wrongly created as Bond - Foreman
[2] Bug #11034: network/interfaces validation checks the removed interfaces - Foreman

··· On Monday 20 of July 2015 14:09:31 Dominic Cleal wrote: > Just a reminder that we have two sets of important issues that I'd still > appreciate help on. > > The first is for Foreman 1.8.3, which may well be the last in the series > unless there are further important regressions or security issues. > > Those can be found at: http://bit.ly/1MfBtQm > > Marek - I know you've been triaging some network issues, are there any > more you'd like to add to that list? > > The second is for Foreman 1.9.0, which is a nice, short list at the > moment with just two unfixed issues. So far it looks like we won't have > a further release candidate, and can potentially release 1.9.0 in the > next couple of weeks. > > That's here: http://bit.ly/1FyhCnI > > Cheers,


Marek

> Just a reminder that we have two sets of important issues that I'd still
> appreciate help on.

Unfortunately I don't think there's been any take-up of these issues, so
I'll try again with a few keywords to help people find tickets they may
be able to help with.

> The first is for Foreman 1.8.3, which may well be the last in the series
> unless there are further important regressions or security issues.
>
> Those can be found at: http://bit.ly/1MfBtQm

  1. Authorisation and ActiveRecord related issue
    Bug #10819: PGError: ERROR: missing FROM-clause entry for table "hosts_reports" LINE 1 - Foreman

  2. Hostnames and domains issue when unattended: false
    Bug #11143: Domain removed from the hostname on host edit in !unattended mode - Foreman

  3. Editing hosts with "invalid" network interfaces
    Bug #10931: Editing of host with docker broken - Foreman

  4. Error from smart class parameter matchers
    Bug #11112: Matcher for unlisted attribute fails with "comparison of Array with Array failed" - Foreman

> The second is for Foreman 1.9.0, which is a nice, short list at the
> moment with just two unfixed issues. So far it looks like we won't have
> a further release candidate, and can potentially release 1.9.0 in the
> next couple of weeks.

This list is growing, and not getting shorter.

> That's here: http://bit.ly/1FyhCnI

  1. API parameter docs and responses missing ptables/taxonomies (easy)
    Bug #11175: organization and location for partition tables (ptable) not returned in json - Foreman

  2. select2 not working with compute profiles (important)
    Bug #11171: Select2 does not work with compute profiles - Foreman

  3. Debian package failures on foreman-installer
    Bug #11152: a2x: ERROR: "xsltproc" ... returned non-zero exit status 5 during Debian package build - Packaging - Foreman

  4. Warning message about already initialised constants
    Bug #11122: Already initialized constant exception after service startup - Foreman

  5. Taxonomy/authorisation issue (PR open)
    Bug #11187: Taxonomy selectors are empty even for users with assign permissions - Foreman

Help with regressions caused by features and bug fixes you wrote during
the last cycle is appreciated especially and will make me more likely to
trust your patches in future!

Thanks,

··· On 20/07/15 14:09, Dominic Cleal wrote:


Dominic Cleal
Red Hat Engineering