Will try that - but my msg has no commit-id yet

Tried updating an existing review - worked fine - may be an issue on my part
Also I see new reviews coming in from other developers - so likely me only

obrienbiometrics:logging-analytics michaelobrien$ git status
On branch master
Your branch and 'origin/master' have diverged,
and have 1 and 6 different commits each, respectively.
  (use "git pull" to merge the remote branch into yours)
Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

        modified:   deploy/cd.sh

obrienbiometrics:logging-analytics michaelobrien$ git commit --amend
[master 6f718d2] cd.sh oom deployment script
 Date: Mon May 14 20:25:45 2018 -0400
 1 file changed, 365 insertions(+)
 create mode 100755 deploy/cd.sh
obrienbiometrics:logging-analytics michaelobrien$ git review -R
Warning: Permanently added '[gerrit.onap.org]:29418,[198.145.29.92]:29418' 
(RSA) to the list of known hosts.
remote: Processing changes: updated: 1, refs: 1, done            
remote: 
remote: Updated Changes:        
remote:   https://gerrit.onap.org/r/47503 cd.sh oom deployment script        
remote: 
To ssh://gerrit.onap.org:29418/logging-analytics
 * [new branch]      HEAD -> refs/publish/master


-----Original Message-----
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, May 16, 2018 7:17 PM
To: Michael O'Brien <frank.obr...@amdocs.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #56089] [LF] Gerrit review fails to push on jetty 404 
looking for /tools/hooks/commit-msg

Michael, 

Are you able to push the code using git push?

Thanks!
Jess


On Wed May 16 19:02:37 2018, frank.obr...@amdocs.com wrote:
> Team,
>    Hi, having a new issue pushing code to gerrit - getting a 404 - 
> where previously if there was a commit message format issue it would 
> notify you of the cause - getting a 404 now.
>    Pushing reviews a couple days ago had no issues.
>    Is anyone else having issues pushing a new gerrit review
>    Will amend "git review -R" and existing review to see if it is just 
> for new commits
> 
> Details on
> https://jira.onap.org/browse/LOG-376
> 
> 
> obrienbiometrics:log-376b michaelobrien$ cd oom
> 
> obrienbiometrics:oom michaelobrien$ git status
> 
> On branch master
> 
> Your branch is up-to-date with 'origin/master'.
> 
> Changes to be committed:
> 
> (use "git reset HEAD <file>..." to unstage)
> 
> 
> 
> modified:   kubernetes/log/charts/log-logstash/values.yaml
> 
> 
> 
> obrienbiometrics:oom michaelobrien$ git commit -am "log logstash 
> replicaset to 3"
> 
> [master 8324970] log logstash replicaset to 3
> 
> 1 file changed, 2 insertions(+), 1 deletion(-)
> 
> obrienbiometrics:oom michaelobrien$ git commit -s --amend
> 
> [master 05509fc] log logstash replicaset to 3
> 
> Date: Wed May 16 18:55:11 2018 -0400
> 
> 1 file changed, 2 insertions(+), 1 deletion(-)
> 
> obrienbiometrics:oom michaelobrien$ git review
> 
> Problems encountered installing commit-msg hook
> 
> The following command failed with exit code 104
> 
> "GET https://michaelobr...@gerrit.onap.org/tools/hooks/commit-msg";
> 
> -----------------------
> 
> <html>
> 
> <head>
> 
> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-
> 1"/>
> 
> <title>Error 404 </title>
> 
> </head>
> 
> <body>
> 
> <h2>HTTP ERROR: 404</h2>
> 
> <p>Problem accessing /tools/hooks/commit-msg. Reason:
> 
> <pre>    Not Found</pre></p>
> 
> <hr /><i><small>Powered by Jetty://</small></i>
> 
> </body>
> 
> </html>
> 
> 
> 
> -----------------------
> *
> Co<https://jira.onap.org/secure/AddComment!default.jspa?id=22902>
> 
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> <https://www.amdocs.com/about/email-disclaimer>



This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to