#10285 503 error when visiting apps.fedoraproject.org/packages and links broken
Closed: Fixed a month ago by kevin. Opened 2 months ago by leo.

If you visit https://apps.fedoraproject.org/packages, you see a 503 error. https://apps.fedoraproject.org is fine.

Additionally, in the apps catalog there are several broken links:
Most of the things under In Development are broken, and the FAS entry redirects to FAS2, which is no longer in use.


https://apps.fedoraproject.org/packages were replaced by https://packages.fedoraproject.org/

We just need to fix the link where it's broken.

Here are few places where it's pointing to wrong target:
https://src.fedoraproject.org/
https://apps.fedoraproject.org/#Packages

@leo Could you update the list with the broken links?

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: dev, high-trouble, medium-gain

2 months ago

Yeah. Broken links:

In Development:

Jenkins
Faitout
Taiga
Ipsilon (description also broken)

Accounts

FAS points to FAS2 (which is deprecated)

QA

Taskotron has been sunset

Packaging

Darkserver
PkgDB
Tagger
Packages

Also, some links point to https://fedmsg.com for the fmsg-bus, but the domain doesn't exist (anymore?)

Metadata Update from @ryanlerch:
- Issue assigned to ryanlerch

a month ago

Ok, so some of these have were fixed, but the changed apps.yaml file that lives in ansible wasnt being updated when the playbook was run. (that part was commented out for some reason). I have updated the playbook so it updates stg with the updated file, which fixes some of these issues (comments inline)

Yeah. Broken links:

In Development:

Jenkins
Faitout
Taiga

these 3 are no longer showing up

Ipsilon (description also broken)

this is still broken

Accounts

FAS points to FAS2 (which is deprecated)

this points to accounts.fp.o, but still reads "FAS" -- should change that

QA

Taskotron has been sunset

this still needs to be removed

Packaging

Darkserver
PkgDB
Tagger

these 3 are all gone

Packages

this still needs to be fixed

Also, some links point to https://fedmsg.com for the fmsg-bus, but the domain doesn't exist (anymore?)

the fedmsg.com references in descriptions are still there and need to be fixed.

before changing any of this, i really need to make sure that the these two files are in sync:

there appears to be changes on both sides that we want to keep. So going to work on getting the one in ansible correct, then copying that to the github repo

Ok, so some of these have were fixed, but the changed apps.yaml file that lives in ansible wasnt being updated when the playbook was run. (that part was commented out for some reason).

I think it was commented out because there is an apps.yaml in the upstream repo
as well and it had got updated there, so there was a more recent version in the
RPM than in ansible then.

oh, okay

the top of that file says to keep them manually in sync, so I have just manually merged the changes between those files, and they now match in both sources.

next, going to resolve the issues raised above, and push them to staging.

I think going forward, until an alternative for apps.fp.o is developed (if ever), we should just use the apps.yaml file from ansible, and copy the changes over to the apps.fp.o github

that way we can easily change links if we have to without spinning up a new release (i dont forsee any changes to the inner workings of apps.fp.o other than a full re-write)

okay, also filed this PR:

https://pagure.io/fedora-infra/ansible/pull-request/854

that removes the staging conditional, so after the freeze, we should just need to merge 854, then run the playbook, and close this one off.

Metadata Update from @ryanlerch:
- Issue priority set to: Waiting on External (was: Waiting on Assignee)

a month ago

I'm pushing this out now. :)

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a month ago

Login to comment on this ticket.

Metadata
Boards 1
dev Status: Backlog