Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1685719 - Satellite 6.5 Tech Preview Features
Summary: Satellite 6.5 Tech Preview Features
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: 6.5.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: Sergei Petrosian
QA Contact: Vlada Grosu
URL:
Whiteboard:
Depends On: 1658510 1669648
Blocks: 1685544
TreeView+ depends on / blocked
 
Reported: 2019-03-05 21:42 UTC by Karie
Modified: 2019-03-07 07:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1658510
Environment:
Last Closed: 2019-03-06 13:04:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 7 Sergei Petrosian 2019-03-06 13:04:57 UTC
The changes are live on the master and 6.5-beta branches.


Note You need to log in before you can comment on or make changes to this bug.