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:
We have some interactive operations in atomic command, it will be convenient for users if we can support for automatically answer yes for all questions like '--assumeyes' option in dnf.
Version-Release number of selected component (if applicable):
[cloud-user@atomic-host-001 atomic]$ cat /etc/redhat-release
Red Hat Enterprise Linux Atomic Host release 7.2
[cloud-user@atomic-host-001 atomic]$ atomic host status
State: idle
Deployments:
● rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard
Version: 7.2.7 (2016-08-25 18:18:13)
Commit: 2c31fbe0af5f907dc541bf23cc8a1ba18bcf9f1d0a74fdcdb17d25043f296d1c
OSName: rhel-atomic-host
[cloud-user@atomic-host-001 atomic]$ rpm -q atomic
atomic-1.10.5-7.el7.x86_64
How reproducible:
always.
Steps to Reproduce:
1. docker pull some images to local
2. atomic storage export --dir /tmp/export
3. systemctl stop docker
4. atomic storage reset
5. systemctl start docker
6. atomic storage import --dir /tmp/export
Actual results:
[cloud-user@atomic-host-001 atomic]$ sudo ./atomic storage import --dir /tmp/export
Importing image: 11a5107645d4
Importing image: 2b8fd9751c4c
Importing container: 911a6948348b
Importing volumes
atomic import completed successfully
Would you like to cleanup (rm -rf /tmp/export) the temporary directory [y/N]
Expected results:
support for automatically answer yes for all questions
Additional info:
PR: https://github.com/projectatomic/atomic/pull/573
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://rhn.redhat.com/errata/RHBA-2016-2857.html
Description of problem: We have some interactive operations in atomic command, it will be convenient for users if we can support for automatically answer yes for all questions like '--assumeyes' option in dnf. Version-Release number of selected component (if applicable): [cloud-user@atomic-host-001 atomic]$ cat /etc/redhat-release Red Hat Enterprise Linux Atomic Host release 7.2 [cloud-user@atomic-host-001 atomic]$ atomic host status State: idle Deployments: ● rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard Version: 7.2.7 (2016-08-25 18:18:13) Commit: 2c31fbe0af5f907dc541bf23cc8a1ba18bcf9f1d0a74fdcdb17d25043f296d1c OSName: rhel-atomic-host [cloud-user@atomic-host-001 atomic]$ rpm -q atomic atomic-1.10.5-7.el7.x86_64 How reproducible: always. Steps to Reproduce: 1. docker pull some images to local 2. atomic storage export --dir /tmp/export 3. systemctl stop docker 4. atomic storage reset 5. systemctl start docker 6. atomic storage import --dir /tmp/export Actual results: [cloud-user@atomic-host-001 atomic]$ sudo ./atomic storage import --dir /tmp/export Importing image: 11a5107645d4 Importing image: 2b8fd9751c4c Importing container: 911a6948348b Importing volumes atomic import completed successfully Would you like to cleanup (rm -rf /tmp/export) the temporary directory [y/N] Expected results: support for automatically answer yes for all questions Additional info: PR: https://github.com/projectatomic/atomic/pull/573