Bug 909974 - [abrt] pcs-0.9.27-3.fc18: resource.py:942:resource_start:IndexError: list index out of range
Summary: [abrt] pcs-0.9.27-3.fc18: resource.py:942:resource_start:IndexError: list ind...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pcs
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Chris Feist
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ee188dd991c00aa0ae5d4d6b2b3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-11 15:02 UTC by gabicr
Modified: 2014-02-05 23:15 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 23:15:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (592 bytes, text/plain)
2013-02-11 15:02 UTC, gabicr
no flags Details
File: core_backtrace (361 bytes, text/plain)
2013-02-11 15:02 UTC, gabicr
no flags Details
File: environ (2.15 KB, text/plain)
2013-02-11 15:02 UTC, gabicr
no flags Details

Description gabicr 2013-02-11 15:02:17 UTC
Version-Release number of selected component:
pcs-0.9.27-3.fc18

Additional info:
cmdline:        /usr/bin/python /usr/sbin/pcs resource start
executable:     /usr/sbin/pcs
kernel:         3.7.5-201.fc18.x86_64
uid:            0

Truncated backtrace:
resource.py:942:resource_start:IndexError: list index out of range

Traceback (most recent call last):
  File "/usr/sbin/pcs", line 87, in <module>
    main(sys.argv[1:])
  File "/usr/sbin/pcs", line 69, in main
    resource.resource_cmd(argv)
  File "/usr/lib/python2.7/site-packages/pcs/resource.py", line 76, in resource_cmd
    resource_start(argv)
  File "/usr/lib/python2.7/site-packages/pcs/resource.py", line 942, in resource_start
    args = ["crm_resource", "-r", argv[0], "-m", "-d", "target-role"]
IndexError: list index out of range

Local variables in innermost frame:
argv: []

Comment 1 gabicr 2013-02-11 15:02:20 UTC
Created attachment 696134 [details]
File: backtrace

Comment 2 gabicr 2013-02-11 15:02:22 UTC
Created attachment 696135 [details]
File: core_backtrace

Comment 3 gabicr 2013-02-11 15:02:24 UTC
Created attachment 696136 [details]
File: environ

Comment 4 Chris Feist 2013-02-11 21:22:58 UTC
This error is occurring because a resource name must be present to start a resource.

It's fixed upstream with this commit

https://github.com/feist/pcs/commit/0fd633bd4c78c445cd7e0eef36186f0335b9acb9

Comment 5 Fedora End Of Life 2013-12-21 15:38:48 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2014-02-05 23:15:46 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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