Bug 781472
| Summary: | Subscription Asset Manager options should be disabled if network is disable. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Chris Pelland <cpelland> |
| Component: | ovirt-node | Assignee: | Joey Boggs <jboggs> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.2 | CC: | acathrow, apevec, bsarathy, cpelland, cshao, gouyang, jboggs, leiwang, mburns, mkhusid, moli, ovirt-maint, pm-eus, sgordon, ycui |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-node-2.0.2-0.14.3.git3eac501.el6_2.5 | Doc Type: | Bug Fix |
| Doc Text: |
In previous versions of Red Hat Enterprise Virtualization, it was possible to configure Subscription Asset Manager on hypervisors without a functional network connection.
Now, configuration of Subscription Asset Manager requires a functional network connection.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-02-15 16:10:13 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: | 752348 | ||
| Bug Blocks: | |||
|
Description
Chris Pelland
2012-01-13 15:12:33 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
In previous versions of Red Hat Enterprise Virtualization, it was possible to configure Subscription Asset Manager on hypervisors without a functional network connection.
Now, configuration of Subscription Asset Manager requires a functional network connection.
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. http://rhn.redhat.com/errata/RHSA-2012-0109.html |