Bug 1751310 - Please split out udev rules into separate package
Summary: Please split out udev rules into separate package
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: google-compute-engine-guest-configs
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: ericedens
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-11 17:17 UTC by Micah Abbott
Modified: 2022-12-13 15:13 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:13:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Micah Abbott 2019-09-11 17:17:22 UTC
This package is currently shipping two udev rules file relevant to GCP:

* /usr/lib/udev/rules.d/64-gce-disk-removal.rules
* /usr/lib/udev/rules.d/65-gce-disk-naming.rules


Those rules have no dependency on the agent binary itself.

For Fedora CoreOS, we are interested in providing those rules on GCP images, but we are not shipping the py3 environment to install/run the agents.

As such, it would be helpful to split out the udev rules into a separate binary RPM (generated from this same source), so that they can be installed without the rest of the agent.

Comment 1 Ben Cotton 2020-02-11 17:56:11 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 2 Fedora Program Management 2021-04-29 15:57:42 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Neal Gompa 2021-04-30 10:51:39 UTC
google-compute-engine-tools has been retired and replaced with google-compute-engine-guest-configs, which no longer has a Python dependency.

Comment 4 Ben Cotton 2021-08-10 12:46:24 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Comment 5 remoe 2022-01-21 16:31:37 UTC
I've tried to install this package on FCOS 35: https://github.com/coreos/fedora-coreos-tracker/issues/1073#issuecomment-1018652155 with following error:

error: Checkout google-compute-engine-guest-configs-20201207.00-8.fc35.noarch: Hardlinking 36/a1140d8cba2b0f03e47c87220dcc9f12296265496f7009d78d4cd231de511e.file to 65-gce-disk-naming.rules: File exists

Comment 6 Benjamin Gilbert 2022-01-21 17:33:38 UTC
@the.rubist Correct, because FCOS currently ships that file directly.

Comment 7 Ben Cotton 2022-11-29 16:46:44 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 8 Ben Cotton 2022-12-13 15:13:28 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.