View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000364 | Rocky-Linux-8 | [Repo] Extras | public | 2022-10-02 10:01 | 2022-10-02 13:42 |
| Reporter | Shahid Hussain | Assigned To | Neil Hanlon | ||
| Priority | high | Severity | major | Reproducibility | always |
| Status | closed | Resolution | unable to reproduce | ||
| Platform | Rocky Linux | OS | Rocky Linux | OS Version | 8.5 |
| Summary | 0000364: Package naming convention is not followed for mod_ssl | ||||
| Description | Standard linux package follows the naming convention as mod-ssl (with hyphen between) but in rocky linux it is declared as mod_ssl (with underscore). In Centos 7 too this package is mod-ssl ( with hyphen which is correct). Fix : change package name from mod_ssl to mod-ssl [root@abc/]# yum -y install mod-ssl Last metadata expiration check: 0:01:22 ago on Sun Oct 2 09:35:33 2022. No match for argument: mod-ssl Error: Unable to find a match: mod-ssl | ||||
| Steps To Reproduce | yum -y install mod-ssl | ||||
| Additional Information | [root@acd /]# yum -y install mod-ssl Last metadata expiration check: 0:01:22 ago on Sun Oct 2 09:35:33 2022. No match for argument: mod-ssl Error: Unable to find a match: mod-ssl | ||||
| Tags | mod-ssl | ||||
|
Shahid, Do you have a third-party repo on your CentOS machine? Just a thought to explain why you are saying there is a difference. On a CentOS 7 machine: sudo yum list *mod_ssl* Installed Packages mod_ssl.x86_64 1:2.4.6-97.el7.centos.5 @updates sudo yum list *mod-ssl* Error: No matching Packages to list Rocky is not changing the package name. It just uses the spec file provided by the package maintainer. Regards, Michael |
|
|
Apologize for causing inconvenience !. It was an error in our procedure!. It was a part of Docker image creation. I am closely monitored now! Centos too failed to install via mod-ssl but not terminating the image creation process so I was not able to figure out but Rocky linux is terminating the image creation process. We were upgrading all our microservices to use rocky linux from Centos! I appreciate your prompt response!. This is first time I did mistake while opening a bug!. |
|
|
No problem at all. We're glad you were able to resolve the issue. If you're installing via kickstart, the reason it may not work on rocky is because you are specifying %packages --ignoremissing for CentOS, but not for Rocky. Without --ignoremissing, the installation will halt/abort if a specified package cannot be installed. I'd actually recommend keeping that flag removed as it will help you ensure that your kickstarts are Correct I'll close this out, but please feel free to post on the forums, in chat/irc, or on the mailing lists if you'd like to continue the discussion! |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-10-02 10:01 | Shahid Hussain | New Issue | |
| 2022-10-02 10:01 | Shahid Hussain | Tag Attached: mod-ssl | |
| 2022-10-02 11:31 | Michael Young | Note Added: 0000628 | |
| 2022-10-02 13:28 | Shahid Hussain | Note Added: 0000629 | |
| 2022-10-02 13:41 | Neil Hanlon | Note Added: 0000630 | |
| 2022-10-02 13:42 | Neil Hanlon | Assigned To | => Neil Hanlon |
| 2022-10-02 13:42 | Neil Hanlon | Status | new => closed |
| 2022-10-02 13:42 | Neil Hanlon | Resolution | open => unable to reproduce |