Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693180 - MachineSet and Machine pages need Event page for resources page consistency
Summary: MachineSet and Machine pages need Event page for resources page consistency
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.1.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-27 09:52 UTC by XiaochuanWang
Modified: 2019-03-27 19:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description XiaochuanWang 2019-03-27 09:52:48 UTC
Description of problem:
MachineSet and Machine pages need Event page for consistency among resource pages. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Cluster admin user create a MachineSet and Machines, or check existed Machineset/Machine.
2. oc describe machineset example-ms
3. oc describe machine

Actual results:
1. There is no Event sub-page for MachineSet / Machine 
2. $ oc describe machineset example-ms
Name:         example-ms
Namespace:    xiaocwan-admin
Events:                    <none>

3. Same as step2

Expected results:
2&3. Both MachineSet/Machine should have Event page, showing the reason why there is any error or warning.

Additional info:

Comment 1 Samuel Padgett 2019-03-27 19:39:37 UTC
This is simple to add if machines and machine sets have events, and we should be showing it to be consistent with other resources. I'm going to make this a low severity bug to investigate.

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