Bug 2231060
| Summary: | [RFE] AIX Patching Support | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Sameh Attia <sattia> |
| Component: | Hosts - Content | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.13.2 | CC: | ahumbe, aruzicka, jlenz |
| Target Milestone: | Unspecified | Keywords: | FutureFeature, MigratedToJIRA, RFE |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-06-06 16:26:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Sameh Attia
2023-08-10 12:13:10 UTC
Case #03583065 the customer is asking for AIX patching support since the supported clients architecture at [1] does not include AIX. Also, created a Jira ticket at https://issues.redhat.com/browse/SAT-19452 [1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/satellite_overview_concepts_and_deployment_considerations/introduction_to_server_planning#sect-Architecture_Supported_Client_Architectures Could you please elaborate a bit on what you exactly mean by patching in this context? Do you want to be able to "just" kick of patching on AIX systems, having them pull content from external sources or do you want to manage AIX content (packages and stuff) in satellite itself? Yes Adam. The customer needs to have AIX supported in Satellite like RHEL exactly, a content host, REX, dashboard, console, ... etc to be a supported client. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |