Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
A new build is needed for other products to take advantage of the expected features.

Version-Release number of selected component (if applicable):
1.16.x

How reproducible:
Always

Steps to Reproduce:
1. Attempt to use a system container using the file copy feature
2. System container installs without error
3. System container doesn't work

Actual results:

The system container acts in a way not expected (failure, misconfigured, etc..)


Expected results:

The system container works as expected.


Additional info:

I believe 1.17.1 is the latest release

Should be updated in 7.3.6/

If we could get a build up to 2760e30296884e9160ff0b8e58c2e5d47791f01d that would be even better. The ansible installer expects to be able to use no_proxy if possible.

[root@atomic-host-test-986 cloud-user]# rpm -qf /etc/atomic.conf
atomic-1.17.2-2.git2760e30.el7.x86_64

[root@atomic-host-test-986 cloud-user]# grep proxy /etc/atomic.conf 
# To always use a proxy with atomic, you can uncomment and fill out
#http_proxy=
#https_proxy=
#no_proxy=

NOTE: the above proxy variables should be KEY: VALUE, it uses YAML format, the following is PR to fix this:

https://github.com/projectatomic/atomic/pull/1004

Tests to check the file for validity: https://github.com/projectatomic/atomic/pull/1009

The PR 1004 and PR 1009 haven't been included by atomic-1.17.2-5.1.git2760e30.el7.x86_64.

PRs 1004 and 1009 do not impact the functionality of what is being asked for here.  I dont see what a FailedQA was assigned.

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, 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-2017:1323