Bug 1866597
Summary: | Example repo in oc should be updated since https://github.com/sclorg/ruby-ex cannot work with ruby:2.7 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Wenjing Zheng <wzheng> |
Component: | Samples | Assignee: | Gabe Montero <gmontero> |
Status: | CLOSED ERRATA | QA Contact: | XiuJuan Wang <xiuwang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.6 | CC: | aos-bugs, jokerman, maszulik, mfojtik, pvalena, tnozicka |
Target Milestone: | --- | ||
Target Release: | 4.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: the 'oc new-app' example included in the message produced by 'oc new-project' used upstream ruby templates instead of officially supported ruby templates
Consequence: intermittent instability due to upstream development would result in the 'oc new-app' example failing if the user tried to use it.
Fix: the 'oc new-app' example included in the message produced by 'oc new-project' now uses and officially supported ruby template
Result: the 'oc new-app' example included in the message produced by 'oc new-project' should work and be immune to intermittent upstream development.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-10-27 16:25:22 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Wenjing Zheng
2020-08-06 02:39:50 UTC
Note that this is actually workaroundable using custom `assemble` script [1] for either the app, or including the required 'capabilitiy' in s2i-ruby-container. [1] https://github.com/sclorg/rails-ex/issues/129 Technically speaking, direct use of https://github.com/sclorg/ruby-ex.git is not an officially supported sample of OCP. It is the upstream representation of samples shipped by samples operator in OCP. In fact, we've gone through some amount of effort in our e2e's to stop validation of new-app against upstream repo's, as they invariable can be "under development" at various times, and have intermittent inconsistencies as noted by this latest bug, and instead our e2e's now new-app against the templates we officially ship. The closest alternative to that new-app is most likely the template at https://github.com/openshift/cluster-samples-operator/blob/master/assets/operator/ocp-x86_64/rails/templates/rails-postgresql-example.json And it you look there, the BuildConfig uses ruby:2.5 - https://github.com/openshift/cluster-samples-operator/blob/master/assets/operator/ocp-x86_64/rails/templates/rails-postgresql-example.json#L120 So the new-app call instead would be: oc new-app rails-postgresql-example My plan is to keep this bz under samples, but change the new-project message in `oc` to move off of direct upstream repo usage. The SCL folks can sort out their ruby versioning issues independently / in parallel as part of their dev cycle. As I research history and refresh my old memory, some of this came up in https://bugzilla.redhat.com/show_bug.cgi?id=1774318 ... FIPS was the fly in the ointment back then. Never did get an answer to my question in https://bugzilla.redhat.com/show_bug.cgi?id=1774318#c2 So I'm going to fix my error back then and use `rails-postgresql-example` re: https://github.com/openshift/oc/pull/170/files#r348680799 $oc new-project xiuwang1 Now using project "xiuwang1" on server "https://api.juzhao-osp.0817-un8.qe.rhcloud.com:6443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app rails-postgresql-example to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: kubectl create deployment hello-node --image=gcr.io/hello-minikube-zero-install/hello-node $oc new-app rails-postgresql-example $oc get builds NAME TYPE FROM STATUS STARTED DURATION rails-postgresql-example-1 Source Git@df00e00 Complete 2 minutes ago 2m2s Verified on version Client Version: 4.6.0-0.nightly-2020-08-18-030245 Server Version: 4.6.0-0.nightly-2020-08-17-184032 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196 |