[JIRA] (JENKINS-59384) the jenkins dockerfile 2.194's jenkins website install feature return error : No such plugin: cloudbees-folder

23 views
Skip to first unread message

tiandong19860806@126.com (JIRA)

unread,
Sep 15, 2019, 11:50:01 PM9/15/19
to jenkinsc...@googlegroups.com
tian dong updated an issue
 
Jenkins / Bug JENKINS-59384
the jenkins dockerfile 2.194's jenkins website install feature return error : No such plugin: cloudbees-folder
Change By: tian dong
Summary: the jenkins dockerfile 2.194's jenkins website   happen a issue install feature return error : No such plugin: cloudbees-folder
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 5:51:02 AM9/21/19
to jenkinsc...@googlegroups.com
tian dong updated an issue
Change By: tian dong
Attachment: image-2019-09-21-17-50-26-587.png

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 5:52:02 AM9/21/19
to jenkinsc...@googlegroups.com
tian dong updated an issue
Change By: tian dong
Attachment: image-2019-09-21-17-51-32-215.png

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 5:52:02 AM9/21/19
to jenkinsc...@googlegroups.com
tian dong commented on Bug JENKINS-59384
 
Re: the jenkins dockerfile 2.194's jenkins website install feature return error : No such plugin: cloudbees-folder

Hi colleague,

     As I manual add plugin file 'cloudbees-folder.hpi' in jenkins install path, there alse can't install jenkins plugin correct as below:

 

upload cloudbees-folder.hpi in jenkins path

 

retry install jenkins plugin, also happen error

 

 

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 6:13:02 AM9/21/19
to jenkinsc...@googlegroups.com
tian dong assigned an issue to tian dong
 
Change By: tian dong
Assignee: tian dong

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 6:19:02 AM9/21/19
to jenkinsc...@googlegroups.com
tian dong updated an issue
Change By: tian dong
Attachment: image-2019-09-21-18-18-27-448.png

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 6:20:02 AM9/21/19
to jenkinsc...@googlegroups.com
tian dong updated an issue
Change By: tian dong
Attachment: image-2019-09-21-18-19-01-139.png

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 6:21:01 AM9/21/19
to jenkinsc...@googlegroups.com
tian dong updated an issue
Change By: tian dong
Attachment: image-2019-09-21-18-20-36-389.png

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 6:21:01 AM9/21/19
to jenkinsc...@googlegroups.com
tian dong started work on Bug JENKINS-59384
 
Change By: tian dong
Status: Open In Progress

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 6:21:02 AM9/21/19
to jenkinsc...@googlegroups.com
 
Re: the jenkins dockerfile 2.194's jenkins website install feature return error : No such plugin: cloudbees-folder

Hi all,

    this problem is also caused by conatainer 's  /etc/resolv.conf error.

fix solution as below:

 
1. 修改VM机器上的resolv.conf文件，增加namesever = K8S_DNS_IP
[root@CNT7XDCK11D01 ~]# cat /etc/resolv.conf
; generated by /usr/sbin/dhclient-script

  1. search home
    search default.svc.cluster.local svc.cluster.local cluster.local
    nameserver 192.168.3.1
    nameserver 10.3.0.2
    [root@CNT7XDCK11D01 ~]#
     

2. 修改VM机器上的网卡ifcfg-eno01文件

  1. 增加DNS2=K8S_DNS_IP
    [root@CNT7XDCK11D02 ~]# vi /etc/sysconfig/network-scripts/ifcfg-eno01
    DEVICE="eno01"
    NAME="eno01"
    BOOTPROTO="static"
    BROADCAST="192.168.3.225"
    DNS1="192.168.3.1"
    DNS2="10.3.0.2"
  2. DNS1="223.5.5.5"
  3. DNS2="223.6.6.6"
    GATEWAY="192.168.3.1"
    HWADDR="xx:xx:xx:xx:xx:xx"
    IPADDR="192.168.3.97"
    IPV6INIT="yes"
    IPV6_AUTOCONF="yes"
    NETMASK="255.255.255.0"
    NM_CONTROLLED="yes"
    ONBOOT="yes"
    TYPE="Ethernet"
    UUID="xxxxxxxx-xxxx-xxxxx-xxxxx-xxxxxxxxxxxxxxxxxx"
     
     
    3. the success result as below:
    first delete old jenkins resouce from k8s.
    root >> kubectl delete service/jenkins-master deployment.apps/jenkins-master -n kube-ops
     
    then re-create the new jenkins resource in k8s,
    root >> kubectl apply -f /opt/dockerfile/jenkins/01

     

     

     
     
     
     

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 6:22:02 AM9/21/19
to jenkinsc...@googlegroups.com
tian dong resolved as Fixed
 
Change By: tian dong
Status: In Progress Resolved
Resolution: Fixed

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 6:26:02 AM9/21/19
to jenkinsc...@googlegroups.com
tian dong edited a comment on Bug JENKINS-59384
Hi all,

    this problem is also caused by conatainer 's  /etc/resolv.conf error.

fix solution as below:

 
1. 修改VM机器上的resolv.conf文件，增加namesever = K8S_DNS_IP
[root@CNT7XDCK11D01 ~]# cat /etc/resolv.conf
; generated by /usr/sbin/dhclient-script
# search home
{color:#df402a}search default.svc.cluster.local svc.cluster.local cluster.local{color}
nameserver 192.168.3.1
nameserver {color:#df402a}10.3.0.2{color}
[root@CNT7XDCK11D01 ~]#
 
2. 修改VM机器上的网卡ifcfg-eno01文件
 #
增加DNS2=K8S_DNS_IP
[root@CNT7XDCK11D02 ~]# vi /etc/sysconfig/network-scripts/ifcfg-eno01
DEVICE="eno01"
NAME="eno01"
BOOTPROTO="static"
BROADCAST="192.168.3.225"
DNS1="192.168.3.1"
{color:# FF0000 ff0000 }DNS2="10.3.0.2"{color}
 #
DNS1="223.5.5.5"
 #
DNS2="223.6.6.6"
GATEWAY="192.168.3.1"
HWADDR="xx:xx:xx:xx:xx:xx"
IPADDR="192.168.3.97"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
NETMASK="255.255.255.0"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
UUID="xxxxxxxx-xxxx-xxxxx-xxxxx-xxxxxxxxxxxxxxxxxx"
 
 
3. the success result as below:
first delete old jenkins resouce from k8s.
root >> kubectl delete service/jenkins-master deployment.apps/jenkins-master -n kube-ops
 
then re-create the new jenkins resource in k8s,
root >> kubectl apply -f /opt/dockerfile/jenkins/01
!image-2019-09-21-18-20-36-389.png!
 
!image-2019-09-21-18-19-01-139.png!
 
!image-2019-09-21-18-18-27-448.png!
 
 
 
 

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 6:26:02 AM9/21/19
to jenkinsc...@googlegroups.com
tian dong edited a comment on Bug JENKINS-59384
Hi all,

    this problem is also caused by conatainer 's  /etc/resolv.conf error.

fix solution as below:

 
1. 修改VM机器上的resolv.conf文件，增加namesever = K8S_DNS_IP
[root@CNT7XDCK11D01 ~]# cat /etc/resolv.conf
; generated by /usr/sbin/dhclient-script
# search home
{color:#df402a}search default.svc.cluster.local svc.cluster.local cluster.local{color}
nameserver 192.168.3.1
nameserver {color:#df402a}10.3.0.2{color}
[root@CNT7XDCK11D01 ~]#
 

2. 修改VM机器上的网卡ifcfg-eno01文件

增加DNS2=K8S_DNS_IP
[root@CNT7XDCK11D02 ~]# vi /etc/sysconfig/network-scripts/ifcfg-eno01
DEVICE="eno01"
NAME="eno01"
BOOTPROTO="static"
BROADCAST="192.168.3.225"
DNS1="192.168.3.1"
{color:#ff0000}DNS2="10.3.0.2"{color}

DNS1="223.5.5.5"


DNS2="223.6.6.6"
GATEWAY="192.168.3.1"
HWADDR="xx:xx:xx:xx:xx:xx"
IPADDR="192.168.3.97"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
NETMASK="255.255.255.0"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
UUID="xxxxxxxx-xxxx-xxxxx-xxxxx-xxxxxxxxxxxxxxxxxx"
 
 
3. the success result as below:
first delete old jenkins resouce from k8s.
root >> kubectl delete service/jenkins-master deployment.apps/jenkins-master -n kube-ops
 
then re-create the new jenkins resource in k8s,
root >> kubectl apply -f /opt/dockerfile/jenkins/01
!image-2019-09-21-18-20-36-389.png!
 
!image-2019-09-21-18-19-01-139.png!
 
!image-2019-09-21-18-18-27-448.png!
 
 
 
 

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 6:27:02 AM9/21/19
to jenkinsc...@googlegroups.com

tiandong19860806@126.com (JIRA)

unread,
Sep 21, 2019, 6:27:02 AM9/21/19
to jenkinsc...@googlegroups.com
tian dong edited a comment on Bug JENKINS-59384
Hi all,

    this problem is also caused by conatainer 's  /etc/resolv.conf error.

fix solution as below:

 
1. 修改VM机器上的resolv.conf文件，增加namesever = K8S_DNS_IP
[root@CNT7XDCK11D01 ~]# cat /etc/resolv.conf
; generated by /usr/sbin/dhclient-script
Reply all
Reply to author
Forward
0 new messages