On Sat, Jun 11, 2016 at 02:10:09PM +0530, Saravanakumar Arumugam wrote: > Hi Niels, > > On 06/10/2016 07:15 PM, Niels de Vos wrote: > > On Fri, Jun 10, 2016 at 06:48:38PM +0530, Nigel Babu wrote: > > > From looking at IRC, this seems like legit bustage. There was a fix for > > > this, which seems to be not backported for 3.7. > > Indeed, these are the changes that we need merged for this issue to be > > resolved: > > > > > > http://review.gluster.org/#/q/project:glusterfs+branch:release-3.7+topic:bug-1336137 > > > > http://review.gluster.org/14340 is the top level patch, and if you base > > your 3.7 changes on that one the tests should pass. You can do this in > > different ways, but I would do it like: > > > > $ git checkout my-branch-for-3.7-backport > > $ git fetch origin refs/changes/40/14340/2 > > $ git rebase FETCH_HEAD > > $ git review --no-rebase --remote origin -t bug-0123456 > > (bug-0123456 should be the bug-<number> for the 3.7 bug) > Thanks! > > I have tried the steps, but the last command failed saying "remote > rejected". > > =============================== > sarumuga@gant glusterfs$ git fetch origin refs/changes/40/14340/2 > remote: Counting objects: 53, done > remote: Finding sources: 100% (33/33) > remote: Total 33 (delta 21), reused 29 (delta 21) > Unpacking objects: 100% (33/33), done. > From ssh://git.gluster.org/glusterfs > * branch refs/changes/40/14340/2 -> FETCH_HEAD > > sarumuga@gant glusterfs$ git status > On branch release3.7_upgrade > > sarumuga@gant glusterfs$ git branch > master > * release3.7_upgrade > release3.8_upgrade > > sarumuga@gant glusterfs$ git rebase FETCH_HEAD > First, rewinding head to replay your work on top of it... > Applying: glusterd/geo-rep: upgrade path when slave vol uuid involved > > sarumuga@gant glusterfs$ git log > commit 5653ffc8785661a655112c84d0fcad042c6bcfe2 > Author: Saravanakumar Arumugam <[email protected]> > Date: Thu May 19 21:13:04 2016 +0530 > > glusterd/geo-rep: upgrade path when slave vol uuid involved > commit 5653ffc8785661a655112c84d0fcad042c6bcfe2 > Author: Saravanakumar Arumugam <[email protected]> > Date: Thu May 19 21:13:04 2016 +0530 > > glusterd/geo-rep: upgrade path when slave vol uuid involved > > slave volume uuid is involved in identifying a geo-replication > session. > > This patch addresses upgrade path, where existing geo-rep session > is gracefully upgraded to involve slave volume uuid. > > Change-Id: Ib7ff5109b161592f24fc86fc7e93a407655fab86 > BUG: 1342453 > Reviewed-on: http://review.gluster.org/#/c/14425 > Signed-off-by: Saravanakumar Arumugam <[email protected]> > > commit 3d946a44df559ce1b9089983edb3465c61ba1ea0 > Author: Niels de Vos <[email protected]> > Date: Sat May 14 19:23:20 2016 +0200 > > configure: Prevent glupy installation outside $prefix > > glupy was installed in the global path outside the prefix path, > even if --prefix is passed. > > ./configure --prefix=/usr/local > make install > > Expected: > ${DESTDIR}${prefix}/lib64/python<VERSION>/site-packages/gluster > Actual: ${DESTDIR}/usr/lib64/python<VERSION>/site-packages/gluster > > > sarumuga@gant glusterfs$ git review --no-rebase --remote origin -t > bug-1342453 > You are about to submit multiple commits. This is expected if you are > submitting a commit that is dependent on one or more in-review > commits. Otherwise you should consider squashing your changes into one > commit before submitting. > > The outstanding commits are: > > 5653ffc (HEAD -> release3.7_upgrade) glusterd/geo-rep: upgrade path when > slave vol uuid involved > 3d946a4 configure: Prevent glupy installation outside $prefix > 01cf67a build: Filter -D_FORTIFY_SOURCE from CFLAGS > 235966b build: place glupy under $prefix while installing > 37ac79f cluster/ec: Restrict the launch of replace brick heal > 3a82ea3 libglusterfs: Even anonymous fds must have fd->flags set > > Do you really want to submit the above commits? > Type 'yes' to confirm, other to cancel: yes > remote: Processing changes: refs: 1, done > To ssh://[email protected]/glusterfs > ! [remote rejected] HEAD -> refs/publish/master/bug-1342453 (change > http://review.gluster.org/14425 closed) > error: failed to push some refs to > 'ssh://[email protected]/glusterfs' > sarumuga@gant glusterfs$
Hmm, it tried to push the change for the master branch. And that one is already merged, so you can not update it. Oh, even the version for release-3.7 has been merged now. So I guess the problems have been resolved? Niels > =============================== > > > HTH, > > Niels > > > > > On Fri, Jun 10, 2016 at 5:31 PM, Saravanakumar Arumugam > > > <[email protected] > > > > wrote: > > > > Hi, > > > > Observed permission denied errors in smoke test as: > > > > > > > > *03:55:40* Traceback (most recent call last):*03:55:40* File > > > > "<string>", line 15, in <module>*03:55:40* File > > > > "/usr/lib64/python2.6/py_compile.py", line 135, in compile*03:55:40* > > > > fc = open(cfile, 'wb')*03:55:40* IOError: [Errno 13] Permission > > > > denied: > > > > '/usr/lib/python2.6/site-packages/gluster/glupy/__init__.pyc'*03:55:40* > > > > make[6]: *** [install-pyglupyPYTHON] Error 1 > > > > > > > > https://build.gluster.org/job/smoke/28549/console > > > > > > > > Can you help? > > > > > > > > Thanks, > > > > Saravana > > > > > > > > > > > > > -- > > > nigelb > > > _______________________________________________ > > > Gluster-infra mailing list > > > [email protected] > > > http://www.gluster.org/mailman/listinfo/gluster-infra >
signature.asc
Description: PGP signature
_______________________________________________ Gluster-infra mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-infra
