CentOS PaaS SIG meeting (2018-04-25)

[Troy Dawson]

Hello,
It's time for our weekly PaaS SIG sync-up meeting

Time: 1700 UTC - Wedensdays (date -d "1700 UTC")
Date: Today Wedensday, 25 April 2018
Where: IRC- Freenode - #centos-devel

Agenda:
- OpenShift Current Status
-- rpms
-- automation
- Training for new committee members
- Open Floor

Minutes from last meeting:
https://www.centos.org/minutes/2018/April/centos-devel.2018-04-18-17.00.log.html

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

CentOS PaaS SIG meeting (2018-04-18)

[Troy Dawson]

Hello,
It's time for our weekly PaaS SIG sync-up meeting

Time: 1700 UTC - Wedensdays (date -d "1700 UTC")
Date: Today Wedensday, 18 April 2018
Where: IRC- Freenode - #centos-devel

Agenda:
- OpenShift Current Status
-- rpms
-- automation
- Training for new committee members
-- How to get packages into repo's
-- How to create tags, build targets, and repo's
- New time for weekly meeting
- Open Floor

Minutes from last meeting:
https://www.centos.org/minutes/2018/April/centos-devel.2018-04-04-17.00.log.html

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: [CentOS-devel] CentOS Origin packages in testing for 3.7, 3.8 and 3.9

[Troy Dawson]

On Fri, Apr 13, 2018 at 8:42 AM, Rich Megginson <rmegg...@redhat.com> wrote:
> On 04/13/2018 09:39 AM, Troy Dawson wrote:
>>
>> On Fri, Apr 13, 2018 at 7:58 AM, Rich Megginson <rmegg...@redhat.com>
>> wrote:
>>>
>>> On 04/12/2018 07:32 AM, Troy Dawson wrote:
>>>>
>>>> We have origin packages for 3.7.2, 3.8.0 and 3.9.0.  We also have the
>>>> corresponding openshift-ansible packages. They have been put in our
>>>> testing repos.
>>>>
>>>> DO NOT USE ORIGIN 3.8.0, IT IS FOR UPGRADE PURPOSES ONLY
>>>>
>>>> These will not be released until *someone* has tested them.  So
>>>> please, someone, anyone, test them, and let us know.
>>>>
>>>> origin 3.9 testing
>>>> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/
>>>> origin-3.9.0-1.el7.git.0.ba7faec
>>>> openshift-ansible-3.9.0-0.53.0.git.1.af49d87.el7
>>>>
>>>> origin 3.8 testing
>>>> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin38/
>>>> origin-3.8.0-1.el7.git.0.dd1558c
>>>> openshift-ansible-3.8.37-1.git.1.151d57f.el7
>>>>
>>>> origin 3.7 testing
>>>> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/
>>>> origin-3.7.2-1.el7.git.0.cd74924
>>>> openshift-ansible-3.7.43-1.git.1.ed51ddd.el7
>>>>
>>>> Once again, test and let us know.  If you don't know who to send it
>>>> to, just reply to this email.
>>>
>>>
>>> Having some problems with logging Kibana certificates - issued with
>>> duplicate serial numbers - was
>>>
>>> https://github.com/openshift/origin/pull/18713/commits/95e262011438642410959914c3db9868c57739ff
>>> fixed in these 3.9 packages?
>>
>>  From what I can tell, yes.
>> Is it acting like it isn't?
>
>
> It is the same symptom - certificates are being issued with duplicate serial
> numbers - but if the fix is in origin 3.9, I'll see if there could possibly
> be another cause.
>

I just double checked the code itself, just in case some later commit
changed things.
The changes that are in
https://github.com/openshift/origin/pull/18713/commits/95e262011438642410959914c3db9868c57739ff
are in origin-3.9.0-1.el7.git.0.ba7faec
So ya, there must be some other cause.

Troy

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: [CentOS-devel] CentOS Origin packages in testing for 3.7, 3.8 and 3.9

[Troy Dawson]

