Gerrit Zuul Communication

71 views
Skip to first unread message

Santhosh Kumar

unread,
Jul 12, 2015, 9:58:38 AM7/12/15
to repo-d...@googlegroups.com

I had installed zuul and Gerrit in two different VM's.

Both are working fine independently which means I can able to listen the stream events through gerrit when the  any changes happens in gerrit ui.

In another machine I can able to see the zuul is running good by the command "zuul-server -d". Seems it listens something in gerrit. I dont know how to make the communication between zuul and gerrit. I had given the specific details about gerrit in zuul.conf also. Please check below,

-bash-4.1$ zuul-server -d

DEBUG:gear.BaseClientServer:Preparing to poll

DEBUG:gear.BaseClientServer:Polling 0 connections

Traceback (most recent call last):

  File "/usr/local/lib/python2.7/logging/handlers.py", line 77, in emit

    self.doRollover()

  File "/usr/local/lib/python2.7/logging/handlers.py", line 350, in doRollover

    os.rename(self.baseFilename, dfn)

OSError: [Errno 13] Permission denied

Logged from file swift.py, line 62

Traceback (most recent call last):

  File "/usr/local/lib/python2.7/logging/handlers.py", line 77, in emit

    self.doRollover()

  File "/usr/local/lib/python2.7/logging/handlers.py", line 350, in doRollover

    os.rename(self.baseFilename, dfn)

OSError: [Errno 13] Permission denied

Logged from file swift.py, line 62

2015-07-12 06:40:43,146 WARNING zuul.lib.swift: Unable to set up swift. Signed storage URL is likely to be wrong. No option 'authurl' in section: 'swift'

DEBUG:gear.Server:Accepting new connection

DEBUG:gear.ServerConnection:Setting state to: INIT

INFO:gear.Server:Accepted connection <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

DEBUG:gear.Server:Registering <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

DEBUG:gear.Server:Processing output on <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

DEBUG:gear.Server:Polling 1 connections

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

INFO:gear.Server:Received admin request <gear.AdminRequest 0x234f4d0 command: status>

DEBUG:gear.ServerConnection:Queuing data to <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>: .


DEBUG:gear.Server:Finished handling admin request <gear.AdminRequest 0x234f4d0 command: status>

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

DEBUG:gear.Server:Processing output on <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

DEBUG:gear.Server:Polling 1 connections

DEBUG:gear.Server:Accepting new connection

DEBUG:gear.ServerConnection:Setting state to: INIT

INFO:gear.Server:Accepted connection <gear.ServerConnection 0x234f4d0 name: None host: 172.16.114.136 port: 33197>

DEBUG:gear.Server:Registering <gear.ServerConnection 0x234f4d0 name: None host: 172.16.114.136 port: 33197>

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x234f4d0 name: None host: 172.16.114.136 port: 33197>

DEBUG:gear.Server:Processing output on <gear.ServerConnection 0x234f4d0 name: None host: 172.16.114.136 port: 33197>

DEBUG:gear.Server:Accepting new connection

DEBUG:gear.Server:Polling 2 connections

DEBUG:gear.ServerConnection:Setting state to: INIT

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

INFO:gear.Server:Accepted connection <gear.ServerConnection 0x23c6110 name: None host: 172.16.114.136 port: 33198>

INFO:gear.Server:Received admin request <gear.AdminRequest 0x234f3d0 command: status>

DEBUG:gear.Server:Registering <gear.ServerConnection 0x23c6110 name: None host: 172.16.114.136 port: 33198>

DEBUG:gear.ServerConnection:Queuing data to <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>: .


DEBUG:gear.Server:Finished handling admin request <gear.AdminRequest 0x234f3d0 command: status>

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

DEBUG:gear.Server:Processing output on <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

DEBUG:gear.Server:Polling 3 connections

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x23c6110 name: None host: 172.16.114.136 port: 33198>

INFO:gear.Server:Received packet from <gear.ServerConnection 0x23c6110 name: None host: 172.16.114.136 port: 33198>: <gear.Packet 0x234f3d0 type: SET_CLIENT_ID id: Zuul RPC Listener>

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>

INFO:gear.Server:Received packet from <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>: <gear.Packet 0x23c61d0 type: CAN_DO function: zuul:get_running_jobs>

DEBUG:gear.Server:Adding function zuul:get_running_jobs to <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>

INFO:gear.Server:Received packet from <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>: <gear.Packet 0x234f3d0 type: CAN_DO function: zuul:promote>

DEBUG:gear.Server:Adding function zuul:promote to <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>

INFO:gear.Server:Received packet from <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>: <gear.Packet 0x23c61d0 type: CAN_DO function: zuul:enqueue>

DEBUG:gear.Server:Adding function zuul:enqueue to <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>

INFO:gear.Server:Received packet from <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>: <gear.Packet 0x234f3d0 type: GRAB_JOB_UNIQ>

DEBUG:gear.ServerConnection:Queuing packet to <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>: <gear.Packet 0x23c61d0 type: NO_JOB>

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>

DEBUG:gear.Server:Processing output on <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>

DEBUG:gear.Server:Polling 3 connections

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>

INFO:gear.Server:Received packet from <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>: <gear.Packet 0x234f3d0 type: PRE_SLEEP>

DEBUG:gear.ServerConnection:Setting state to: SLEEP

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>

DEBUG:gear.Server:Processing output on <gear.ServerConnection 0x23c6110 name: Zuul RPC Listener host: 172.16.114.136 port: 33198>

DEBUG:gear.Server:Polling 3 connections

DEBUG:gear.Server:Accepting new connection

DEBUG:gear.ServerConnection:Setting state to: INIT

INFO:gear.Server:Accepted connection <gear.ServerConnection 0x234f3d0 name: None host: 172.16.114.136 port: 33199>

DEBUG:gear.Server:Registering <gear.ServerConnection 0x234f3d0 name: None host: 172.16.114.136 port: 33199>

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x234f3d0 name: None host: 172.16.114.136 port: 33199>

DEBUG:gear.Server:Processing output on <gear.ServerConnection 0x234f3d0 name: None host: 172.16.114.136 port: 33199>

DEBUG:gear.Server:Polling 4 connections

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

INFO:gear.Server:Received admin request <gear.AdminRequest 0x23c61d0 command: status>

DEBUG:gear.ServerConnection:Queuing data to <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>: zuul:get_running_jobs 0 0 1


DEBUG:gear.ServerConnection:Queuing data to <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>: zuul:promote 0 0 1


DEBUG:gear.ServerConnection:Queuing data to <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>: zuul:enqueue 0 0 1


DEBUG:gear.ServerConnection:Queuing data to <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>: .


DEBUG:gear.Server:Finished handling admin request <gear.AdminRequest 0x23c61d0 command: status>

DEBUG:gear.Server:Processing input on <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

DEBUG:gear.Server:Processing output on <gear.ServerConnection 0x234f450 name: None host: 172.16.114.136 port: 33196>

DEBUG:gear.Server:Polling 4 connections




Zaro

unread,
Jul 12, 2015, 7:30:12 PM7/12/15
to Santhosh Kumar, repo-d...@googlegroups.com
Hello Santhosh, Zuul communicates with Gerrit via the Gerrit Stream events.  Your error indicates that zuul user is having a problem polling for the Gerrit events which probably means that your zuul user in gerrit does not have access to stream events.  You can give stream event access to the zuul user by setting the Gerrit ACLs [1] or by putting the zuul user in the Non-Interactive users group [2].  


--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages