#9678 Search in web interface of Fedora Containers Registry is not working
Closed: Fixed 3 years ago by kevin. Opened 3 years ago by ibotty.

Can you point me to the source of the web interface backing
https://registry.fedoraproject.org

I would create a merge request fixing it.


Hi @ibotty, the package that we use is https://src.fedoraproject.org/rpms/reg the upstream source is https://github.com/genuinetools/reg. Thank you for helping us.

Metadata Update from @humaton:
- Issue tagged with: dev, low-gain, medium-trouble

3 years ago

Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

3 years ago

The current version of reg used to generate registry.fedoraproject.org pages is quite old.
I'm in the process of upgrading the version available in Fedora repos (see #9657).

However, the fix for this issue is already been posted upstream (https://github.com/genuinetools/reg/pull/200/files) and it is already applied as a patch to the version currently available in Fedora repos. Strangely, the patch is not present in the js file on the server...

> curl -I 'https://registry.fedoraproject.org/js/scripts.js'  | grep last-modified
last-modified: Wed, 05 Sep 2018 19:08:39 GMT

Tells me, that an old version is picked up.

I looked a bit into the ansible scripts. That was the first time though so beware my wild musings.
I assume the proxy is not picking up the changes, because I cannot imagine the rsync not to copy the new version (rsync -a should pick up changes) unless the timestamp on the webservers are wrong, but why should they.

Just checked, the patch was applied in 0.15.5-7 while EPEL7 version is stuck at 0.15.5-1.

I'll try to cherry-pick the change and do a rebuild.

I updated reg on sundries01{stg}. Should sync the new content out soon.

Looks like it's fixed. Thanks everyone!

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

3 years ago

Metadata Update from @ibotty:
- Issue status updated to: Open (was: Closed)

3 years ago

Yes, it's a cloudfront cache in front of it. It should refresh here soon.

ok, it's updated now.

Let us know if you see anything further.

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

3 years ago

Login to comment on this ticket.

Metadata
Boards 1
dev Status: Done