On Fri, Apr 13, 2018 at 7:58 AM, Rich Megginson <rmegg...@redhat.com> wrote:
> On 04/12/2018 07:32 AM, Troy Dawson wrote:
>>
>> We have origin packages for 3.7.2, 3.8.0 and 3.9.0.  We also have the
>> corresponding openshift-ansible packages. They have been put in our
>> testing repos.
>>
>> DO NOT USE ORIGIN 3.8.0, IT IS FOR UPGRADE PURPOSES ONLY
>>
>> These will not be released until *someone* has tested them.  So
>> please, someone, anyone, test them, and let us know.
>>
>> origin 3.9 testing
>> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/
>> origin-3.9.0-1.el7.git.0.ba7faec
>> openshift-ansible-3.9.0-0.53.0.git.1.af49d87.el7
>>
>> origin 3.8 testing
>> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin38/
>> origin-3.8.0-1.el7.git.0.dd1558c
>> openshift-ansible-3.8.37-1.git.1.151d57f.el7
>>
>> origin 3.7 testing
>> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/
>> origin-3.7.2-1.el7.git.0.cd74924
>> openshift-ansible-3.7.43-1.git.1.ed51ddd.el7
>>
>> Once again, test and let us know.  If you don't know who to send it
>> to, just reply to this email.
>
>
> Having some problems with logging Kibana certificates - issued with
> duplicate serial numbers - was
> https://github.com/openshift/origin/pull/18713/commits/95e262011438642410959914c3db9868c57739ff
> fixed in these 3.9 packages?

>From what I can tell, yes.
Is it acting like it isn't?

Troy

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

CentOS Origin packages in testing for 3.7, 3.8 and 3.9

[Troy Dawson]

We have origin packages for 3.7.2, 3.8.0 and 3.9.0.  We also have the
corresponding openshift-ansible packages. They have been put in our
testing repos.

DO NOT USE ORIGIN 3.8.0, IT IS FOR UPGRADE PURPOSES ONLY

These will not be released until *someone* has tested them.  So
please, someone, anyone, test them, and let us know.

origin 3.9 testing
https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/
origin-3.9.0-1.el7.git.0.ba7faec
openshift-ansible-3.9.0-0.53.0.git.1.af49d87.el7

origin 3.8 testing
https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin38/
origin-3.8.0-1.el7.git.0.dd1558c
openshift-ansible-3.8.37-1.git.1.151d57f.el7

origin 3.7 testing
https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/
origin-3.7.2-1.el7.git.0.cd74924
openshift-ansible-3.7.43-1.git.1.ed51ddd.el7

Once again, test and let us know.  If you don't know who to send it
to, just reply to this email.

Thanks
Paas Sig Group

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

CentOS PaaS SIG meeting (2018-04-11)

[Troy Dawson]

Hello,
It's time for our weekly PaaS SIG sync-up meeting

Time: 1700 UTC - Wedensdays (date -d "1700 UTC")
Date: Today Wedensday, 11 April 2018
Where: IRC- Freenode - #centos-devel

Agenda:
- OpenShift Current Status
-- rpms
-- automation
- Training for new committee members
-- How to do manual builds of origin and openshift-ansible
- New time for weekly meeting
- Open Floor

Minutes from last meeting:
https://www.centos.org/minutes/2018/April/centos-devel.2018-04-04-17.00.log.html

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

CentOS PaaS SIG meeting (2018-04-04)

[Troy Dawson]

Hello,
It's time for our weekly PaaS SIG sync-up meeting

Time: 1700 UTC - Wedensdays (date -d "1700 UTC")
Date: Today Wedensday, 04 April 2018
Where: IRC- Freenode - #centos-devel

Agenda:
- OpenShift Current Status
-- rpms
-- automation
- Training for new committee members
- New time for weekly meeting
- Open Floor

Minutes from last meeting:
https://www.centos.org/minutes/2018/March/centos-devel.2018-03-28-17.00.log.html

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

CentOS PaaS SIG meeting (2018-03-28)

[Troy Dawson]

Hello,
It's time for our weekly PaaS SIG sync-up meeting
This week will be a bit different because we are going to devote alot
of the time to training new committee members.

Time: 1700 UTC - Wedensdays (date -d "1700 UTC")
Date: Today Wedensday, 28 March 2018
Where: IRC- Freenode - #centos-devel

Agenda:
- OpenShift Current Status
-- rpms
- Training for new committee members
- Open Floor

Minutes from last meeting:
https://www.centos.org/minutes/2018/March/centos-devel.2018-03-21-17.01.log.html

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: [CentOS-devel] CentOS PaaS SIG meeting (2018-03-21)

[Troy Dawson]

I didn't see anything saying that 3.9 was released yet.  Last I heard
they were working on some regressions.
If I missed it, can someone point me at it.  Maybe I just need a
better place to look than the mailling lists.


On Thu, Mar 22, 2018 at 11:01 PM, Jeffrey Zhang  wrote:
> hi, openshift origin 3.9 is released already,
> when centos-release-openshift-origin39 repo will be GA? it is still using
> alpha tag now.
>
> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/
>

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

CentOS PaaS SIG meeting (2018-03-21)

[Troy Dawson]

Hello,
It's time for our weekly PaaS SIG sync-up meeting

Time: 1700 UTC - Wedensdays (date -d "1700 UTC")
Date: Today Wedensday, 21 March 2018
Where: IRC- Freenode - #centos-devel

Agenda:
- OpenShift Current Status
-- rpms
-- Automated rpm building and Automated testing
-- Documentation
- Upcomming Committee Member Changes
- Open Floor

Minutes from last meeting:
https://www.centos.org/minutes/2018/March/centos-devel.2018-03-14-17.01.log.html

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

CentOS PaaS SIG meeting (2018-03-14) [DST Time reminder]

[Troy Dawson]

Hello,
It's time for our weekly PaaS SIG sync-up meeting

Time: 1700 UTC - Wedensdays (date -d "1700 UTC")
Date: Today Wedensday, 14 March 2018
Where: IRC- Freenode - #centos-devel

For those in the United States, remember that we are using UTC time,
and so the time is an hour later than it was last week.

Agenda:
- OpenShift Current Status
-- rpms
-- Automated rpm building and Automated testing
-- Multi-arch
-- Documentation
- Upcomming Committee Member Changes
- Open Floor

Minutes from last meeting:
https://www.centos.org/minutes/2018/March/centos-devel.2018-03-07-17.02.log.html

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Two New Committee Members Needed for CentOS PAAS SIG

[Troy Dawson]

Hi Ricardo,
I'm so sorry in the delay of replying.  I do appreciate the offer to be on
the committee.
What position(s) were you thinking of filling?

Troy


On Tue, Feb 27, 2018 at 8:05 AM, Ricardo Martinelli de Oliveira <
rmart...@redhat.com> wrote:

> Awesome! Thanks for the clarification!
>
> I'm interested in being part of the committee.
>
> On Tue, Feb 27, 2018 at 12:09 PM, Troy Dawson <tdaw...@redhat.com> wrote:
>
>> A few good questions have come up.
>> What are the responsibilities I would take on if I joined the committee?
>> Can I work on a sub-set of those responsibilities?
>>
>> Ari was in charge of keeping the jenkins cli working for our Paas.
>> He made sure the automatic builds continued building on their appointed
>> time.
>> He made sure that it was easy to do manual builds.
>> When OpenShift Origin code changed and broke the automation he would
>> jump in to fix the automation.
>> When OpenShift Origin code changed and broke the builds he would jump
>> in to fix the automation.
>>
>> Troy was in charge of orchestrating everything and making sure things
>> happened.
>> He held the weekly Paas Sig meeting.
>> He did the documentation.
>> He maintained the package repo's, and koji build targets.
>> He was the automation backup, so he helped Ari figure out the broken bits.
>> He was the central source of information.  So if people had questions,
>> or wanted to pass information on, it tended to go through him.  This
>> could certainly change.
>> He was the backup for pretty much everyone.  So as people came and
>> went from the Paas Sig, he would drop and/or gain new roles.
>>
>> These roles could certainly be broken up, so that others could take
>> certain parts.  We could certainly have more than two people take over
>> these roles.
>>
>>
>> On Mon, Feb 26, 2018 at 6:52 AM, Troy Dawson <tdaw...@redhat.com> wrote:
>> > Hello,
>> > Due to "Real Life" the following CentOS PAAS Sig committee members
>> > will be leaving the committee, on the following dates.  We will need
>> > to get replacements for them by those dates.
>> >
>> > Ari LiVigni - March 14th
>> > Troy Dawson - May 15th
>> >
>> > Ari is in charge of Automation.
>> > Troy is the committee chairman.
>> >
>> > The CentOS PAAS Sig has been very successful in bringing a free
>> > version of OpenShift to everyone.  These two people have been a very
>> > large part of that.  They will be missed.
>> >
>> > But it's time to look to the future.  We need people to step up and
>> > not only fill their shoes, but continue to move forward.
>> >
>> > Take a minute and see if this is something that you would want to do.
>> > If it is, please let us know.
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>
>
>
> --
> Ricardo Martinelli de Oliveira
> Senior Software Engineer
> T: +55 11 3524-6125 <+55%2011%203524-6126> | M: +55 11 9 7069-6531
> Av. Brigadeiro Faria Lima 3900, 8° Andar. São Paulo, Brasil
> <https://maps.google.com/?q=Av.+Brigadeiro+Faria+Lima+3900,+8%C2%B0+Andar.+S%C3%A3o+Paulo,+Brasil=gmail=g>
> .
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
>  Red Hat é reconhecida entre as melhores empresas para trabalhar no Brasil
> pelo *Great Place to Work*.
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Two New Committee Members Needed for CentOS PAAS SIG

