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 1415972 - [RFE]openstack_manila plugin required to capture configuration and logs from openstack manila setup
Summary: [RFE]openstack_manila plugin required to capture configuration and logs from ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sos
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Moravec
QA Contact: Miroslav Hradílek
URL: https://github.com/sosreport/sos/pull...
Whiteboard:
: 1438932 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-24 09:44 UTC by Poornima
Modified: 2023-09-14 03:52 UTC (History)
14 users (show)

Fixed In Version: sos-3.4-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 23:08:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Result file which explains tha patch https://github.com/sosreport/sos/pull/906 been verified on osp10 (714.63 KB, application/x-xz)
2017-02-13 10:56 UTC, Anandprakash Tandale
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2203 0 normal SHIPPED_LIVE sos bug fix and enhancement update 2017-08-01 19:41:56 UTC

Description Poornima 2017-01-24 09:44:28 UTC
1. Proposed title of this feature request: 
Ans: [RFE]openstack_manila plugin required to capture configuration and logs from openstack manila setup

2. Who is the customer behind the request?
Ans: Ecosystem and Red Hat offering manila certifications https://access.redhat.com/documentation/en/red-hat-openstack-certification/10/paged/red-hat-openstack-certification-policy-guide/chapter-9-openstack-manila  

3. What is the nature and description of the request?
Ans: sos plugin is required to capture OpenStack manila related information.
This is needed to get openstack system environment details
and must be enabled plugin when running on manila deployments.

4. How would the customer like to achieve this? (List the functional requirements here)
Ans:Just like other sos plugins for openstack_neutron, openstack_cinder customer will be using manila plugin 'sosreport -o openstack_manila'.
which is redundant with only plugins tagges as well.
This plugin also needs to have  openstack profiles coverage
'sosreport -p openstack' capturing manila configurations and logs.

5. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Ans:yes we shared a patch to upstream sosreport project.
git hub Issue tracker:https://github.com/sosreport/sos/pull/906

6. Is the sales team involved in this request and do they have any additional input?
Ans: no

7. List any affected packages or components.
Ans: sos

11. Would the customer be able to assist in testing this functionality if implemented?
Ans: yes (certification QE team will help in testing this plugin)

Comment 4 Anandprakash Tandale 2017-02-13 10:52:45 UTC
https://github.com/sosreport/sos/pull/906 been verified on osp10 manila

Comment 5 Anandprakash Tandale 2017-02-13 10:56:00 UTC
Created attachment 1249791 [details]
Result file which explains tha patch https://github.com/sosreport/sos/pull/906 been verified on osp10

