getting centos7 into bootstrap and gitlab CI

[joeg at catalyst.net.nz]

On 4/05/19 11:36 AM, Christof Schmitt via samba-technical wrote:
> On Wed, May 01, 2019 at 01:36:36PM +1200, Andrew Bartlett wrote:
>> On Tue, 2019-04-30 at 16:04 -0700, Christof Schmitt wrote:
>>> On Wed, May 01, 2019 at 06:45:42AM +1200, Andrew Bartlett via samba-technical wrote:
>>>> On Tue, 2019-04-30 at 16:10 +0200, Andreas Schneider via samba-
>>>> technical wrote:
>>>>> On Tuesday, April 30, 2019 3:58:45 PM CEST Rowland Penny wrote:
>>>>>>  
>>>>>> Quite right EPEL doesn't have python34-crypto or python34-dns, but
>>>>>> it
>>>>>> does have these:
>>>>>>
>>>>>> https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/epel/7
>>>>>> /x86_64/P
>>>>>> ackages/p/python36-crypto-2.6.1-16.el7.x86_64.rpm
>>>>>> https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/epel/7
>>>>>> /x86_64/
>>>>>> Packages/p/python36-dns-1.15.0-8.el7.noarch.rpm
>>>>> I think we are more lucky once RHEL 7.7 is out :-)
>>>> Can we use this:
>>>> https://centos.pkgs.org/7/epel-x86_64/python36-3.6.6-5.el7.x86_64.rpm.html
>>>>
>>>> It would be very helpful if we could have a python 3.6 baseline.
>>> I have a RHEL7 system and these python 3.6 rpms installed from EPEL:
>>>
>>> $ rpm -qa | grep python36
>>> python36-libs-3.6.6-5.el7.x86_64
>>> python36-crypto-2.6.1-16.el7.x86_64
>>> python36-devel-3.6.6-5.el7.x86_64
>>> python36-3.6.6-5.el7.x86_64
>>> python36-dns-1.15.0-8.el7.noarch
>>>
>>> That seems sufficient to run the AD testenvs on master. If those can be
>>> added to a CentOS7 image on gitlab, that might be sufficient to run the
>>> tests.
>> So I guess it should be mostly a matter of adding EPEL repo during
>> bootstrap.  Currently it runs the same thing on all RPM based systems,
>> but this can be changed.
>>
>> See bootstrap/config.py
> I tried to fixup the patches from Andreas to use Python 3.6 in CentOS7
> and force the new image build:
> https://gitlab.com/samba-team/devel/samba/pipelines/59674602
>
> The centos7 image build seems to succeed, but then the centos7-samba-o3
> build does not start and only has:
>
> ERROR: Preparation failed: invalid reference format (executor_docker.go:168:0s)
> Will be retried in 3s ...
> ERROR: Job failed (system failure): invalid reference format (executor_docker.go:168:0s)
>
> Does that mean there is something wrong with the image or the tag?

Hi Christof:

This error is because $SAMBA_CI_CONTAINER_IMAGE_centos7 was not defined
in .gitlab-ci.yml, so you get empty string for image.

Also, your private jobs get stuck, because we replace the `private` tag
to `samba-ci-private` but we can not have both.

I fixed both issues and pushed to your branch, ci is in process now:

https://gitlab.com/samba-team/devel/samba/pipelines/59867359

>
> Christof

-- 
Joe Guo
joeg at catalyst.net.nz
Catalyst IT