Bug 517601
| Summary: | unable to use the SSM to ks systems that have different rhel base channels | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | wes hayutin <whayutin> | ||||||||
| Component: | Provisioning | Assignee: | Tomas Lestach <tlestach> | ||||||||
| Status: | CLOSED DEFERRED | QA Contact: | Red Hat Satellite QA List <satqe-list> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 530 | CC: | jsherril, mmccune | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| URL: | https://test1182.test.redhat.com/rhn/systems/ssm/kickstart/KickstartableSystems.do | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2014-07-04 13:24:59 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 462714 | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 357511 [details]
ss2
Created attachment 357512 [details]
ss3
HA HA caused by A kickstart was not scheduled for rlx-3-18.rhndev.redhat.com because the package profile did not contain the 'up2date' package. An update of that system's package profile may be required. please verify that bug is fixed!!! Please ALSO change the ssm to report the error properly as it does in the sdc. |
Created attachment 357510 [details] ss1 Description of problem: unable to use the SSM to ks systems that have different rhel base channels 1. register a rhel4 box, give provisioning entitlement 2. register a rhel5 box give provisioning entitlement 3. create a ks profile 4. use the ssm to kickstart the boxes to the same ks profile get Successfully scheduled 0 system(s) for provisioning.