[releng] Issue #7217: new FLIBS container release for all container images

[Dusty Mabe]

dustymabe reported a new issue against the project: `releng` that you are following:
``
These used to be done every two weeks right after the Atomic Host releases. Some ownership
of this has changed hands recently, but I believe it is sufficiently automated. Can we
please do an ad-hoc release of any new containers and also any existing containers with
rebuilt content (i.e. security updates). 
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Honza Horak]

hhorak added a new comment to an issue you are following:
``
I'm +1 for this, automation is very important in containers work.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Giuseppe Scrivano]

gscrivano added a new comment to an issue you are following:
``
+1
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Honza Horak]

hhorak added a new comment to an issue you are following:
``
As for the ad-hoc release, few changes are blocked on the new s2i-core image on our side,
that has been in candidate registry for few weeks now and we'd like to see it in
official registry.. So, it would help us a lot if this image (and others from candidate)
are pushed to proper repo soon..
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Giuseppe Scrivano]

gscrivano added a new comment to an issue you are following:
``
I'd like to see "docker" and "cri-o" to be pushed to
registry.fedoraproject.org/f27
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Mohan Boddu]

mohanboddu added a new comment to an issue you are following:
``
Automation of releasing child container images is not completed in prod, @puiterwijk is
working on it. Once thats done, we can be able release child container images.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
@mohanboddu - any ETA on that work?

While we wait is it possible to manually release select images (in this case `s2i-core`,
`docker`, and `cri-o`)?.  I know manually doing things is not ideal, but it did allow us
to ship things in the past (thanks @maxamillion) 
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Jason Brooks]

jasonbrooks added a new comment to an issue you are following:
``
I really need all the kubernetes- images pushed asap, there's been a bug in them
waiting for release for some time now:
https://github.com/projectatomic/atomic-system-containers/issues/156
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Steve Milner]

smilner added a new comment to an issue you are following:
``
:thumbsup: 
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Steve Milner]

smilner added a new comment to an issue you are following:
``
Related:
- https://github.com/projectatomic/atomic-system-containers/issues/155
- https://github.com/projectatomic/atomic-system-containers/issues/43
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Steve Milner]

smilner added a new comment to an issue you are following:
``
FYI This is being discussed and looked at in IRC by @maxamillion and @mohanboddu.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
From IRC:

```
14:42:25    dustymabe | do you have any idea when that might make it to prod?
https://pagure.io/releng/issue/7217#comment-485157
14:43:19   puiterwijk | I am going to say by end of tomorrow is feasible.
14:43:37    dustymabe | so possible container relese tomorrow? do you mind updating the
ticket with that info?
```
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Steve Milner]

smilner added a new comment to an issue you are following:
``
>  From IRC:
>  14:42:25    dustymabe | do you have any idea when that might make it to prod?
> https://pagure.io/releng/issue/7217#comment-485157
>  14:43:19   puiterwijk | I am going to say by end of tomorrow is feasible.
>  14:43:37    dustymabe | so possible container relese tomorrow? do you mind updating the
> ticket with that info?
>  
>  
@puiterwijk  What was the outcome from the above conversation?
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``

>  @puiterwijk  What was the outcome from the above conversation?
>  
He's going to try to have it by the end of the day today.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Giuseppe Scrivano]

gscrivano added a new comment to an issue you are following:
``
any update on this?
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Honza Horak]

hhorak added a new comment to an issue you are following:
``
Any update on this now?
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Jens Neuhalfen]

neuhalje added a new comment to an issue you are following:
``
Is there any way I can help/support in this matter? I am a bit concerned that (at least)
two "blocker type" bugs cannot be resolved bc. of a missing release
automation.

* https://github.com/projectatomic/atomic-system-containers/issues/156
* https://github.com/projectatomic/atomic-system-containers/issues/155

``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Steve Milner]

smilner added a new comment to an issue you are following:
``
@neufeind we're trying to pin down more help in IRC now as well.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Steve Milner]

smilner added a new comment to an issue you are following:
``
[This](https://fedoramagazine.org/protect-fedora-system-meltdown/) caused a delay.
Speaking with @puiterwijk and @dustymabe this morning the belief is this should be fixed
by Friday evening.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Jens Neuhalfen]

neuhalje added a new comment to an issue you are following:
``
@smilner Where on IRC?
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Steve Milner]

