AWS RHEL 7 AMI -REPOS正在禁用自己
我们正在使用官方RHEL 7 AMI。
Red Hat Enterprise Linux 7.9（HVM），SSD卷类型-AMI -E9D5EC88
我们正在启用所有存储库，并禁用所有订阅管理，
sudo yum-config-manager --enable rhel-7-server-rhui-extras-rpms
sudo yum-config-manager --enable rhel-7-server-rhui-optional-rpms
sudo yum-config-manager --enable rhel-7-server-rhui-rh-common-rpms
sudo yum-config-manager --enable rhel-7-server-rhui-rpms
sudo yum-config-manager --enable rhel-7-server-rhui-supplementary-rpms
sudo yum-config-manager --enable rhel-server-rhui-rhscl-7-rpms
sudo yum-config-manager --enable rhui-client-config-server-7
subscription-manager config --rhsm.manage_repos=0
subscription-manager config --rhsm.auto_enable_yum_plugins=0
一切看起来都不错。
yum repolist enabled
"Loaded plugins: amazon-id, product-id, search-disabled-repos",
"repo id repo name status",
"epel/x86_64 Extra Packages for E 13,756",
"rhel-7-server-rhui-extras-rpms/x86_64 Red Hat Enterprise L 1,430",
"rhel-7-server-rhui-optional-rpms/7Server/x86_64 Red Hat Enterprise L 23,399",
"rhel-7-server-rhui-rh-common-rpms/7Server/x86_64 Red Hat Enterprise L 243",
"rhel-7-server-rhui-rpms/7Server/x86_64 Red Hat Enterprise L 32,927",
"rhel-7-server-rhui-supplementary-rpms/7Server/x86_64 Red Hat Enterprise L 443",
"rhel-server-rhui-rhscl-7-rpms/7Server/x86_64 Red Hat Software Col 13,928",
"rhui-client-config-server-7/x86_64 Custom Repositories 4",
"repolist: 86,130"
然后sudo yum更新 - y或任何其他百胜命令已运行，并且存储库已重置。
yum repolist enabled
"Loaded plugins: amazon-id, product-id, search-disabled-repos",
"repo id repo name status",
"epel/x86_64 Extra Packages for Enter 13,756",
"rhel-7-server-rhui-rh-common-rpms/7Server/x86_64 Red Hat Enterprise Linux 243",
"rhel-7-server-rhui-rpms/7Server/x86_64 Red Hat Enterprise Linux 32,927",
"rhui-client-config-server-7/x86_64 RHUI Client Configuratio 4",
"repolist: 46,930"
We are using the official RHEL 7 AMI.
Red Hat Enterprise Linux 7.9 (HVM), SSD Volume Type - ami-e9d5ec88
We are enabling all of the repo's, and disabling all the subscription management
sudo yum-config-manager --enable rhel-7-server-rhui-extras-rpms
sudo yum-config-manager --enable rhel-7-server-rhui-optional-rpms
sudo yum-config-manager --enable rhel-7-server-rhui-rh-common-rpms
sudo yum-config-manager --enable rhel-7-server-rhui-rpms
sudo yum-config-manager --enable rhel-7-server-rhui-supplementary-rpms
sudo yum-config-manager --enable rhel-server-rhui-rhscl-7-rpms
sudo yum-config-manager --enable rhui-client-config-server-7
subscription-manager config --rhsm.manage_repos=0
subscription-manager config --rhsm.auto_enable_yum_plugins=0
everything looks good..
yum repolist enabled
"Loaded plugins: amazon-id, product-id, search-disabled-repos",
"repo id repo name status",
"epel/x86_64 Extra Packages for E 13,756",
"rhel-7-server-rhui-extras-rpms/x86_64 Red Hat Enterprise L 1,430",
"rhel-7-server-rhui-optional-rpms/7Server/x86_64 Red Hat Enterprise L 23,399",
"rhel-7-server-rhui-rh-common-rpms/7Server/x86_64 Red Hat Enterprise L 243",
"rhel-7-server-rhui-rpms/7Server/x86_64 Red Hat Enterprise L 32,927",
"rhel-7-server-rhui-supplementary-rpms/7Server/x86_64 Red Hat Enterprise L 443",
"rhel-server-rhui-rhscl-7-rpms/7Server/x86_64 Red Hat Software Col 13,928",
"rhui-client-config-server-7/x86_64 Custom Repositories 4",
"repolist: 86,130"
Then sudo yum update -y or any other yum command is ran, and the repo's are reset.
yum repolist enabled
"Loaded plugins: amazon-id, product-id, search-disabled-repos",
"repo id repo name status",
"epel/x86_64 Extra Packages for Enter 13,756",
"rhel-7-server-rhui-rh-common-rpms/7Server/x86_64 Red Hat Enterprise Linux 243",
"rhel-7-server-rhui-rpms/7Server/x86_64 Red Hat Enterprise Linux 32,927",
"rhui-client-config-server-7/x86_64 RHUI Client Configuratio 4",
"repolist: 46,930"
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
弄清楚了。
应用于AMI上的“ Rh-Amazon-rhui-Clien-client”软件包的更新，以将其从3.0.32版本更新为4.0.4版，导致一次性重置存储库配置。
Figured it out.
An update which is applied to the 'rh-amazon-rhui-client' Red Hat-managed package on the AMI to update it from version 3.0.32 to 4.0.4 causes a one-time reset of the repository configuration.