Version: ./openshift-install 4.10.0-0.nightly-2022-01-11-065245 built from commit 28cfc831cee01eb503a2340b4d5365fd281bf867 release image registry.ci.openshift.org/ocp/release@sha256:d9759e7c8ec5e2555419d84ff36aff2a4c8f9367236c18e722a3fe4d7c4f6dee release architecture amd64 Platform: alibabacloud Please specify: * IPI What happened? The NAT gateway and the OSS bucket used by image registry were created in the default resource group, rather than the cluster's one (name 'jiwei-201-ljt5q-rg', id 'rg-aek2pes36c7uzqa'). $ aliyun vpc DescribeNatGateways --RegionId ap-northeast-1 --NatGatewayId ngw-6werhwd0ahuxjdsecql9j --output cols=Name,NatGatewayId,ResourceGroupId,RegionId,VpcId rows=NatGateways.NatGateway[] Name | NatGatewayId | ResourceGroupId | RegionId | VpcId ---- | ------------ | --------------- | -------- | ----- jiwei-201-ljt5q-ngw | ngw-6werhwd0ahuxjdsecql9j | rg-acfnw6kdej3hyai | ap-northeast-1 | vpc-6wed8e8xm2nm71vmaoe51 $ aliyun resourcemanager ListResources --ResourceId jiwei-201-ljt5q-image-registry-ap-northeast-1-ntykktujnntbmipw --endpoint resourcemanager.ap-northeast-1.aliyuncs.com --output cols=Service,ResourceType,ResourceId,ResourceGroupId,RegionId rows=Resources.Resource[] Service | ResourceType | ResourceId | ResourceGroupId | RegionId ------- | ------------ | ---------- | --------------- | -------- oss | bucket | jiwei-201-ljt5q-image-registry-ap-northeast-1-ntykktujnntbmipw | rg-acfnw6kdej3hyai | ap-northeast-1 $ What did you expect to happen? They should be created in the cluster's resource group. How to reproduce it (as minimally and precisely as possible)? Always. Anything else we need to know? $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.0-0.nightly-2022-01-11-065245 True False 34m Cluster version is 4.10.0-0.nightly-2022-01-11-065245 $ oc get nodes NAME STATUS ROLES AGE VERSION jiwei-201-ljt5q-master-0 Ready master 67m v1.22.1+6859754 jiwei-201-ljt5q-master-1 Ready master 42m v1.22.1+6859754 jiwei-201-ljt5q-master-2 Ready master 67m v1.22.1+6859754 jiwei-201-ljt5q-worker-ap-northeast-1a-47nq4 Ready worker 55m v1.22.1+6859754 jiwei-201-ljt5q-worker-ap-northeast-1b-52qwm Ready worker 52m v1.22.1+6859754 $
Sorry, please ignore the NAT gateway issue, it's caused by the VPC is in the default resource group. If without customized VPC, the NAT gateway does be in the cluster's resource group. Thanks!
When image-Registry creates a bucket, there is no way to get the corresponding ResourceGroupID
I have just confirmed with the OSS TEAM that resource groups are not supported by OSS at present and are expected to be supported in April 2022.
I understand the comment 3 that it works as expected today.
(In reply to mengxiaobing from comment #3) > I have just confirmed with the OSS TEAM that resource groups are not > supported by OSS at present and are expected to be supported in April 2022. @xiameng Could you please confirm again whether OSS supports the option "--ResourceGroupId" (or something) now? Thanks!
Any progress @xiameng , why this is closed not bug without resolution? Please confirm whether we support --ResourceGroupId now?
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days