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 1417954 - RFE - Disable default asynchronous output to the terminal from mdadm
Summary: RFE - Disable default asynchronous output to the terminal from mdadm
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mdadm
Version: 6.8
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: XiaoNi
QA Contact: guazhang@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-31 13:54 UTC by John Pittman
Modified: 2017-12-06 10:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:40:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description John Pittman 2017-01-31 13:54:01 UTC 
Description of problem:

In some cases, mdadm prints asynchronous output to the terminal by default.  Asynchronous work is expected by mdadm, for example with grow action, but not output to the terminal.

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

mdadm-3.3.4-1.el6_8.5.x86_64

How reproducible:

[root@host ~]# mdadm --grow --raid-devices=3 /dev/md0 --add /dev/vdd
  mdadm: level of /dev/md0 changed to raid4
  mdadm: added /dev/vdd
[root@rhel6 ~]# mdadm: level of /dev/md0 changed to raid0 

Steps to Reproduce:

Any grow operation should reproduce.

Actual results:

Asynchronous output is printed to the terminal.

Expected results:

This type of output to the terminal is neither expected nor desired.  Printing to log files or even the console asynchronously is fine, but not to the cli (in these tests I was connected via ssh).

Possible resolutions:
 - Move the level change messages to md and print to log file as "kernel: md: some message"
 - Increase the verbosity of asynchronous messages and note that increasing verbosity of command may produce async cli messages in man page.

I know this is cosmetic, hence the low severity.  It's the same upstream as far as I can tell as well.  Admins are prepared to watch mdstat, but generally don't want informational messages interrupting their ssh sessions.
Comment 3 Jan Kurik 2017-12-06 10:40:43 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Note You need to log in before you can comment on or make changes to this bug.