rocky-release-cloud package enables cloud-kernel repo by default #1
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Membership
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sig_cloud/meta#1
Loading…
Reference in New Issue
Block a user
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?
The
rocky-release-cloud
is the only package that provides two repos with both enabled automatically:It is normal for a package to provide one or more repos, which may include an always-on "common" repo while all other repos stay disabled. In this instance, users may not want to use a kernel that is not destined for their cloud (for example, the kernel would not be necessary on openstack, oracle cloud, or aws).
https://git.rockylinux.org/staging/src/rocky-release-cloud/-/blob/r9/SOURCES/Rocky-SIG-Cloud-Kernel.repo#L16
Tentative fixes:
Need to coordinate with Google in order to make sure their image builds enable this.
https://github.com/GoogleCloudPlatform/compute-image-tools/blob/master/daisy_workflows/image_build/enterprise_linux/kickstart/rocky_linux_9_optimized_gcp.cfg
I will sign the CLA (if I haven't yet) and open a PR so we can time this.
https://github.com/GoogleCloudPlatform/compute-image-tools/blob/master/daisy_workflows/image_build/enterprise_linux/kickstart/rocky_linux_9_optimized_gcp.cfg#L108-L116
actually, looks like we're fine.
Approved by me
Confirmed with Zach at google this should be fine!