Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 946994

Summary: [RFE]Provide Validation process to check all services start success or not when configuring them in TUI.
Product: Red Hat Enterprise Linux 6 Reporter: haiyang,dong <hadong>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: acathrow, bsarathy, cboyle, cshao, fdeutsch, gouyang, hadong, jboggs, leiwang, mburns, ovirt-maint, tlavigne, ycui
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-3.0.1-2.el6 Doc Type: Enhancement
Doc Text:
--no tech note required
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-21 19:30:33 UTC Type: Bug
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: 911398    

Description haiyang,dong 2013-04-01 06:50:02 UTC
Description of problem:
For example, when configuring the netconsole service via TUI, the rhev-h only execute "/sbin/service netconsole restart &> /dev/null",
it didn't check that whether this service restart success or not.


Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20130327.0.bz918541.el6_4

How reproducible:
100%
  
Steps to Reproduce:


Actual result:


Expect result:
It' better to Provide Validation process to check all services start success or not when configuring them in TUI.

Additional info:
Seems it only have the indication for CIM,  "CIM Successfully Enabled" 
can be seen on TUI when starting this service success.

Comment 1 Fabian Deutsch 2013-09-18 08:22:54 UTC
This is fixed in 0346d3389ed80fd08041134de3614db5c149602b (and others) which landed during the upstream node-3.0 cycle.

Comment 6 Cheryn Tan 2013-11-08 00:32:07 UTC
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 7 haiyang,dong 2013-11-11 09:10:36 UTC
Test version:
rhevh-6.5-20131031.1.0
ovirt-node-3.0.1-7.el6.noarch

the function "service()" in system.py provide validation process to check all services start success or not, but i notice when configuring the netconsole service via TUI, the rhev-h still only executed "/sbin/service netconsole restart &> /dev/null", didn't use system.service("netconsole", "restart") to check the netconsole service start success or not.

so this bug wasn't fixed, need to re-assigned it.

Comment 8 Fabian Deutsch 2013-12-10 15:46:11 UTC
(In reply to haiyang,dong from comment #7)
> Test version:
> rhevh-6.5-20131031.1.0
> ovirt-node-3.0.1-7.el6.noarch
> 
> the function "service()" in system.py provide validation process to check
> all services start success or not, but i notice when configuring the
> netconsole service via TUI, the rhev-h still only executed "/sbin/service
> netconsole restart &> /dev/null", didn't use system.service("netconsole",
> "restart") to check the netconsole service start success or not.
> 
> so this bug wasn't fixed, need to re-assigned it.

Hey Haiyang,

this bug is about creating a validation process. And that has been fixed with the introduction of the service() function.
I know that there are some remaining service calls which don't use the service() method, but please open separate bugs for them if necessary.

Comment 9 haiyang,dong 2013-12-16 10:05:10 UTC
According to Fabian's comment 8 to verified this bug.

Comment 11 errata-xmlrpc 2014-01-21 19:30:33 UTC
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/RHBA-2014-0033.html