Infrastructure/fedora-infrastructure
5
0
Fork 0
Code Issues 68 Pull requests Projects Releases Packages Wiki Activity Actions

tar errors out when creating hard links (aarch64 flatpak issue) #9532

New issue
Closed
opened 2020-12-15 11:55:06 +00:00 by kalev · 19 comments
kalev commented 2020-12-15 11:55:06 +00:00
Copy link

I ran into an issue with aarch64 flatpaks where tar is erroring out when creating hard links. The koji task is https://koji.fedoraproject.org/koji/taskinfo?taskID=57503246 and the matching x86_64 build went fine. aarch64 reproducibly errors out with:

tar: files/lib/python3.9/site-packages/hydrapaper/__pycache__/__main__.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/__main__.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/app_window.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/app_window.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/apply_wallpapers.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/apply_wallpapers.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/confManager.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/confManager.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/get_desktop_environment.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/get_desktop_environment.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/headerbar.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/headerbar.cpython-39.opt-1.pyc’: No such file or directory
tar: files/lib/python3.9/site-packages/hydrapaper/__pycache__/is_image.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/is_image.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/listbox_helper.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/listbox_helper.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/main_stack.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/main_stack.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/monitor_parser.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/monitor_parser.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/monitors_flowbox.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/monitors_flowbox.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/settings_box.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/settings_box.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/singleton.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/singleton.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/threading_helper.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/threading_helper.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpaper_flowbox_item.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpaper_flowbox_item.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpaper_merger.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpaper_merger.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpapers_flowbox.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpapers_flowbox.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpapers_folder_listbox_row.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpapers_folder_listbox_row.cpython-39.opt-1.pyc’: No such file or directory
tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpapers_folders_view.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpapers_folders_view.cpython-39.opt-1.pyc’: No such file or directory
tar: Exiting with failure status due to previous errors
2020-12-15 11:28:36,608 - atomic_reactor.plugin - DEBUG - Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/atomic_reactor/plugin.py", line 268, in run
    plugin_response = plugin_instance.run()
  File "/usr/lib/python3.9/site-packages/atomic_reactor/plugins/prepub_flatpak_create_oci.py", line 116, in run
    ref_name, outfile, tarred_outfile = self.builder.build_container(tarred_filesystem)
  File "/usr/lib/python3.9/site-packages/flatpak_module_tools/flatpak_builder.py", line 882, in build_container
    ref_name = self._create_app_oci(tarred_filesystem, outfile)
  File "/usr/lib/python3.9/site-packages/flatpak_module_tools/flatpak_builder.py", line 736, in _create_app_oci
    subprocess.check_call(['tar', 'xCfz', builddir, tarred_filesystem])
  File "/usr/lib64/python3.9/subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['tar', 'xCfz', '/tmp/tmpideyjdf6/build', '/tmp/tmpideyjdf6/filesystem.tar.gz']' returned non-zero exit status 2.

