Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1363733

Summary:	planet.gluster.org isn't syncing
Product:	[Community] GlusterFS	Reporter:	Kaushal <kaushal>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, mscherer
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-04 11:50:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kaushal 2016-08-03 12:52:59 UTC

I'd added a new post [1] to my blog for the 3.7.14 release. This hasn't shown up yet on planet.gluster.org.

[1]: https://kshlm.in/post/glusterfs-3-7-14/

Comment 1 M. Scherer 2016-08-04 09:49:11 UTC

Ok so it seems deploy is broken:

[middleman_builder@webbuilder ~]$ /usr/local/bin/build_deploy.py -f -d  /srv/builder/gluster_planet.yml
No local changes to save
Current branch master is up to date.
rsync: failed to set times on "/srv/middleman_website/www/planet/master/.": Operation not permitted (1)
rsync: mkstemp "/srv/middleman_website/www/planet/master/.feed.xml.sRr5mT" failed: Permission denied (13)
inflate returned -3 (5 bytes)
rsync error: error in rsync protocol data stream (code 12) at token.c(547) [receiver=3.0.6]
rsync: connection unexpectedly closed (6411 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]


I wonder what happened :/

Comment 2 M. Scherer 2016-08-04 11:35:39 UTC

Ok so that's likely a side effect of the change 2 weeks ago when moving from salt to ansible, after removing the wiki.

Comment 3 M. Scherer 2016-08-04 11:50:46 UTC

Ok so that's fixed by the 2 last commits. I will likely have to refactor the ansible playbook later, cause for now, that's slightly a bit more uglier than 1 hoped :/