Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1368916 - Cannot find "sample-pipeline" item in jenkins webconsole
Cannot find "sample-pipeline" item in jenkins webconsole
Status: CLOSED NEXTRELEASE
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image (Show other bugs)
3.3.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Ben Parees
Wang Haoran
:
Depends On: 1368888
Blocks:
  Show dependency treegraph
 
Reported: 2016-08-22 02:13 EDT by Dongbo Yan
Modified: 2017-03-08 13 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
: 1374127 (view as bug list)
Environment:
Last Closed: 2016-09-19 05:03:02 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 RHBA-2016:1933 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.3 Release Advisory 2016-09-27 09:24:36 EDT

  None (edit)
Description Dongbo Yan 2016-08-22 02:13:47 EDT
Description of problem:
After jenkins is deployed, cannot find "sample-pipeline" item in jenkins webconsole

Version-Release number of selected component (if applicable):
openshift3/jenkins-1-rhel7 (19bc08e9d803)

How reproducible:
Always

Steps to Reproduce:
1.Create a pipeline build
 $ oc new-app https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.json
2.Login in jenkins, check item info
3.

Actual results:
Cannot find "sample-pipeline" item

Expected results:
"sample-pipeline" item exists

Additional info:
Could trigger pipeline build, build successfully, but cannot check buildlog
Comment 1 Ben Parees 2016-08-22 11:31:32 EDT
Does this occur with the pulp rhel jenkins image?  the public image is not yet up to date.

Also I don't see a step where you created the jenkins service/deployment, but since autoprovisioning is now disabled, I assume you did, right?
Comment 3 Dongbo Yan 2016-08-22 22:06:10 EDT
When I create a pipeline application, it still can auto deploy jenkins

openshift v3.3.0.23-dirty
kubernetes v1.3.0+507d3a7
etcd 2.3.0+git
Comment 4 Ben Parees 2016-08-22 22:22:23 EDT
You're saying you were able to start the pipeline build and it completed successfully, but there is no jenkins job definition in the jenkins console?
Comment 5 Dongbo Yan 2016-08-22 22:28:31 EDT
yes, only "Openshift Sample" item in the jenkins console, item "sample-pipeline" is not existing
Comment 6 Dongbo Yan 2016-08-22 22:31:15 EDT
And there is no jenkins job definition in the jenkins webconsole, but I can see the slave node
Comment 7 Ben Parees 2016-08-23 16:00:32 EDT
I can't recreate this using the latest pulp image that was built today, can you retry w/ that image and if you're still seeing an issue, please gather the logs from the jenkins pod?
Comment 8 Dongbo Yan 2016-08-24 06:46:35 EDT
Test with
brew-pulp...openshift3/jenkins-1-rhel7             latest     7e4706a0e228

openshift v3.3.0.24-dirty
kubernetes v1.3.0+507d3a7
etcd 2.3.0+git

step:
1.Create a pipeline build
 $ oc new-app https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.json
2.Create a jenkins
 $ oc new-app https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/jenkins-ephemeral-template.json

cannot reproduce this issue any more.

Due to Jenkins server is not automatically instantiated in ose3.3.0.24, I have tried to enable autoprovisioning in master-config.yaml, like:
kubernetesMasterConfig:
  jenkinsPipelineConfig:
    enabled: true
    templateNamespace: openshift
    templateName: jenkins-ephemeral
    serviceName: jenkins

But it does not work, how can I enable autoprovisioning.
Comment 9 Ben Parees 2016-08-24 10:54:54 EDT
Did you "oc create -f jenkins-ephemeral-template.json -n openshift" ?

What happens when you create a new pipeline buildconfig with the provisioner enabled?
Comment 10 Ben Parees 2016-08-24 11:02:56 EDT
I think the docs may be wrong, investigating.
Comment 11 Ben Parees 2016-08-24 11:47:22 EDT
ok so there are two issues:

1) the "enabled" field was named wrong and i'm fixing that here:
https://github.com/openshift/origin/pull/10612

2) the instructions weren't very good and i'm fixing that here:
https://github.com/openshift/openshift-docs/pull/2725

What you need to do is add the following to your master config:
jenkinsPipelineConfig:
  autoProvisionEnabled: true
  serviceName: jenkins
  templateName: jenkins-ephemeral
  templateNamespace: openshift


that goes at the top level of the file, it's not nested under anything.

and until 10612 merges, you will need to specify "enabled: true" instead of "autoProvisionEnabled: true"
Comment 12 Ben Parees 2016-08-24 11:49:19 EDT
Note that if you use the "openshift start --write-config" flag you can generate a proper config and then just edit that file, find the "jenkinsPipelineConfig" section, and change the "enabled" field from false to true (and change the templateName if needed)
Comment 13 Dongbo Yan 2016-08-24 22:28:50 EDT
Verified with
openshift v3.3.0.24-dirty
kubernetes v1.3.0+507d3a7
etcd 2.3.0+git

Add following into master config
jenkinsPipelineConfig:
  enabled: true
  serviceName: jenkins
  templateName: jenkins-ephemeral
  templateNamespace: openshift

It works, thanks

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