[Troy Dawson]

A few good questions have come up.
What are the responsibilities I would take on if I joined the committee?
Can I work on a sub-set of those responsibilities?

Ari was in charge of keeping the jenkins cli working for our Paas.
He made sure the automatic builds continued building on their appointed time.
He made sure that it was easy to do manual builds.
When OpenShift Origin code changed and broke the automation he would
jump in to fix the automation.
When OpenShift Origin code changed and broke the builds he would jump
in to fix the automation.

Troy was in charge of orchestrating everything and making sure things happened.
He held the weekly Paas Sig meeting.
He did the documentation.
He maintained the package repo's, and koji build targets.
He was the automation backup, so he helped Ari figure out the broken bits.
He was the central source of information.  So if people had questions,
or wanted to pass information on, it tended to go through him.  This
could certainly change.
He was the backup for pretty much everyone.  So as people came and
went from the Paas Sig, he would drop and/or gain new roles.

These roles could certainly be broken up, so that others could take
certain parts.  We could certainly have more than two people take over
these roles.


On Mon, Feb 26, 2018 at 6:52 AM, Troy Dawson <tdaw...@redhat.com> wrote:
> Hello,
> Due to "Real Life" the following CentOS PAAS Sig committee members
> will be leaving the committee, on the following dates.  We will need
> to get replacements for them by those dates.
>
> Ari LiVigni - March 14th
> Troy Dawson - May 15th
>
> Ari is in charge of Automation.
> Troy is the committee chairman.
>
> The CentOS PAAS Sig has been very successful in bringing a free
> version of OpenShift to everyone.  These two people have been a very
> large part of that.  They will be missed.
>
> But it's time to look to the future.  We need people to step up and
> not only fill their shoes, but continue to move forward.
>
> Take a minute and see if this is something that you would want to do.
> If it is, please let us know.

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Two New Committee Members Needed for CentOS PAAS SIG

[Troy Dawson]

Hello,
Due to "Real Life" the following CentOS PAAS Sig committee members
will be leaving the committee, on the following dates.  We will need
to get replacements for them by those dates.

Ari LiVigni - March 14th
Troy Dawson - May 15th

Ari is in charge of Automation.
Troy is the committee chairman.

The CentOS PAAS Sig has been very successful in bringing a free
version of OpenShift to everyone.  These two people have been a very
large part of that.  They will be missed.

But it's time to look to the future.  We need people to step up and
not only fill their shoes, but continue to move forward.

Take a minute and see if this is something that you would want to do.
If it is, please let us know.

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: registry.access.redhat.com/openshift3/ose:latest wrongly tagged?

[Troy Dawson]

For the official OpenShift Container Platform (OCP) images, you should
*not* use "latest"

The definition of "latest" for docker images is "The last image pushed
into the registry with that name."

As Jonathan showed, there are alot of images for openshift3/ose, and
all sorts of different versions.  OCP is the enterprise version of
Origin.  Because of that, we still support the older versions, and we
have updates for those older versions.
Because we have updates for those older versions, the "latest" tag,
gets changed quite a bit, and goes to all different types of versions.

What should you use if you want the latest 3.5 image?
openshift3/ose:v3.5

The v tag is the latest image for that version.
So if you want the latest 3.4 image, you get openshift3/ose:v3.4 for
3.3 get openshift3/ose:v3.3 and so forth.

Is this documented?
Documentation is currently being updated and we should have a URL for
you in a week or two with better explanation than this.  We apologize
that this wasn't documented before.

