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 1111517 - can not return instance as an output argument from method
Summary: can not return instance as an output argument from method
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: konkretcmpi
Version: 7.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Vitezslav Crhonek
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1111527
TreeView+ depends on / blocked
 
Reported: 2014-06-20 08:35 UTC by Michal Minar
Modified: 2020-03-04 11:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1111527 (view as bug list)
Environment:
Last Closed: 2020-03-04 11:27:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
patch fixing this issue (1.11 KB, patch)
2014-06-20 08:35 UTC, Michal Minar
no flags Details | Diff

Description Michal Minar 2014-06-20 08:35:41 UTC
Created attachment 910689 [details]
patch fixing this issue

Description of problem:
  Konkret generator generates bad type signature into header files for instance parameters. This averts instances to be returned as output argument from any method.

Version-Release number of selected component (if applicable):
  konkretcmpi-0.9.1-5.el7

How reproducible:
  ALWAYS

Steps to Reproduce:
1. try to return CMPIInstance as an output argument from method (for example CIM_ConcreteJob.GetError()
2. call this implemented method from client (lmishell)
   

Actual results:
  broker will return weird error:
    CIMError: (1, u'CIM_ERR_FAILED: The byte sequence starting at index 1 is not valid UTF-8 encoding:   0xFC 0x03 0xA8 0xF3 0x7F') ?
  it tries to store CMPIInstance as an string and fails on UTF-8 encoding error

Expected results:
  client receives CMPIInstance as expected

Additional info:

Comment 3 Vitezslav Crhonek 2020-03-04 11:27:44 UTC
Red Hat Enterprise Linux version 7 entered the Maintenance Support 1 Phase in August 2019. In this phase only qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. Other errata advisories may be delivered as appropriate.

This bug has been reviewed by Support and Engineering representative and does not meet the inclusion criteria for Maintenance Support 1 Phase. If this issue still exists in newer major version of Red Hat Enterprise Linux, it has been cloned there and work will continue in the cloned bug.

For more information about Red Hat Enterprise Linux Lifecycle, please see https://access.redhat.com/support/policy/updates/errata/


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