-
Notifications
You must be signed in to change notification settings - Fork 66
FAQ
Here are some commonly asked questions.
Click on the Register Now
link in the landing page, and sign-in using your @redhat.com
account.
< to be filled in >
This is a bug which is being fixed in https://github.com/almighty/almighty-core/pull/1367 After this PR is merged, re-login to OpenShift.io to be able to see your updated username.
Currently, the tenant URL is https://console.starter-us-east-2.openshift.com
My username on OpenShift.io is different than the name of the project created in my OpenShift Online account
The reason is unknown as of now, however the debugging session was successful in resolving this for chmouel
This will cause issues with creating your QuickStart projects and pipelines.
( need to fill in details )
Assuming your old project is pke-test1
and your OpenShift.io username is pkettman
, this might cause your pipelines to not show up since there is no pkettman
namespace.
Clean-up your existing project by running the following:
Visit https://console.starter-us-east-2.openshift.com/oauth/token/request to get your oc
auth token needed for the CLI login.
oc login https://console.starter-us-east-2.openshift.com --token=TOKEN
oc delete project pke-test1
oc new-project pkettman
oc delete all --all -n pkettman-test
oc delete all --all -n pkettman-stage
oc delete all --all -n pkettman-run
"When I goto https://jenkins-username-jenkins.8a09.starter-us-east-2.openshiftapps.com
I just get Application Not Available"
This happens when your Jenkins service is struggling to load because of resource issues.
Workaround :
- Login to https://console.starter-us-east-2.openshift.com
- Navigate to https://console.starter-us-east-2.openshift.com/console/project/your-username-jenkins/overview by clicking on the *-jenkins project.
- Scale the "jenkins" service to 0 pods and then to 1. This might take upto 5 minutes to take effect.
[Pipeline] End of Pipeline
java.lang.OutOfMemoryError: Metaspace
Finished: FAILURE
The solution is same as the one above, if you are using the OpenShift CLI, you could use these command alternatively to restart the Jenkins pod
oc scale dc/jenkins --replicas=0 -n burrsutter-jenkins
oc scale dc/jenkins --replicas=1 -n burrsutter-jenkins
https://github.com/openshiftio/openshift.io/issues/206
Your own jenkins,che,etc is running in your OpenShift Online account in the https://console.starter-us-east-2.openshift.com cluster. The Deployment Configs have to be updated every few days. To do so,
- Login to OpenShift.io , if you face issues while trying to login, please see ( add link )
- Visit your profile by clicking on the top-right corner.
- Click "Update profile"
- Scroll down to the bottom of the page and click "Update tenant". This doesn't provide any feedback as of now, but you could check for a
/api/user 200 OK
response in the browser console.
To confirm you need to be checking which build version of Jenkins/Che you are running, and compare it with the intended version.
To find out which version of the Jenkins 2 build you are running,
use the oc
CLI , and try running oc export dc jenkins -n oc {ID}-jenkins | grep "version:"
If the above doesn't work, use the UI:
- Login to OpenShift Online https://console.starter-us-east-2.openshift.com
- Select project {ID}-jenkins
- Navigate to ``Applications
->
Deployments` -> `jenkins`. - Open the latest 'active' deployment from the list.
- On the
details
tab, there should aversion=3.x.x
To find out the intended version, visit http://central.maven.org/maven2/io/fabric8/online/packages/fabric8-online-jenkins/1.0.160/fabric8-online-jenkins-1.0.160-openshift.yml and look for the section:
provider: fabric8
project: jenkins-openshift
version: 3.0.33
Re-construct the above URL by replacing 1.0.160 with the value in https://github.com/fabric8io/fabric8-init-tenant/blob/master/TEAM_VERSION
Note: Assuming that the latest fabric8-init-tenant
commit is in production.
"well the update is fine; it updates the Jenkins DC just fine - but for some reason openshift then decides to ignore that, cancel the deployment so the version 0 keeps running despite version N being more recent. I found I had to manually go into the openshift console and click the Deploy button by hand." - James ( need to improve the instructions ) https://github.com/fabric8io/fabric8-init-tenant/issues/74
oc delete bc --all -n ${ID}
oc delete build --all -n ${ID}
oc delete all --all -n ${ID}-test
oc delete all --all -n ${ID}-stage
oc delete all --all -n ${ID}-run
This happens when the the Openshift-v3 or Github expires.
- Go to https://sso.openshift.io/auth/realms/fabric8/account/identity
- Remove and add your Openshift-v3 account.
- Remove and add your Github account.
This happens because of a bug in the jenkins-sync plugin which restarts all old builds. Since, we have a restriction of only allowing 1 build at a time, the newly created project's build pipeline falls low into the build queue. To fix this, abort all the queued up builds except the one which was created 'just now'.
- On the Pipelines UI, click on the Jenkins URL ( this part needs better instructions )
- In the Jenkins UI, locate the queue visualisation on the left-hand side of the page.
- Click on the red abort button for each build.
This could have happened if lots of builds were triggered and never got provisioned due to quotas and there's lots of Build resources left over.
Delete all the build resources by doing a oc delete build --all
Unauthorized! Configured service account doesn't have access. Service account may have been revoked. Unauthorized
- Go to https://sso.openshift.io/auth/realms/fabric8/account/identity
- Remove and add your Openshift-v3 account.
- Remove and add your Github account.