Closed Bug 777692 Opened 12 years ago Closed 12 years ago

Push to releases/l10n/mozilla-beta/ach fails with bad permissions, reset content?

Categories

(Developer Services :: General, task)

x86
macOS
task
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: Pike, Assigned: cshields)

Details

Übertrage nach ssh://hg.mozilla.org/releases/l10n/mozilla-beta/ach/
Suche nach Änderungen
Entfernt: Füge Änderungssätze hinzu
Entfernt: Füge Manifeste hinzu
Entfernt: Füge Dateiänderungen hinzu
Entfernt: Fügte 28 Änderungssätze mit 1087 Änderungen an 345 Dateien hinzu
Entfernt: Fehler: Hook changegroup.z_loghistory löste eine Ausnahme aus: attempt to write a readonly database

The last one is the interesting piece, can you check the file permissions? Should be set up for scm_l10n.

Apparently the push itself succeeded, but wasn't recorded in pushlog. http://hg.mozilla.org/releases/l10n/mozilla-beta/ach is full, but http://hg.mozilla.org/releases/l10n/mozilla-beta/ach/pushloghtml is empty

Can you revert the content so that the pushlog will show the right data on retry?
(In reply to Axel Hecht [:Pike] from comment #0)
> Can you revert the content so that the pushlog will show the right data on
> retry?

hrmm  that's not so easy, or safe to do..  Looking into this.
oddly enough, the pushlog2.db file did have bad perms and that has been fixed..

but that doesn't solve the discrepency yet.
umm..  pushlog2.db is empty on this repo.  Has it ever been used or worked properly?  Is there another repo we can clone this one from?
I just tried to push to this for the first time, it hasn't been used before, and was empty.

The only consumers of that repo are build infras so far, too, through the pushlog data, so it'll appear to be empty to the bots I know.
Assignee: server-ops → server-ops-devservices
Component: Server Operations → Server Operations: Developer Services
QA Contact: phong → shyam
(In reply to Axel Hecht [:Pike] from comment #4)
> I just tried to push to this for the first time, it hasn't been used before,
> and was empty.
> 
> The only consumers of that repo are build infras so far, too, through the
> pushlog data, so it'll appear to be empty to the bots I know.

Ok what was this repo cloned from, I'll wipe it out and start fresh?
This repo was created empty, and I'd prefer to have it set up like that again. I don't have a repo that we could use as a base without having something to push to it afterwards. Just a fresh vanilla repo would be great.
Try it now..  Please let me know.
Hook changegroup.z_loghistory löste eine Ausnahme aus: [Errno 1] Operation not permitted: '/repo/hg/mozilla/releases/l10n/mozilla-beta/ach/.hg/pushlog2.db'

Weird, different error, same result :-(
Corey, any idea?
Bumping severity. Being able to use this repo blocks us from uplifting Acholi to beta.
Severity: normal → major
Assignee: server-ops-devservices → eziegenhorn
hrmm..  I'm not sure why this is.  I've reset it again, please try one more time.
Assignee: eziegenhorn → cshields
What the freck, third try, and yet a different error. Exported LANG=C so that you can read it.

wokbok:ach axelhecht$ hg push
pushing to ssh://hg.mozilla.org/releases/l10n/mozilla-beta/ach/
searching for changes
remote: abort: could not lock repository /repo/hg/mozilla/releases/l10n/mozilla-beta/ach/: Permission denied
abort: unexpected response: empty string

This is pushes from the very same repo.

If that matters, host hg.m.o gives me 63.245.215.25
OK, this still doesn't work, and apparently we're having localization teams for ach-borked-777692 and ach-borked-777692-2 now, looking at https://l10n.mozilla.org/teams/. In other words, please don't create repositories that nobody asked for.
(In reply to Axel Hecht [:Pike] from comment #13)
> OK, this still doesn't work, and apparently we're having localization teams
> for ach-borked-777692 and ach-borked-777692-2 now, looking at
> https://l10n.mozilla.org/teams/. In other words, please don't create
> repositories that nobody asked for.

hah!  these are not repositories that nobody asked for, they are the original repos that you reported as not working.  We don't just delete them but move them away temporarily in case they are needed in process of fixing things.

I'd say it is a bug that https://l10n.mozilla.org/teams just pulls the repos it finds. 

We will delete those as soon as this bug is resolved and you verify it is resolved.
(In reply to Axel Hecht [:Pike] from comment #12)
> What the freck, third try, and yet a different error. Exported LANG=C so
> that you can read it.
> 
> wokbok:ach axelhecht$ hg push
> pushing to ssh://hg.mozilla.org/releases/l10n/mozilla-beta/ach/
> searching for changes
> remote: abort: could not lock repository
> /repo/hg/mozilla/releases/l10n/mozilla-beta/ach/: Permission denied

Thanks, this helps.  The perm issue should now be resolved, please try again.
At least this is an error we had before, but still :-(

wokbok:ach axelhecht$ hg -v push 
pushing to ssh://hg.mozilla.org/releases/l10n/mozilla-beta/ach/
running ssh hg.mozilla.org 'hg -R releases/l10n/mozilla-beta/ach/ serve --stdio'
searching for changes
28 changesets found
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 28 changesets with 1087 changes to 345 files
remote: error: changegroup.z_loghistory hook raised an exception: attempt to write a readonly database

Same state of the repo that we had before, http://hg.mozilla.org/releases/l10n/mozilla-beta/ach/pushloghtml is empty, changesets are there.

I could add --traceback next time to get more details.

Also, we should really figure this out, and not try to post-hoc fix the repo that we have now. I'm the guy that's pushing to new l10n repos in general, and we have a few coming up. That makes somewhat hacking around the issue in this case less attractive.
figured this out and verified with Pike on irc.  New repo was missing the l10n custom hgrc file.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in before you can comment on or make changes to this bug.