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 1096818 - setregdomain sometimes fails silently, without reporting error and/or nonzero exitcode
Summary: setregdomain sometimes fails silently, without reporting error and/or nonzero...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: crda
Version: 7.0
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: 7.1
Assignee: John W. Linville
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1082756 1123440
TreeView+ depends on / blocked
 
Reported: 2014-05-12 13:33 UTC by Karel Volný
Modified: 2015-03-05 07:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 07:54:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0340 0 normal SHIPPED_LIVE crda bug fix update 2015-03-05 12:22:23 UTC

Description Karel Volný 2014-05-12 13:33:14 UTC
Filed from caserun https://tcms.engineering.redhat.com/run/118979/#caserun_5066159

Version-Release number of selected component (if applicable):
crda-1.1.3_2013.11.27-5.el7.x86_64

Steps to Reproduce: 
run the test /CoreOS/crda/Regression/bz1071983-regulatory-domain-no-longer-get-set


Actual results: 
Timezone information not found!  Unable to set regulatory domain.
:: [ 05:46:01 ] :: [ INFO    ] :: rlRun: command = 'setregdomain'; exitcode = 0; expected = 1
:: [   FAIL   ] :: Trying 'setregdomain' (should fail) (Expected 1, got 0)

...

:: [ 13:46:08 ] :: [ INFO    ] :: rlRun: command = 'setregdomain'; exitcode = 0; expected = 0
:: [   PASS   ] :: Trying 'setregdomain' (Expected 0, got 0)
:: [   PASS   ] :: File '/var/tmp/tmp.mHy25RLHAs' should not contain 'unable' 
May  7 01:46:08 intel-sugarbay-do-01 logger: bz1071983-marker-copy
:: [   FAIL   ] :: File 'copy.log' should contain 'Calling CRDA for country: CN' 
:: [   PASS   ] :: File 'copy.log' should not contain 'world' 
:: [   FAIL   ] :: ChiNa should be set (Assert: US should equal CN)


Expected results:
nonzero exit codes from setregdomain calls(*) and appropriate error message in the second part

(*) well, in fact, the second call should not end in an error but that is another problem - and until it is fixed, error should be reported

Comment 8 errata-xmlrpc 2015-03-05 07:54:39 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.

https://rhn.redhat.com/errata/RHBA-2015-0340.html


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