Comment 6 Pavel Moravec 2017-02-13 13:00:32 UTC
(In reply to Anandprakash Tandale from comment #4)
> https://github.com/sosreport/sos/pull/906 been verified on osp10 manila

Thanks for the verification.

Upstream hasnt accepted the PR yet, theoretically there can be changes applied (I am not sure whats the upstream PR status, now). And definitely for "real QE work" I suggest verifying against RHEL7.4 RPM that will be available around devel freeze time.

Comment 7 Pavel Moravec 2017-02-19 14:23:09 UTC
(In reply to Pavel Moravec from comment #6)
> (In reply to Anandprakash Tandale from comment #4)
> > https://github.com/sosreport/sos/pull/906 been verified on osp10 manila
> 
> Thanks for the verification.
> 
> Upstream hasnt accepted the PR yet, theoretically there can be changes
> applied (I am not sure whats the upstream PR status, now). And definitely
> for "real QE work" I suggest verifying against RHEL7.4 RPM that will be
> available around devel freeze time.

Anand (or Poornima),
would you be able to do the verification on candidate RPM for 7.4, once available?

Our QE would appreciate it.

Comment 8 Poornima 2017-02-22 10:26:22 UTC
(In reply to Pavel Moravec from comment #7)
> (In reply to Pavel Moravec from comment #6)
> > (In reply to Anandprakash Tandale from comment #4)
> > > https://github.com/sosreport/sos/pull/906 been verified on osp10 manila
> > 
> > Thanks for the verification.
> > 
> > Upstream hasnt accepted the PR yet, theoretically there can be changes
> > applied (I am not sure whats the upstream PR status, now).

Hey pavel thanks for details 
Here is status of PR I have verified the output files, data and captured by this plugins with manila SME's they gave go green from manila side. So PR is waiting for bmr hand to move ahead.

> > for "real QE work" I suggest verifying against RHEL7.4 RPM that will be
> > available around devel freeze time.
> 
> Anand (or Poornima),
> would you be able to do the verification on candidate RPM for 7.4, once
> available?
> 
> Our QE would appreciate it.

Please share us details of candidate RPM for 7.4 once out over here.
If QE team has bandwidth they can test it.

Comment 10 Pavel Moravec 2017-03-24 19:27:45 UTC
POSTed to upstream as https://github.com/sosreport/sos/commit/60895a4c5ee363e1c457a16e731fc56851b1ded2

Comment 12 Pavel Moravec 2017-04-05 13:24:45 UTC
*** Bug 1438932 has been marked as a duplicate of this bug. ***

Comment 14 Tom Barron 2017-04-05 13:51:22 UTC
The business justification for this backport is that SOS reports are essential to Red Hat's support capability, which is itself central to our subscription business model.  Currently we are shipping Red Hat Open Stack Storage Platform version 10 with GA support status for manila with the NetApp backend.  But because the manila SOS plugin is not available for RHEL 7.3 and OSP10 uses RHEL 7.3 our support capability is currently crippled for manila.

Comment 17 Pavel Moravec 2017-04-10 08:43:56 UTC
Steve,
there is a 7.3 z-stream request (see some more background in bz1438932) for this RFE/Improvement. Could you please evaluate (business justification in $c14) and if you agree, add PMApproved to let it clone?

From devel perspective, backport shall be trivial.

Thanks.

Comment 19 Pavel Moravec 2017-04-27 18:35:39 UTC
(In reply to Poornima from comment #8)
> (In reply to Pavel Moravec from comment #7)
> > (In reply to Pavel Moravec from comment #6)
> > Anand (or Poornima),
> > would you be able to do the verification on candidate RPM for 7.4, once
> > available?
> > 
> > Our QE would appreciate it.
> 
> Please share us details of candidate RPM for 7.4 once out over here.
> If QE team has bandwidth they can test it.

Poornima,
See brew build https://brewweb.engineering.redhat.com/brew/rpminfo?rpmID=4647392 for OtherQE.

Comment 20 Pavel Moravec 2017-05-02 06:47:01 UTC
(In reply to Pavel Moravec from comment #19)
> (In reply to Poornima from comment #8)
> > (In reply to Pavel Moravec from comment #7)
> > > (In reply to Pavel Moravec from comment #6)
> > > Anand (or Poornima),
> > > would you be able to do the verification on candidate RPM for 7.4, once
> > > available?
> > > 
> > > Our QE would appreciate it.
> > 
> > Please share us details of candidate RPM for 7.4 once out over here.
> > If QE team has bandwidth they can test it.
> 
> Poornima,
> See brew build
> https://brewweb.engineering.redhat.com/brew/rpminfo?rpmID=4647392 for
> OtherQE.

Hello Poornima,
could you please verify this BZ against (updated/new) build:

https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=552080

or directly against package:

https://brewweb.engineering.redhat.com/brew/rpminfo?rpmID=4647392

?

Thanks in advance.

Comment 21 Miroslav Hradílek 2017-05-24 15:25:08 UTC
I can confirm that the plugin was added. If there is no positive feedback from the customer I will verify this SanityOnly.

# rpm -qf /usr/lib/python2.7/site-packages/sos/plugins/openstack_manila.py
sos-3.4-4.el7.noarch

# cat /usr/lib/python2.7/site-packages/sos/plugins/openstack_manila.py
. . .
    def setup(self):
        super(RedHatManila, self).setup()
        self.add_copy_spec("/etc/sudoers.d/manila")
. . .

Comment 27 Dustin Schoenbrun 2017-06-07 20:52:18 UTC
I was able to install the sos-3.3-5.bz1415972.el7_3.noarch RPM on my OSP-11 system and I was able to run the SOS Report successfully. The generated tarball did contain correct data for the Manila logs and configuration files and no other plugin failed to generate their report. The only nit I have is that the description of the Manila SOS plugin needs a space between "OpenStack" and "Manila". Other than that, it looks great to me.

Comment 30 errata-xmlrpc 2017-08-01 23:08:12 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://access.redhat.com/errata/RHBA-2017:2203

Comment 31 Red Hat Bugzilla 2023-09-14 03:52:39 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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