StarlingX

  1. Bug #2045627
  2. Activity log

Activity log for bug #2045627

Date Who What changed Old value New value Message
2023-12-05 07:43:35 TaoWang bug added bug
2023-12-05 07:43:45 TaoWang starlingx: assignee TaoWang (twang4)
2023-12-05 07:44:50 TaoWang tags stx.9.0 stx.distcloud
2023-12-05 07:53:52 TaoWang description Brief Description Creation of subcloud peer group/system peer is successful for irrelevant name. Severity Minor Steps to Reproduce Run the below command: [sysadmin@controller-0 ~(keystone_admin)]$ dcmanager subcloud-peer-group add -peer-group-name 5* --max-subcloud-rehoming 1 -----------------------------------------------------------+ Field Value -----------------------------------------------------------+ id 15 peer_group_name 5-* group_priority 0 group_state enabled system_leader_id ecf72a34-07d2-471c-8b74-1ae38da17f63 system_leader_name wrcpeng-dc40-1-system-controller max_subcloud_rehoming 1 created_at 2023-12-04 10:39:59.830078 updated_at None -----------------------------------------------------------+ [sysadmin@controller-0 ~(keystone_admin)]$ dcmanager subcloud-peer-group show 15 -----------------------------------------------------------+ Field Value -----------------------------------------------------------+ id 15 peer_group_name 5-* group_priority 0 group_state enabled system_leader_id ecf72a34-07d2-471c-8b74-1ae38da17f63 system_leader_name wrcpeng-dc40-1-system-controller max_subcloud_rehoming 1 created_at 2023-12-04 10:39:59.830078 updated_at None -----------------------------------------------------------+ [sysadmin@controller-0 ~(keystone_admin)]$ Expected Behavior Should have some logic to validate the name which should be more appropriate Actual Behavior Allowed to create the peer group with irrelevant name. Reproducibility Yes System Configuration http://128.224.150.21/jenkins/view/All/job/wrcpeng-distributed_cloud-40_1_System_Controller Load info (eg: 2022-03-10_20-00-07) 23.09 Last Pass Timestamp/Logs Alarms Test Activity Feature Testing Workaround NA Brief Description Creation of subcloud peer group/system peer is successful for irrelevant name. Severity Minor Steps to Reproduce Run the below command: [sysadmin@controller-0 ~(keystone_admin)]$ dcmanager subcloud-peer-group add -peer-group-name 5* --max-subcloud-rehoming 1 -----------------------------------------------------------+ Field Value -----------------------------------------------------------+ id 15 peer_group_name 5-* group_priority 0 group_state enabled system_leader_id ecf72a34-07d2-471c-8b74-1ae38da17f63 system_leader_name wrcpeng-dc40-1-system-controller max_subcloud_rehoming 1 created_at 2023-12-04 10:39:59.830078 updated_at None -----------------------------------------------------------+ [sysadmin@controller-0 ~(keystone_admin)]$ dcmanager subcloud-peer-group show 15 -----------------------------------------------------------+ Field Value -----------------------------------------------------------+ id 15 peer_group_name 5-* group_priority 0 group_state enabled system_leader_id ecf72a34-07d2-471c-8b74-1ae38da17f63 system_leader_name wrcpeng-dc40-1-system-controller max_subcloud_rehoming 1 created_at 2023-12-04 10:39:59.830078 updated_at None -----------------------------------------------------------+ [sysadmin@controller-0 ~(keystone_admin)]$ Expected Behavior Should have some logic to validate the name which should be more appropriate Actual Behavior Allowed to create the peer group with irrelevant name. Reproducibility Yes Workaround NA
2023-12-05 08:24:11 OpenStack Infra starlingx: status New In Progress
2024-01-12 15:54:06 OpenStack Infra starlingx: status In Progress Fix Released
2024-04-10 14:08:12 Ghada Khalil starlingx: importance Undecided Low