On a different note, since the registry handles both v1 and v2
registry commands, you can query the registry with curl to get the
listings, along with the image sha sum.  I like this way because I can
then see which tags go with which image.

$ curl -k http://registry.access.redhat.com/v1/repositories/openshift3/ose/tags
| python -m json.tool
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  8798  100  87980 0  47409  0 --:--:-- --:--:-- --:--:-- 47556
{
"latest": 
"38d0523d03b7c155031f20ff54c47836bef577bc1c3392de9cfcc549b0da77d3",
"v3.1": "241393b078ca6bfe9f83bad824bd41692eecc6fd2d641b9f7ba34df319bd2536",
"v3.1.0.4":
"62208f15133798af253a651386ae2753da9130fcc68f1863cbd735c547356173",
"v3.1.0.4-1":
"2eb816e9a7d05f6d5816be42ba21cf272770a9be1d15e839e7474c0541a40bc7",
...
"v3.4.1.7":
"c729d138d383fb273a520341e5671b4e2fcd2ad77c062b6e9ad725fd06af33ff",
"v3.4.1.7-2":
"c729d138d383fb273a520341e5671b4e2fcd2ad77c062b6e9ad725fd06af33ff",
"v3.5": "38d0523d03b7c155031f20ff54c47836bef577bc1c3392de9cfcc549b0da77d3",
"v3.5.5.5":
"ace03132c45fd6c32233f5b588db2812e341cadf46a4b2a9298699c64f0f81ac",
"v3.5.5.5-2":
"ace03132c45fd6c32233f5b588db2812e341cadf46a4b2a9298699c64f0f81ac",
"v3.5.5.8":
"38d0523d03b7c155031f20ff54c47836bef577bc1c3392de9cfcc549b0da77d3",
"v3.5.5.8-3":
"38d0523d03b7c155031f20ff54c47836bef577bc1c3392de9cfcc549b0da77d3"
}

You'll notice that right now, "latest" is actually pointing to the
latest 3.5 image.  But that is only because the 3.5 image was the last
image pushed up to the registry.

I hope this helps.  Like I said, documentation is coming.  I'm sorry
it wasn't up before now.

Troy



On Tue, May 9, 2017 at 11:56 AM, David Schweikert  wrote:
> Hi Jonathan,
>
> On Tue, May 09, 2017 at 09:36:48 -0700, Jonathan Yu wrote:
>> I've confirmed the problem using the skopeo tool and am asking around
>> about a resolution. The build date looks pretty recent, so it's
>> possible that the old version was rebuilt and therefore ended up as
>> the "latest" - give us some time to investigate & we'll provide an
>> update here.
>
> OK, thanks for the very quick reaction!
>
> Also, thanks for the hint about the skopeo tool. Looks very useful.
>
> Cheers
> David
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Origin 1.4

[Troy Dawson]

They already have.  Maybe you have a stale yum cache, and/or possibly
need a subscription-manager refresh

subscription-manager refresh
yum clean all
rm -rf /var/cache/yum/x86_64/

yum --enablerepo=rhel-7-server-extras-rpms list docker
...
docker.x86_64 2:1.12.5-14.el7   rhel-7-server-extras-rpms
...

On Thu, Jan 19, 2017 at 3:59 PM, Lionel Orellana  wrote:
> This version requires Docker 1.12.
>
> I can't find Docker 1.12 in the rhel-7-server-extras-rpms repository. It's
> only there as docker-latest.
>
> -bash-4.2$ sudo yum list available docker-latest
> Available Packages
> docker-latest.x86_64
> 1.12.3-10.el7
> rhel-7-server-extras-rpms
> -bash-4.2$ sudo yum list available docker
> Available Packages
> docker.x86_64
> 2:1.10.3-59.el7
> rhel-7-server-extras-rpms
> -bash-4.2$
>
> Anyone knows if RedHat will update those docker packages as well?
>
> Thanks
>
> Lionel.
>
>
>
> On 20 January 2017 at 01:00, Daniel Barker  wrote:
>>
>> It looks like it's taken a couple weeks to get rpms out in the past. Is
>> that still an accurate estimate?
>>
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Bad CentOS packages

[Troy Dawson]

Hi Alex,
We're still working on our CentOS workflow / testing.  The tests that
let this through didn't check the version the binary thought it was
running.  That test is being updated.  We'd much rather find and fix
an issue before we push it all the way out, due to this delay of
pushing to a released repo.

