Bug 1317733
| Summary: | [RFE] As a user I want to see ostree information published in an environment | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Partha Aji <paji> | ||||
| Component: | Content Management | Assignee: | Partha Aji <paji> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Sachin Ghai <sghai> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.2.0 | CC: | bbuckingham, bkearney, sghai, sthirugn | ||||
| Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://projects.theforeman.org/issues/13720 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-07-27 09:27:29 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: | 1321771 | ||||||
| Attachments: |
|
||||||
|
Description
Partha Aji
2016-03-15 02:47:29 UTC
Created from redmine issue http://projects.theforeman.org/issues/13720 Upstream bug assigned to paji Here are the screen shots of the ui change this feature will add -> https://partha.fedorapeople.org/ostree-prs/PR-5879/ Moving to POST since upstream bug http://projects.theforeman.org/issues/13720 has been closed ------------- Partha Aji Applied in changeset commit:katello|92c2d4366a85975e1954f6c548150f47323c1bcd. Verified with sat6.2 beta snap6 I can see ostree repo count in webUI. Please see the attached sreenshot. Created attachment 1143740 [details]
ostree repo info available on lifecycle-env page on webUI
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501 |