1.8.0 final delayed

The original scheduled date for 1.8.0 final was tomorrow (Tue 21st) but
I'll delay it by a further week to get fixes for these two issues found
in RC3:

  1. Bug #10111: "primary_interface is nil" error when editing unmanaged host - Foreman unmanaged host edit
    error, PR open and needs reviewing

  2. http://projects.theforeman.org/issues/10186 network error with
    vSphere distributed port groups, needs a patch (Francois has been
    working on it)

Schedule at
http://projects.theforeman.org/projects/foreman/wiki/Foreman_18_Schedule
has been updated.

I had also expected progress on #10105 (hammer interface errors), which
will now probably target 1.8.1 with a new version of apipie-bindings(?),
as might #10030 (vSphere template errors).

Issues still remain on the ticket list (http://bit.ly/172VbxZ), any help
is appreciated - aside from a couple of people, not much has been
forthcoming, and I'd like to see this change please.

··· -- Dominic Cleal Red Hat Engineering

Another update, as these issues are still unfixed and put Tuesday 28th
April at risk again.

> 1. Bug #10111: "primary_interface is nil" error when editing unmanaged host - Foreman unmanaged host edit
> error, PR open and needs reviewing

PR needs updating (Daniel).

> 2. http://projects.theforeman.org/issues/10186 network error with
> vSphere distributed port groups, needs a patch (Francois has been
> working on it)

PR's open, but needs more testing and discussion between Shlomi and
Francois to figure out what's the correct behaviour.

> I had also expected progress on #10105 (hammer interface errors), which
> will now probably target 1.8.1 with a new version of apipie-bindings(?)

#10105's not merged in apipie-bindings, but #3849 has been merged to
hammer-cli-foreman which should also fix the issue. When will Hammer
0.1.5 be released, perhaps we should include that in .0 or .1? (The
regression fix merged for #10215 is important too.)

> as might #10030 (vSphere template errors).

PR can't be merged in its current form as it's dependent on an unmerged
change to fog, needs rewriting for 1.8.

> Issues still remain on the ticket list (http://bit.ly/172VbxZ), any help
> is appreciated - aside from a couple of people, not much has been
> forthcoming, and I'd like to see this change please.

Still a few issues on this list that can be picked up!

··· On 20/04/15 15:57, Dominic Cleal wrote:


Dominic Cleal
Red Hat Engineering

> Another update, as these issues are still unfixed and put Tuesday 28th
> April at risk again.

I think we're on track again for Tues/Weds for 1.8.0 final.

>> 2. http://projects.theforeman.org/issues/10186 network error with
>> vSphere distributed port groups, needs a patch (Francois has been
>> working on it)
>
> PR's open, but needs more testing and discussion between Shlomi and
> Francois to figure out what's the correct behaviour.

I think we're pretty much settled on accepting this, it just needs an
update to fix a couple of style issues.

>> I had also expected progress on #10105 (hammer interface errors), which
>> will now probably target 1.8.1 with a new version of apipie-bindings(?)
>
> #10105's not merged in apipie-bindings

Merged, we'll pull apipie-bindings 0.0.13 into 1.8.

> but #3849 has been merged to
> hammer-cli-foreman which should also fix the issue. When will Hammer
> 0.1.5 be released, perhaps we should include that in .0 or .1? (The
> regression fix merged for #10215 is important too.)

Hammer 0.2.0 is released, debs are done, but RPMs are blocked on
hammer_cli_foreman_tasks which has dependencies on ~> 0.1.x. As soon as
that's resolved we can put those packages through nightlies and into 1.8.0.

>> as might #10030 (vSphere template errors).
>
> PR can't be merged in its current form as it's dependent on an unmerged
> change to fog, needs rewriting for 1.8.

Not done, probably going to miss 1.8.0 now.

>> Issues still remain on the ticket list (http://bit.ly/172VbxZ), any help
>> is appreciated - aside from a couple of people, not much has been
>> forthcoming, and I'd like to see this change please.
>
> Still a few issues on this list that can be picked up!

And still!

··· On 23/04/15 09:41, Dominic Cleal wrote: > On 20/04/15 15:57, Dominic Cleal wrote:


Dominic Cleal
Red Hat Engineering

>> Another update, as these issues are still unfixed and put Tuesday 28th
>> April at risk again.
>
> I think we're on track again for Tues/Weds for 1.8.0 final.

Everything I had been expecting has now been completed in time, we're
now go to release 1.8.0 tomorrow, Tuesday 28th.

>>> 2. http://projects.theforeman.org/issues/10186 network error with
>>> vSphere distributed port groups, needs a patch (Francois has been
>>> working on it)
>>
>> PR's open, but needs more testing and discussion between Shlomi and
>> Francois to figure out what's the correct behaviour.
>
> I think we're pretty much settled on accepting this, it just needs an
> update to fix a couple of style issues.

Merged, thanks Francois.

>> but #3849 has been merged to
>> hammer-cli-foreman which should also fix the issue. When will Hammer
>> 0.1.5 be released, perhaps we should include that in .0 or .1? (The
>> regression fix merged for #10215 is important too.)
>
> Hammer 0.2.0 is released, debs are done, but RPMs are blocked on
> hammer_cli_foreman_tasks which has dependencies on ~> 0.1.x. As soon as
> that's resolved we can put those packages through nightlies and into 1.8.0.

Finished off today, tests passed.

>>> as might #10030 (vSphere template errors).
>>
>> PR can't be merged in its current form as it's dependent on an unmerged
>> change to fog, needs rewriting for 1.8.
>
> Not done, probably going to miss 1.8.0 now.
>
>>> Issues still remain on the ticket list (http://bit.ly/172VbxZ), any help
>>> is appreciated - aside from a couple of people, not much has been
>>> forthcoming, and I'd like to see this change please.
>>
>> Still a few issues on this list that can be picked up!
>
> And still!

I'm going to mark these for 1.8.1 in the hope that they get picked up
for that release instead.

··· On 24/04/15 15:01, Dominic Cleal wrote: > On 23/04/15 09:41, Dominic Cleal wrote: >> On 20/04/15 15:57, Dominic Cleal wrote:


Dominic Cleal
Red Hat Engineering

Moved to http://bit.ly/1J3rpWK

··· On 27/04/15 10:59, Dominic Cleal wrote: > On 24/04/15 15:01, Dominic Cleal wrote: >> On 23/04/15 09:41, Dominic Cleal wrote: >>>> Issues still remain on the ticket list (http://bit.ly/172VbxZ), any help >>>> is appreciated - aside from a couple of people, not much has been >>>> forthcoming, and I'd like to see this change please. >>> >>> Still a few issues on this list that can be picked up! >> >> And still! > > I'm going to mark these for 1.8.1 in the hope that they get picked up > for that release instead.


Dominic Cleal
Red Hat Engineering

1.8.0 has now shipped (see foreman-announce).

Thanks everyone.

··· On 27/04/15 10:59, Dominic Cleal wrote: > On 24/04/15 15:01, Dominic Cleal wrote: >> > On 23/04/15 09:41, Dominic Cleal wrote: >>> >> Another update, as these issues are still unfixed and put Tuesday 28th >>> >> April at risk again. >> > >> > I think we're on track again for Tues/Weds for 1.8.0 final. > Everything I had been expecting has now been completed in time, we're > now go to release 1.8.0 tomorrow, Tuesday 28th.


Dominic Cleal
Red Hat Engineering