Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v9 #1473

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

red-hat-konflux[bot]
Copy link
Contributor

@red-hat-konflux red-hat-konflux bot commented Dec 9, 2024

This PR contains the following updates:

Package Type Update Change
registry.access.redhat.com/ubi9/go-toolset final major 1.21.11-7 -> 9.5-1739801907
registry.access.redhat.com/ubi9/go-toolset stage major 1.21.11-7 -> 9.5-1739801907

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Configuration

📅 Schedule: Branch creation - "before 5am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.

This PR has been generated by MintMaker (powered by Renovate Bot).

Copy link

openshift-ci bot commented Dec 9, 2024

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a konflux-ci member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/main/registry.access.redhat.com-ubi9-go-toolset-9.x branch from 66be69c to 11a2032 Compare December 23, 2024 08:33
@dheerajodha
Copy link
Member

/retest

@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/main/registry.access.redhat.com-ubi9-go-toolset-9.x branch from 11a2032 to 78fd41d Compare January 13, 2025 08:31
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/main/registry.access.redhat.com-ubi9-go-toolset-9.x branch from 78fd41d to 0720ce6 Compare January 27, 2025 08:55
Copy link

openshift-ci bot commented Jan 27, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign rhopp for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v9 chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v9 - autoclosed Feb 1, 2025
@red-hat-konflux red-hat-konflux bot closed this Feb 1, 2025
@red-hat-konflux red-hat-konflux bot deleted the konflux/mintmaker/main/registry.access.redhat.com-ubi9-go-toolset-9.x branch February 1, 2025 08:54
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v9 - autoclosed chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v9 Feb 1, 2025
@red-hat-konflux red-hat-konflux bot restored the konflux/mintmaker/main/registry.access.redhat.com-ubi9-go-toolset-9.x branch February 1, 2025 20:57
@red-hat-konflux red-hat-konflux bot reopened this Feb 1, 2025
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/main/registry.access.redhat.com-ubi9-go-toolset-9.x branch 2 times, most recently from a514f6f to db9d2d3 Compare February 6, 2025 00:12
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/main/registry.access.redhat.com-ubi9-go-toolset-9.x branch 2 times, most recently from 7a026fa to 36ca02b Compare February 12, 2025 00:58
… tag to v9

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/main/registry.access.redhat.com-ubi9-go-toolset-9.x branch from 36ca02b to 499b295 Compare February 18, 2025 00:35
@konflux-ci-qe-bot
Copy link

@red-hat-konflux[bot]: The following test has Failed, say /retest to rerun failed tests.

PipelineRun Name Status Rerun command Build Log Test Log
konflux-e2e-cmpvj Failed /retest View Pipeline Log View Test Logs

Inspecting Test Artifacts

To inspect your test artifacts, follow these steps:

  1. Install ORAS (see the ORAS installation guide).
  2. Download artifacts with the following commands:
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/e2e-tests:konflux-e2e-cmpvj

Test results analysis

🚨 Failed to provision a cluster, see the log for more details:

Click to view logs
INFO: Log in to your Red Hat account...
INFO: Configure AWS Credentials...
WARN: The current version (1.2.47) is not up to date with latest rosa cli released version (1.2.50).
WARN: It is recommended that you update to the latest version.
INFO: Logged in as 'konflux-ci-418295695583' on 'https://api.openshift.com'
INFO: Create ROSA with HCP cluster...
WARN: The current version (1.2.47) is not up to date with latest rosa cli released version (1.2.50).
WARN: It is recommended that you update to the latest version.
INFO: Creating cluster 'kx-f85b838d49'
INFO: To view a list of clusters and their status, run 'rosa list clusters'
INFO: Cluster 'kx-f85b838d49' has been created.
INFO: Once the cluster is installed you will need to add an Identity Provider before you can login into the cluster. See 'rosa create idp --help' for more information.

Name: kx-f85b838d49
Domain Prefix: kx-f85b838d49
Display Name: kx-f85b838d49
ID: 2h0ok7cs40v8n3lekkdo8s4jlek14f9d
External ID: faae346b-fb35-4302-a1f4-e9e3ae0b61a2
Control Plane: ROSA Service Hosted
OpenShift Version: 4.15.44
Channel Group: stable
DNS: Not ready
AWS Account: 418295695583
AWS Billing Account: 418295695583
API URL:
Console URL:
Region: us-east-1
Availability:

  • Control Plane: MultiAZ
  • Data Plane: SingleAZ