smilner added a new comment to an issue you are following:
``
@neuhalje Freenode in #fedora-releng
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
update from patrick:

```
18:20:54      puiterwijk | dustymabe: okay, I think the FLIBS rebuild stuff is now setup
in the infra. I'll be working with Rob/Mohan │ eroji
                         | to get a cycle running soon.                                   
                                           │ evilissimo
18:21:05      puiterwijk | However, I'm probably going to try to get it run tomorrow  
                                               │ fabianvf
18:21:37      puiterwijk | (the reason being that I'd like to be there for the first
time we run it in case it fails, and I'm going   │ fkautz
                         | to head out in 10 minutes) 
```
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
we hit some issues when running through the first build on friday. THose have been fixed
and the builds are progressing, hopefully to be released today! 
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Steve Milner]

smilner added a new comment to an issue you are following:
``
@dustymabe thanks for the update.

@dustymabe and @puiterwijk please keep us posted via this issue. Thanks!
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
TL;DR - your images should be in the registry and we'll do another release next week
after the two week atomic release. 

ok here is the latest update: all images have been rebuilt and pushed to the registry
except s2i-base and ones that layer on top of it (there was some build error with them).

we didn't notice until later that the base images did not get pushed (so the base
images are not new at this time, but the layered images are). We will do another FLIBS
release next week including base images and will send a proper email. 


``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Tomas Tomecek]

ttomecek added a new comment to an issue you are following:
``
Dusty, thanks for update!

This should fix the s2i-base failure:
https://src.fedoraproject.org/container/s2i-base/c/cd22158f287f2bc5f5fed9...
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Honza Horak]

hhorak added a new comment to an issue you are following:
``
Thanks dusty and tomas as well!

So, how is it gonna work now? My understanding of
https://fedoraproject.org/wiki/Container:Guidelines is that the images will get built
automatically and be pushed to stable registry every two weeks, right?

Further thinking... since docker is based on layering and it allows us to share some
common parts for more containers, one thing I'm thinking on is how to build containers
on updated base image -- e.g. the case with the s2i-base that Tomas mentions above -- if
we change something in s2i-base image and depended containers use `FROM
registry.fedoraproject.org/f26/s2i-base:latest` per guidelines, are we not able to build
such depended containers within the two weeks? Or am I misunderstanding something?
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
>  Thanks dusty and tomas as well!
>  
and thanks to @puiterwijk who mainly pushed this through the last mile

>  So, how is it gonna work now? My understanding of
> https://fedoraproject.org/wiki/Container:Guidelines is that the images will get built
> automatically and be pushed to stable registry every two weeks, right?
>  
that is correct. My understanding is that even if they don't have new changes they
will get rebuilt anyways on top of a newer base image (with possible security updates). 

>  Further thinking... since docker is based on layering and it allows
> us to share some common parts for more containers, one thing I'm thinking on is how to
> build containers on updated base image -- e.g. the case with the s2i-base that Tomas
> mentions above -- if we change something in s2i-base image and depended containers use
> FROM registry.fedoraproject.org/f26/s2i-base:latest per guidelines, are we not able to
> build such depended containers within the two weeks? Or am I misunderstanding something?
>  
The build process considers this and builds layered images after dependent layers have
been built. If a new s2i-base container is built during a rebuild then new s2i-base-layer1
container would build on top of that s2i-base container that was just built. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Honza Horak]

hhorak added a new comment to an issue you are following:
``
Sooo, any updates here? I still don't see the automatic two-week-cadence push
happening -- e.g. registry.fedoraproject.org/f26/s2i-core still not available, although
built for looong time..
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Clement Verna]

cverna added a new comment to an issue you are following:
``
@mohanboddu , the blocking containers are now built for f27 see [atomic
#424](https://pagure.io/atomic-wg/issue/424).

Can run the release playbook.

Thanks
Clément
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Mohan Boddu]

mohanboddu added a new comment to an issue you are following:
``
@cverna Okay, let me run that, thanks
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Clement Verna]

cverna added a new comment to an issue you are following:
``
Ok so I think we can close this ticket. :fireworks: .

Let's try to do another one in 2 weeks :)
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
thanks @cverna and @mohanboddu - closing ticket now!
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7217

[Dusty Mabe]

The status of the issue: `new FLIBS container release for all container images` of
project: `releng` has been updated to: Closed as Fixed by dustymabe.

https://pagure.io/releng/issue/7217