Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1365349

Summary: Duplicated service ids with different status are listed in services page after "mark" operation.
Product: Red Hat Enterprise Linux 7 Reporter: Wei Wang <weiwang>
Component: cockpitAssignee: Martin Pitt <mpitt>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: low Docs Contact:
Priority: low    
Version: 7.2CC: anilsson, bugs, cshao, huiwa, huzhao, jscotka, leiwang, mvollmer, yaniwang, ycui
Target Milestone: pre-dev-freezeKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-15 07:44:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1329957    
Attachments:
Description Flags
picture
none
log files none

Description Wei Wang 2016-08-09 03:21:33 UTC
Created attachment 1189009 [details]
picture

Description of problem:
Duplicated service ids with different status are listed in services page after "mark" operation.

Version-Release number of selected component (if applicable):
RHVH-7.2-20160804.0-RHVH-x86_64-dvd1.iso
imgbased-0.7.4-0.1.el7ev.noarch
cockpit-0.114-2.el7.x86_64
cockpit-ovirt-dashboard-0.10.6-1.3.4.el7ev.noarch


How reproducible:
100%
Not Regression bug
Keywords: UI

Steps to Reproduce:
1. Install RHVH-7.2-20160804.0-RHVH-x86_64-dvd1.iso (default ks file)
2. Login cockpit website hostIP:9090 with root account
3. Select "Services" page
4. Select "System Services"
5. Select one service which status is empty, e.g: serial-getty@.service
6. Input the hostname of host, then click "instantiate" button
7. Enable it , then click "Mark" option menu
8. Go back to services page, check the <service name>@<hostname>.service


Actual results:
Duplicated service ids with different status are listed in services page after "mark" operation.


Expected results:
Duplicated services id should not be displayed.



Additional info:

Comment 1 Wei Wang 2016-08-09 03:24:49 UTC
Created attachment 1189010 [details]
log files

Comment 2 Fabian Deutsch 2016-08-09 10:23:01 UTC
The image shows a template and an instance.

The instance should probably also include the device which it was instantiated for.

Comment 4 Dominik Perpeet 2016-08-09 11:37:46 UTC
Andreas, how should cockpit display this?

Comment 6 RHEL Program Management 2020-12-15 07:44:16 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.