Nodes:

  • Compute (desired): 3
  • Compute (current): 0
    Network:
  • Type: OVNKubernetes
  • Service CIDR: 172.30.0.0/16
  • Machine CIDR: 10.0.0.0/16
  • Pod CIDR: 10.128.0.0/14
  • Host Prefix: /23
  • Subnets: subnet-05b9daa0609597f68, subnet-04cf6376374bf9e09
    EC2 Metadata Http Tokens: optional
    Role (STS) ARN: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Installer-Role
    Support Role ARN: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Support-Role
    Instance IAM Roles:
  • Worker: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Worker-Role
    Operator IAM Roles:
  • arn:aws:iam::418295695583:role/rosa-hcp-openshift-cloud-network-config-controller-cloud-credent
  • arn:aws:iam::418295695583:role/rosa-hcp-kube-system-control-plane-operator
  • arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kms-provider
  • arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kube-controller-manager
  • arn:aws:iam::418295695583:role/rosa-hcp-kube-system-capa-controller-manager
  • arn:aws:iam::418295695583:role/rosa-hcp-openshift-image-registry-installer-cloud-credentials
  • arn:aws:iam::418295695583:role/rosa-hcp-openshift-ingress-operator-cloud-credentials
  • arn:aws:iam::418295695583:role/rosa-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials
    Managed Policies: Yes
    State: waiting (Waiting for user action)
    Private: No
    Delete Protection: Disabled
    Created: Feb 18 2025 00:45:23 UTC
    User Workload Monitoring: Enabled
    Details Page: https://console.redhat.com/openshift/details/s/2tBxyRf2HTCAZX1ZOOlpLYzEDLW
    OIDC Endpoint URL: https://oidc.op1.openshiftapps.com/2du11g36ejmoo4624pofphlrgf4r9tf3 (Managed)
    Etcd Encryption: Disabled
    Audit Log Forwarding: Disabled
    External Authentication: Disabled
    Zero Egress: Disabled