If possible, you could install the fixed/updated package from the
-testing repo via yum

yum --enablerepo=centos-openshift-origin-testing update "*origin*"

It's not ideal, but it's currently the only workaround I have.


On Thu, Jun 23, 2016 at 10:55 AM, Alex Wauck  wrote:
> Whoops, I didn't see the rest of the thread "define openshift origin version
> (stable 1.2.0) for Ansible install" before sending this.  I guess the fix is
> on the way.  It's still kind of annoying that this is still failing a day
> later.
>
> On Thu, Jun 23, 2016 at 10:54 AM, Alex Wauck  wrote:
>>
>> The current latest packages in the CentOS repository (as installed by
>> openshift-ansible) are 1.2.0-2.el7.  The version of OpenShift in these
>> packages is actually v1.2.0-rc1-13-g2e62fab.  This causes OpenShift to
>> attempt to download an origin-pod image with that tag, which does not exist.
>> This prevents all pods from starting.  The repository does not appear to
>> contain the last known good packages, which are 1.2.0-1.el7.
>>
>> As a result, I now have a cluster with 5 good nodes and one bad node that
>> I can't fix.
>>
>> Here is the repo config:
>>
>> [centos-openshift-origin]
>> name=CentOS OpenShift Origin
>> baseurl=http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/
>> enabled=1
>> gpgcheck=1
>> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-PaaS
>>
>> [centos-openshift-origin-testing]
>> name=CentOS OpenShift Origin Testing
>> baseurl=http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin/
>> enabled=0
>> gpgcheck=0
>> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-PaaS
>>
>> [centos-openshift-origin-debuginfo]
>> name=CentOS OpenShift Origin DebugInfo
>> baseurl=http://debuginfo.centos.org/centos/7/paas/x86_64/
>> enabled=0
>> gpgcheck=1
>> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-PaaS
>>
>> [centos-openshift-origin-source]
>> name=CentOS OpenShift Origin Source
>> baseurl=http://vault.centos.org/centos/7/paas/Source/openshift-origin/
>> enabled=0
>> gpgcheck=1
>> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-PaaS
>>
>> --
>>
>> Alex Wauck // DevOps Engineer
>>
>> E X O S I T E
>> www.exosite.com
>>
>> Making Machines More Human.
>
>
>
>
> --
>
> Alex Wauck // DevOps Engineer
>
> E X O S I T E
> www.exosite.com
>
> Making Machines More Human.
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Re-download old RPMs of OpenShift?

[Troy Dawson]

Currently, no.
copr keeps only the latest builds and this caught us off-guard when we
switched to 1.1.
Someone already opened this as an issue on github.
https://github.com/openshift/origin/issues/6695

Here is the reply

It looks like copr keeps only the latest builds.
If you want to grab any of the src.rpm's of any of the builds you can
find them in the projects builds area.
https://copr.fedoraproject.org/coprs/maxamillion/origin-next/builds/
If you look at the 1.0.8 build page, you will see that the src.rpm
came from here.
https://tdawson.fedorapeople.org/copr/openshift/origin-1.0.8-0.git.7227.8f1868d.el7.src.rpm
You should be able to rebuild the packages from the source rpm.


We are working on getting OpenShift Origin in EPEL and CentOS so this
issue won't be as dramatic.
It already is in Fedora, thanks to Adam Miller.



On Fri, Jan 29, 2016 at 7:28 AM, v  wrote:
> Dear Mailing List,
>
> is it possible to download old RPMs of OpenShift? The official repo only has 
> versions starting form 1.1.
>
> The reason why I am asking is because we are trying to set up a test cluster 
> and practice the update to 1.1 there before applying the update to our live 
> cluster.
>
> To be more specific, we are looking for the following RPMs:
> origin-1.0.6-0.git.5812.e2a02a8.el7.centos.x86_64
> origin-clients-1.0.6-0.git.5812.e2a02a8.el7.centos.x86_64
> origin-master-1.0.6-0.git.5812.e2a02a8.el7.centos.x86_64
> origin-node-1.0.6-0.git.5812.e2a02a8.el7.centos.x86_64
> origin-sdn-ovs-1.0.6-0.git.5812.e2a02a8.el7.centos.x86_64
> tuned-profiles-origin-node-1.0.6-0.git.5812.e2a02a8.el7.centos.x86_64
>
> Regards,
> v
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users