Bug 1228249 – "Server with newer configure next run" icon not documented

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1228249 - "Server with newer configure next run" icon not documented

Summary:	"Server with newer configure next run" icon not documented

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	Documentation (Show other bugs)
Sub Component:
Version:	3.5.1
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	3.5.0
Assigned To:	Tahlia Richardson
QA Contact:	Megan Lewis
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1265080
	Show dependency tree / graph

Reported:	2015-06-04 09:29 EDT by Robert McSwain
Modified:	2015-10-20 06:12 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-10-20 06:12:41 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Image of icon in question (8.90 KB, image/jpeg) 2015-06-04 09:30 EDT, Robert McSwain	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Robert McSwain 2015-06-04 09:29:46 EDT

Description of problem:
The orange icon which signifying requested changes/updates will be made to the system on next boot and produces a "Server with newer configure next run" message, is not documented. 

Version-Release number of selected component (if applicable):
3.5 Documentation

Comment 1 Robert McSwain 2015-06-04 09:30:30 EDT

Created attachment 1034721 [details]
Image of icon in question

Comment 2 Andrew Dahms 2015-06-21 21:38:50 EDT

Assigning to Tahlia for review.

Tahlia - for this bug, all we need to do is ensure the above icon is documented somewhere in the User Guide and possibly in the Administration Guide.

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