Bug 1936663 - [assisted operator] AI Operator assisted-service stays in loop due to upstream entries in configmap
Summary: [assisted operator] AI Operator assisted-service stays in loop due to upstrea...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: assisted-installer
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.8.0
Assignee: David Zager
QA Contact: Yuri Obshansky
URL:
Whiteboard: AI-Team-Platform
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-08 21:15 UTC by bjacot
Modified: 2024-01-08 00:10 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-03 06:09:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:2896 0 None None None 2021-08-03 06:10:17 UTC

Description bjacot 2021-03-08 21:15:52 UTC
Description of problem:
AI Operator assisted-service stays in a constant loop Ready, Error and Crash loop due to upstream entries in configmap.  In the assisted-service config map its still pointing to upstream entries.  There are many entries still pointing to quay.io.  This makes a ipv6 disconnected deployment to fail unless configmaps are manually updated via the admin.

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

How reproducible:
100%

Steps to Reproduce:
1. Deploy hub ocp 4.7 ipv6, disconnected with local registry
2. mirror over assisted service image.. this issue is specific to --> quay.io/ocpmetal/assisted-service:latest and push to local registry
3. Complete steps to build operator bundle and try to deploy operator.

List of images that were mirrored over for this operator:
quay.io/ocpmetal/assisted-installer-agent:latest
quay.io/ocpmetal/assisted-installer-controller:latest
quay.io/ocpmetal/assisted-installer:latest
quay.io/ocpmetal/assisted-service:latest
quay.io/ocpmetal/assisted-service:latest
quay.io/openshift/origin-cli:latest
quay.io/ocpmetal/ocp-metal-ui:latest
quay.io/ocpmetal/postgresql-12-centos7
quay.io/openshift/origin-cli:latest
quay.io/ocpmetal/s3server

Actual results:
assisted-service in crashloop

Expected results:
to start without any issues

Additional info:

workaround:
create a local HTTP server and mirror over two images.
wget https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.6/4.6.8/rhcos-4.6.8-x86_64-live.x86_64.iso
wget https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/pre-release/4.7.0-rc.2/rhcos-4.7.0-rc.2-x86_64-live.x86_64.iso

before creating and pushing index bundle image need to modify the assisted-service-config_v1_configmap.yaml to point to local registry.  assisted-service container should see images.

Comment 1 David Zager 2021-04-13 19:26:50 UTC
https://github.com/openshift/assisted-service/pull/1475 should address this issue. Moved to an AgentServiceConfig controller that manages the assisted-service deployment w/o the use of configmaps.

Comment 2 bjacot 2021-04-23 13:38:55 UTC
also verified can override images in the operator subscription.  NOt an issue anymore.

Comment 5 errata-xmlrpc 2021-08-03 06:09:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.8.3 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:2896

Comment 6 Martinez 2023-11-24 09:29:26 UTC Comment hidden (spam)

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