INFO: Preparing to create operator roles.
INFO: Operator Roles already exists
INFO: Preparing to create OIDC Provider.
INFO: OIDC provider already exists
INFO: To determine when your cluster is Ready, run 'rosa describe cluster -c kx-f85b838d49'.
INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-f85b838d49 --watch'.
INFO: Track the progress of the cluster creation...
WARN: The current version (1.2.47) is not up to date with latest rosa cli released version (1.2.50).
WARN: It is recommended that you update to the latest version.
�[0;33mW:�[m Region flag will be removed from this command in future versions
INFO: Cluster 'kx-f85b838d49' is in waiting state waiting for installation to begin. Logs will show up within 5 minutes
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-f85b838d49 Version
2025-02-18 00:49:15 +0000 UTC hostedclusters kx-f85b838d49 ValidAWSIdentityProvider StatusUnknown
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Condition not found in the CVO.
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Condition not found in the CVO.
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 The hosted control plane is not found
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 The hosted control plane is not found
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 The hosted control plane is not found
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 The hosted control plane is not found
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 The hosted control plane is not found
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Condition not found in the CVO.
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Waiting for hosted control plane to be healthy
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Condition not found in the CVO.
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Condition not found in the CVO.
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 The hosted control plane is not found
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Ignition server deployment not found
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Configuration passes validation
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 HostedCluster is supported by operator configuration
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Release image is valid
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 The hosted control plane is not found
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Reconciliation active on resource
2025-02-18 00:49:18 +0000 UTC hostedclusters kx-f85b838d49 HostedCluster is at expected version
2025-02-18 00:49:19 +0000 UTC hostedclusters kx-f85b838d49 Required platform credentials are found
2025-02-18 00:49:19 +0000 UTC hostedclusters kx-f85b838d49 failed to get referenced secret ocm-production-2h0ok7cs40v8n3lekkdo8s4jlek14f9d/cluster-api-cert: Secret "cluster-api-cert" not found
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-f85b838d49 Version
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Release image is valid
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Ignition server deployment not found
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Condition not found in the CVO.
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Condition not found in the CVO.
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Waiting for hosted control plane kubeconfig to be created
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 HostedCluster is supported by operator configuration
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Condition not found in the CVO.
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Condition not found in the CVO.
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Condition not found in the CVO.
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Reconciliation active on resource
2025-02-18 00:49:17 +0000 UTC hostedclusters kx-f85b838d49 Configuration passes validation
2025-02-18 00:49:18 +0000 UTC hostedclusters kx-f85b838d49 HostedCluster is at expected version
2025-02-18 00:49:19 +0000 UTC hostedclusters kx-f85b838d49 Required platform credentials are found
2025-02-18 00:51:02 +0000 UTC hostedclusters kx-f85b838d49 OIDC configuration is valid
2025-02-18 00:51:02 +0000 UTC hostedclusters kx-f85b838d49 Reconciliation completed successfully
2025-02-18 00:51:03 +0000 UTC hostedclusters kx-f85b838d49 WebIdentityErr
2025-02-18 00:51:05 +0000 UTC hostedclusters kx-f85b838d49 All is well
2025-02-18 00:51:05 +0000 UTC hostedclusters kx-f85b838d49 lookup api.kx-f85b838d49.ze2b.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-02-18 00:51:05 +0000 UTC hostedclusters kx-f85b838d49 capi-provider deployment has 1 unavailable replicas
2025-02-18 00:51:05 +0000 UTC hostedclusters kx-f85b838d49 Configuration passes validation
2025-02-18 00:51:05 +0000 UTC hostedclusters kx-f85b838d49 AWS KMS is not configured
2025-02-18 00:51:05 +0000 UTC hostedclusters kx-f85b838d49 Waiting for etcd to reach quorum
2025-02-18 00:51:05 +0000 UTC hostedclusters kx-f85b838d49 Kube APIServer deployment not found
2025-02-18 00:51:13 +0000 UTC hostedclusters kx-f85b838d49 All is well
2025-02-18 00:52:06 +0000 UTC hostedclusters kx-f85b838d49 EtcdAvailable QuorumAvailable
2025-02-18 00:53:09 +0000 UTC hostedclusters kx-f85b838d49 Kube APIServer deployment is available
2025-02-18 00:53:14 +0000 UTC hostedclusters kx-f85b838d49 All is well
2025-02-18 00:53:46 +0000 UTC hostedclusters kx-f85b838d49 The hosted control plane is available
INFO: Cluster 'kx-f85b838d49' is now ready
INFO: ROSA with HCP cluster is ready, create a cluster admin account for accessing the cluster
WARN: The current version (1.2.47) is not up to date with latest rosa cli released version (1.2.50).
WARN: It is recommended that you update to the latest version.
INFO: Storing login command...
INFO: Check if it's able to login to OCP cluster...
Retried 1 times...
Retried 2 times...
Retried 3 times...
Retried 4 times...
Retried 5 times...
INFO: Check if apiserver is ready...
[INFO] Checking cluster operators' status...
[INFO] Attempt 1/10
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console
csi-snapshot-controller 4.15.44 True False False 7m8s
dns 4.15.44 False False True 7m7s DNS "default" is unavailable.
image-registry False True True 6m28s Available: The deployment does not have available replicas...
ingress False True True 6m42s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights
kube-apiserver 4.15.44 True False False 6m58s
kube-controller-manager 4.15.44 True False False 6m58s
kube-scheduler 4.15.44 True False False 6m58s
kube-storage-version-migrator
monitoring
network 4.15.44 True True False 6m43s Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning False True False 6m13s DaemonSet "tuned" has no available Pod(s)
openshift-apiserver 4.15.44 True False False 6m58s
openshift-controller-manager 4.15.44 True False False 6m58s
openshift-samples
operator-lifecycle-manager 4.15.44 True False False 7m1s
operator-lifecycle-manager-catalog 4.15.44 True False False 7m2s
operator-lifecycle-manager-packageserver 4.15.44 True False False 6m58s
service-ca
storage 4.15.44 False False False 6m51s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service
[INFO] Cluster operators are accessible.
[INFO] Waiting for cluster operators to be in 'Progressing=false' state...


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants