Bug 2039304 - [IPI on Alibabacloud] OSS bucket used by image registry is put in the default resource group unexpectedly
Summary: [IPI on Alibabacloud] OSS bucket used by image registry is put in the default...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Oleg Bulatov
QA Contact: XiuJuan Wang
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-11 13:25 UTC by Jianli Wei
Modified: 2023-09-15 01:50 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-01-12 10:12:55 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Jianli Wei 2022-01-11 13:25:51 UTC
./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:

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)?

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

Comment 1 Jianli Wei 2022-01-11 14:00:44 UTC
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!

Comment 2 mengxiaobing 2022-01-12 04:41:55 UTC
When image-Registry creates a bucket, there is no way to get the corresponding ResourceGroupID

Comment 3 mengxiaobing 2022-01-12 06:52:40 UTC
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.

Comment 4 Oleg Bulatov 2022-01-12 10:12:55 UTC
I understand the comment 3 that it works as expected today.

Comment 6 Jianli Wei 2022-06-20 02:38:00 UTC
(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!

Comment 7 Bin Hu 2022-09-12 04:02:41 UTC
Any progress @xiameng , why this is closed not bug without resolution? Please confirm whether we support --ResourceGroupId now?

Comment 8 Red Hat Bugzilla 2023-09-15 01:50:59 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days

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