I am not sure what's going on: could it be something to do with how the file system is mounted that causes tar to error out? Is it a file system that doesn't support hard links (or doesn't support hard links that point to a different directory)?

I ran into an issue with aarch64 flatpaks where tar is erroring out when creating hard links. The koji task is https://koji.fedoraproject.org/koji/taskinfo?taskID=57503246 and the matching x86_64 build went fine. aarch64 reproducibly errors out with: ``` tar: files/lib/python3.9/site-packages/hydrapaper/__pycache__/__main__.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/__main__.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/app_window.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/app_window.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/apply_wallpapers.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/apply_wallpapers.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/confManager.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/confManager.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/get_desktop_environment.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/get_desktop_environment.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/headerbar.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/headerbar.cpython-39.opt-1.pyc’: No such file or directory tar: files/lib/python3.9/site-packages/hydrapaper/__pycache__/is_image.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/is_image.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/listbox_helper.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/listbox_helper.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/main_stack.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/main_stack.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/monitor_parser.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/monitor_parser.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/monitors_flowbox.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/monitors_flowbox.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/settings_box.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/settings_box.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/singleton.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/singleton.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/threading_helper.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/threading_helper.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpaper_flowbox_item.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpaper_flowbox_item.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpaper_merger.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpaper_merger.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpapers_flowbox.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpapers_flowbox.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpapers_folder_listbox_row.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpapers_folder_listbox_row.cpython-39.opt-1.pyc’: No such file or directory tar: var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpapers_folders_view.cpython-39.pyc: Cannot hard link to ‘var/tmp/flatpak-build/app/lib/python3.9/site-packages/hydrapaper/__pycache__/wallpapers_folders_view.cpython-39.opt-1.pyc’: No such file or directory tar: Exiting with failure status due to previous errors 2020-12-15 11:28:36,608 - atomic_reactor.plugin - DEBUG - Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/atomic_reactor/plugin.py", line 268, in run plugin_response = plugin_instance.run() File "/usr/lib/python3.9/site-packages/atomic_reactor/plugins/prepub_flatpak_create_oci.py", line 116, in run ref_name, outfile, tarred_outfile = self.builder.build_container(tarred_filesystem) File "/usr/lib/python3.9/site-packages/flatpak_module_tools/flatpak_builder.py", line 882, in build_container ref_name = self._create_app_oci(tarred_filesystem, outfile) File "/usr/lib/python3.9/site-packages/flatpak_module_tools/flatpak_builder.py", line 736, in _create_app_oci subprocess.check_call(['tar', 'xCfz', builddir, tarred_filesystem]) File "/usr/lib64/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['tar', 'xCfz', '/tmp/tmpideyjdf6/build', '/tmp/tmpideyjdf6/filesystem.tar.gz']' returned non-zero exit status 2. ``` I am not sure what's going on: could it be something to do with how the file system is mounted that causes tar to error out? Is it a file system that doesn't support hard links (or doesn't support hard links that point to a different directory)?
mobrien commented 2020-12-15 14:22:50 +00:00
Copy link

Metadata Update from @mobrien:

  • Issue assigned to mobrien
**Metadata Update from @mobrien**: - Issue assigned to mobrien
smooge commented 2020-12-15 14:23:27 +00:00
Copy link

I don't know enough about how OSBS (Open Shift Build System) composes flatpacks for any architecture. @otaylor can you give some pointed on what to look at?

I don't know enough about how OSBS (Open Shift Build System) composes flatpacks for any architecture. @otaylor can you give some pointed on what to look at?
smooge commented 2020-12-15 14:23:28 +00:00
Copy link

Metadata Update from @smooge:

  • Issue priority set to: Waiting on Assignee (was: Needs Review)
  • Issue tagged with: OSBS, medium-gain, medium-trouble, ops, releng
**Metadata Update from @smooge**: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: OSBS, medium-gain, medium-trouble, ops, releng
mobrien commented 2020-12-15 14:37:10 +00:00
Copy link

I'm just going to have a look at this now to see if it was caused by the installation but my knowledge of flatpaks is limited so any assistance is appreciated

I'm just going to have a look at this now to see if it was caused by the installation but my knowledge of flatpaks is limited so any assistance is appreciated
kalev commented 2020-12-15 14:54:59 +00:00
Author
Copy link

Thanks! I'm not very knowledgeable how atomic reactor works, but when looking through the two logs (x86_64.log that succeeded and aarch64.log that failed) it stands out that the failed one says that docker uses:

"Driver": "overlay2",

and the one that succeeds says:

Driver": "devicemapper",

I don't know if that's what causing the issue, but might be related? Could it be that overlayfs doesn't support all the hard link features that Fedora rpm contents uses?

Thanks! I'm not very knowledgeable how atomic reactor works, but when looking through the two logs (x86_64.log that succeeded and aarch64.log that failed) it stands out that the failed one says that docker uses: "Driver": "overlay2", and the one that succeeds says: Driver": "devicemapper", I don't know if that's what causing the issue, but might be related? Could it be that overlayfs doesn't support all the hard link features that Fedora rpm contents uses?
mobrien commented 2020-12-15 15:27:34 +00:00
Copy link

@kalev that is likely the issue, we came to a similar conclusion independently. Not sure if this is something we can fix easily. I'll do some investigation

@kalev that is likely the issue, we came to a similar conclusion independently. Not sure if this is something we can fix easily. I'll do some investigation
mobrien commented 2020-12-15 15:44:09 +00:00
Copy link

There is a reasonably high amount of work involved in changing it so I wouldn't be able to promise the change anytime soon. Its something that would need to be discussed as it would probably need an outage as well

There is a reasonably high amount of work involved in changing it so I wouldn't be able to promise the change anytime soon. Its something that would need to be discussed as it would probably need an outage as well
kalev commented 2020-12-15 17:51:25 +00:00
Author
Copy link

Fair enough, thanks. I'll do some tests in the mean time and try to figure out how many flatpaks are affected.

Fair enough, thanks. I'll do some tests in the mean time and try to figure out how many flatpaks are affected.
kalev commented 2020-12-17 10:34:37 +00:00
Author
Copy link

I've found two more flatpaks that fail the same way: gnome-music and gedit. That is out of ~30 I've tried to build so far. It should be easy enough to work this around in individual flatpak container.yaml by adding

platforms:
    only: x86_64

... so it's not super urgent to get the infra side fixed :)

I've found two more flatpaks that fail the same way: gnome-music and gedit. That is out of ~30 I've tried to build so far. It should be easy enough to work this around in individual flatpak container.yaml by adding ``` platforms: only: x86_64 ``` ... so it's not super urgent to get the infra side fixed :)
mobrien commented 2020-12-17 15:36:59 +00:00
Copy link

Thanks for looking into this @kalev hopefully we will get it resolved in the new year

Thanks for looking into this @kalev hopefully we will get it resolved in the new year
otaylor commented 2020-12-18 17:10:17 +00:00
Copy link

Talking about this with kalev, we figured out what is going wrong - it's a question of how flatpak-module-tools manipulates python tarfile.TarInfo headers when rewriting paths. If a path goes from > 100 to < 100 bytes, then the member.name field is changed, but member.pax_headers is left untouched and ends up overriding the name.

I'm not sure yet why we're seeing this:

  • Only with python-3.9 ?
  • In some cases only on aarch64 ?

But I do know why it it's not happening with local builds - the paths we rewrite in that case are different and shorter. In any case, I'll come up with a fixed version of flatpak-module-tools and that should resolve this - nothing to do with filesystem drivers :-)

