Forge wizard fails on vert.x quickstart

[tdcox]

Environment: Release 0.4.149 running on minikube with K8S 1.7.0 on MacOs 10.12.6.

Steps to reproduce: Clean install of platform. Log in. Create a space. Choose to create a quickstart when prompted. Choose vert.x quickstart. Accept 'default' Jenkins space.

Wizard fails at the validating phase with:

Error! Something went wrong while attempting to perform this operation ...

ExecuteForgeCommandError
The forge-quick-start :: execute :: 4 command failed or only partially succeeded
messageFailed to find Jenkins URL in namespace default typeorg.javassist.tmp.java.lang.RuntimeException_$$_javassist_8fd29280-574a-4812-be3a-c5e69e3fee2e forgeVersion3.6.1.Final

Code gets deployed to GitHub successfully.

Also note - Clearing the warning dialog returns the user to the previous (final) step of the wizard. Pressing 'Finish' again results in an error saying that the GitHub repo already exists. looks like this is a 'sad' path that doesn't have a viable workflow at the moment. Extra test needed?

At this point, the user is able to edit the repo name in the edit box, but resubmitting with a new name doesn't impact the actual behaviour and you end up in a circular loop of errors.

By returning to the space and importing the codebase from the repo, I could see the code but still had no pipeline. By then adding a pipeline, I was able to correctly see the -jenkins namespace that was missing originally. The wizard validates correctly but the build doesn't run and clicking on the build link takes you back to the home page for fabric8.

Exploring Codebases shows that two entries now exist for the same repo.

[tdcox]

Getting this problem again. The Jenkins Space value in the app wizard is set to 'default' rather than the user namespace. This causes forge to throw a runtime exception if the form is submitted.

[tdcox]

2017-09-14 13:24:19,306 INFO [io.fabric8.kubernetes.api.Controller] (default task-27) Using namespace: default
2017-09-14 13:24:19,441 INFO [io.fabric8.utils.Systems] (default task-27) Connecting to service jenkins on : from $JENKINS_SERVICE_HOST and $JENKINS_SERVICE_PORT
2017-09-14 13:24:19,447 SEVERE [org.obsidiantoaster.generator.rest.ObsidianResource] (default task-27) Failed to find Jenkins URL in namespace default: io.fabric8.forge.generator.kubernetes.BadTenantException: Failed to find Jenkins URL in namespace default

[jstrachan]

failure to find the Jenkins URL sounds like your tenant hasn't been provisioned yet. The init-tenant process should create your namespaces; ${ID}, ${ID}-jenkins, ${ID}-che, ${ID}-stage, ${ID}-run - am guessing that didn't work.

Only thing I can imagine is there's RBAC enabled on your cluster? Or is there some error in the init-tenant log?

[tdcox]

"Failed to find Secret name in ServiceAccount tdcox" in tenant log...

https://gist.github.com/tdcox/0664d590b660fcee0dd703d9c3a8f016

[tdcox]

I have just performed a clean and re-install of fabric8. I have yet to log in to the system, but am seeing the error "Failed to find Secret name in ServiceAccount tdcox" in the init-tenant log.

Is something trying to get to GitHub before the user has logged in for the first time?

[tdcox]

This time, when logging in for the first time, I received a page with the black and red top menu where I had to click on the right hand drop down to log in, rather than the simple 'log in' drop down in the centre. All the namespaces were set up correctly and the quickstart wizard has the right data.

Did something get fixed from 4.0.191 to 4.0.192, or do we have a race condition?