Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1300214 - Failed to build with openshift/golang-ex
Failed to build with openshift/golang-ex
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Templates (Show other bugs)
3.1.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Rodolfo Carvalho
XiuJuan Wang
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-20 04:47 EST by Wenjing Zheng
Modified: 2016-05-12 12:26 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-12 12:26:58 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1064 normal SHIPPED_LIVE Important: Red Hat OpenShift Enterprise 3.2 security, bug fix, and enhancement update 2016-05-12 16:19:17 EDT

  None (edit)
Description Wenjing Zheng 2016-01-20 04:47:20 EST
Description of problem:
Below error appears when build with openshift/golang-ex:
github.com/openshift/golang-ex/models
github.com/openshift/golang-ex/controllers
# github.com/openshift/golang-ex/controllers
../github.com/openshift/golang-ex/controllers/app.go:79: this.TplNames undefined (type *AppController has no field or method TplNames)
../github.com/openshift/golang-ex/controllers/longpolling.go:38: this.TplNames undefined (type *LongPollingController has no field or method TplNames)
../github.com/openshift/golang-ex/controllers/longpolling.go:45: this.TplNames undefined (type *LongPollingController has no field or method TplNames)
../github.com/openshift/golang-ex/controllers/longpolling.go:66: this.ServeJson undefined (type *LongPollingController has no field or method ServeJson)
../github.com/openshift/golang-ex/controllers/longpolling.go:76: this.ServeJson undefined (type *LongPollingController has no field or method ServeJson)
../github.com/openshift/golang-ex/controllers/websocket.go:41: this.TplNames undefined (type *WebSocketController has no field or method TplNames)
F0120 04:07:53.554946       1 builder.go:185] Error: build error: The command '/bin/sh -c go-wrapper install' returned a non-zero code: 2

Version-Release number of selected component (if applicable):
https://github.com/openshift/golang-ex
openshift v3.1.1.5
kubernetes v1.1.0-origin-1107-g4c8e6f4
etcd 2.1.2

How reproducible:
Always

Steps to Reproduce:
1. Create a project
2. Build with the forked repo
$oc new-app -f  https://raw.githubusercontent.com/openshift/golang-ex/master/openshift/templates/beego.json  -p  SOURCE_REPOSITORY_URL=https://github.com/openshift/golang-ex
 3. Check the build status status
$oc get builds

Actual results:
Build failed with errors in build log.

Expected results:
It should succeed.
Comment 1 Ben Parees 2016-01-20 09:08:32 EST
Rodolfo or Victor can you take a look at this since you're working on the golang example anyway to add tests?

thanks
Comment 2 Rodolfo Carvalho 2016-01-20 09:24:39 EST
Taking a look
Comment 3 Rodolfo Carvalho 2016-01-20 09:41:53 EST
I can reproduce the bug. It was caused by this PR in beego:
https://github.com/astaxie/beego/pull/1540

By looking at the latest commits, looks like they are breaking the API all the time :(

I don't really like using beego in our golang-ex, but, anyway, an old PR I have open will fix the problem by vendoring all dependencies:

https://github.com/openshift/golang-ex/pull/9
Comment 4 Rodolfo Carvalho 2016-01-20 09:49:35 EST
My PR in golang-ex got merged, the problem should be fixed.

@Wenjing Zheng please check.
Comment 5 Wenjing Zheng 2016-01-20 23:39:40 EST
Verified with new openshift/golang-ex repo, works correctly. Thanks!
Comment 7 errata-xmlrpc 2016-05-12 12:26:58 EDT
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, 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/RHSA-2016:1064

Note You need to log in before you can comment on or make changes to this bug.