User can not update email address in src.fedoraproject.org #8372
Labels
No labels
announcement
authentication
automate
aws
backlog
blocked
bodhi
ci
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Initiative Worthy
Closed As
Insufficient data
Closed As
Invalid
Closed As
Spam
Closed As
Upstream
Closed As/Will Not
Can Not fix
cloud
communishift
copr
database
deprecated
dev
discourse
dns
downloads
easyfix
epel
factory2
firmitas
gitlab
greenwave
hardware
help wanted
high-gain
high-trouble
iad2
koji
koschei
lists
low-gain
low-trouble
mbs
medium-gain
medium-trouble
mini-initiative
mirrorlists
monitoring
Needs investigation
notifier
odcs
OpenShift
ops
OSBS
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
rdu-cc
release-monitoring
releng
repoSpanner
request-for-resources
s390x
security
SMTP
src.fp.o
staging
taiga
unfreeze
waiverdb
websites-general
wiki
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#8372
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@pkfed can not update their mailing email address in src.fedoraproject.org. The problem is in pagure code and needs some manual work to fix. @pingou did this on pagure.io but did not on src.fedoraproject.org since that has a different set of production rules. This ticket is to track permissions to make changes to src.fedoraproject.org by @mohanboddu and @kevin
The problem is with the "star" button on the user. It is read-only and can not be updated.
In both pagure.io and src.fp.o, the interface does not allow altering the default email address when multiple email addresses appear. It looks like very similar javascript code is being used in both areas, but the underlying data stores are different (pagure.io vs src.fp.o) .
I've updated the database for @pkfed in src.fp.o.
@jlanda is working on the fix upstream.
I hope we'll be able to cut a pagure release upstream in the coming weeks with all the changes that we have landed.
Sorry for the inconvenience :(
Oh and the for record here are the commands I ran:
Metadata Update from @pingou:
https://pagure.io/pagure/pull-request/4657
I could prepare an ansible hotfix task for {stg.,}{pagure.io,src.fp.o} if needed