Talking about this with kalev, we figured out what is going wrong - it's a question of how flatpak-module-tools manipulates python tarfile.TarInfo headers when rewriting paths. If a path goes from > 100 to < 100 bytes, then the member.name field is changed, but member.pax_headers is left untouched and ends up overriding the name. I'm not sure yet why we're seeing this: - Only with python-3.9 ? - In some cases only on aarch64 ? But I do know why it it's not happening with local builds - the paths we rewrite in that case are different and shorter. In any case, I'll come up with a fixed version of flatpak-module-tools and that should resolve this - nothing to do with filesystem drivers :-)
otaylor commented 2020-12-18 17:15:39 +00:00
Copy link

Only with python-3.9

Probably this is actually "only with Python-3.8 and newer" - in Python-3.8, the default format for the tarfile module was changed from GNU_FORMAT to PAX_FORMAT

> Only with python-3.9 Probably this is actually "only with Python-3.8 and newer" - in Python-3.8, the default format for the tarfile module was changed from GNU_FORMAT to PAX_FORMAT
otaylor commented 2020-12-18 20:55:31 +00:00
Copy link

OK, fixed the bug upstream, built a new version for Fedora, submitted f32/f33 updates:

https://bodhi.fedoraproject.org/updates/FEDORA-2020-c4773405c8

When you have a chance, please update the buildroot to contain this python3-flatpak-module-tools - hopefully that will resolve this issue.

OK, fixed the bug upstream, built a new version for Fedora, submitted f32/f33 updates: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c4773405c8 When you have a chance, please update the buildroot to contain this python3-flatpak-module-tools - hopefully that will resolve this issue.
mobrien commented 2020-12-21 11:48:41 +00:00
Copy link

@otaylor I've updated the buildroot container on the aarch64 builders with the updated version of python3-flatpak-module-tools. Let me know if it solves the issue.

@otaylor I've updated the buildroot container on the aarch64 builders with the updated version of python3-flatpak-module-tools. Let me know if it solves the issue.
otaylor commented 2020-12-21 14:49:47 +00:00
Copy link

I've updated the buildroot container on the aarch64 builders with the updated version of python3-flatpak-module-tools.

https://koji.fedoraproject.org/koji/buildinfo?buildID=1660933 completed successfully on aarch64, so I think we can consider this fixed.

Could we get this updated for x86_64 as well? #9538 and #9542 are manifestations of the same issue on x86_64.

> I've updated the buildroot container on the aarch64 builders with the updated version of python3-flatpak-module-tools. https://koji.fedoraproject.org/koji/buildinfo?buildID=1660933 completed successfully on aarch64, so I think we can consider this fixed. Could we get this updated for x86_64 as well? #9538 and #9542 are manifestations of the same issue on x86_64.
mobrien commented 2020-12-21 14:55:10 +00:00
Copy link

Ok great! I have added the change to the x86_64 nodes now too.

Ok great! I have added the change to the x86_64 nodes now too.
mobrien commented 2020-12-21 14:55:11 +00:00
Copy link

Metadata Update from @mobrien:

  • Issue close_status updated to: Fixed
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @mobrien**: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
kevin commented 2021-01-28 19:07:09 +00:00
Copy link

Issue status updated to: Open (was: Closed)

Issue status updated to: Open (was: Closed)
kevin commented 2021-01-28 19:10:29 +00:00
Copy link

Issue status updated to: Closed (was: Open)
Issue close_status updated to: Fixed

Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
announcement

   
authentication

Authentication related issues

  
automate

   
aws

Issues related to Amazon Web Services

  
backlog

Tasks that will take longer then ~4 hours to do

  
blocked

Issue is blocked

  
bodhi

Issues with Bodhi

  
ci

Continuous Integration

  
Closed As
Duplicate
Closed with the reason of Duplicate

  
Closed As
Fixed
Closed with the reason of Fixed

  
Closed As
Fixed with Explanation
Closed with the reason of Fixed with Explanation

  
Closed As
Initiative Worthy
Closed with the reason of Initiative Worthy

  
Closed As
Insufficient data
Closed with the reason of Insufficient data

  
Closed As
Invalid
Closed with the reason of Invalid

  
Closed As
Spam
Closed with the reason of Spam

  
Closed As
Upstream
Closed with the reason of Upstream

  
Closed As
Will Not or Can Not fix
Closed with the reason of Will Not/Can Not fix

  
cloud

Items in FedoraInfraCloud or COmmunishift

  
communishift

issues/questions about os.edorainfracloud.org ( Community OpenShift)

  
copr

COPR system (run by other team)

  
database

Issues related to databases

  
deprecated

Tools which Infrastructure may not be able to fix

  
dev

Tasks requiring some dev work

  
discourse

outsourced tool

  
dns

Changes or problems with DNS

  
downloads

rsync,dl.fp.o,AWS,torrents

  
easyfix

   
epel

Issues relating to epel

  
factory2

Generic issues for the factory2 team

  
firmitas

   
gitlab

   
greenwave

Issues with greenwave

  
hardware

Problem is with Fedora Infrastructure Owned/Leased Hardware

  
help wanted

   
high-gain

task that gets us a lot / is important / makes many people happy

  
high-trouble

task that is complex/long/difficult

  
iad2

Something to do with the iad2 datacenter

  
koji

Issues with the build system

  
koschei

Items needing Koschei team

  
lists

issues with lists

  
low-gain

tasks that gets us little / isn't very important / makes only 1 person or few happy

  
low-trouble

task that is easy/short

  
mbs

Issues with mbs.fedoraproject.org

  
medium-gain

task that gets us some / is somewhat important / makes some people happy

  
medium-trouble

task that is medium complex / difficult

  
mini-initiative

Something that is bigger than one person but not a full initiative

  
mirrorlists

Way to tell systems where downloads are

  
monitoring

   
Needs investigation

   
notifier

   
odcs

On Demand Compose Service issues

  
OpenShift

Issues with OpenShift

  
ops

ops problem now...

  
OSBS

OpenShift Build System issues in Fedora

  
outage

   
packager_workflow_blocker

Blocks the packager workflow

  
pagure

Issues with pagure.io

  
permissions

Items which need permissions set in outside tools

  
Priority
Needs Review
Priority of Needs Review

  
Priority
Next Meeting
Priority of Next Meeting

  
Priority
🔥 URGENT 🔥
Priority of 🔥 URGENT 🔥

  
Priority
Waiting on Assignee
Priority of Waiting on Assignee

  
Priority
Waiting on External
Priority of Waiting on External

  
Priority
Waiting on Reporter
Priority of Waiting on Reporter

  
rabbitmq

issues with the message broker

  
rdu-cc

Items doing with RDU Community Cage

  
release-monitoring

release-monitoring.org (Anitya)

  
releng

For problems which should be in the releng ticket system

  
repoSpanner

Issues with repoSpanner

  
request-for-resources

   
s390x

The secondary architecture hardware and problems related with it

  
security

   
SMTP

Email issues outside of lists (DMARC, SPF, aliases)

  
src.fp.o

Issues related to src.fedoraproject.org

  
staging

Issues in staging

  
taiga

outsourced tool

  
unfreeze

Patches to be applied after freeze is lifted

  
waiverdb

Issues with waiverdb

  
websites-general

General items with a website focus

  
wiki

Issues with the Wiki

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 or 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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/fedora-infrastructure#9532
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?