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:
use vim to open a config file such as: vi /etc/virt-who.d/esx.conf, if don't quit vim, there is a ".esx.conf.swp" file created, virt-who will check the .swp file and feedback error message.
the expected result is: virt-who shouldn't check the .esx.conf.swp file.
Version-Release number of selected component (if applicable):
virt-who-0.16-7.el6.noarch
subscription-manager-1.16.8-8.el6.x86_64
python-rhsm-1.16.6-1.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. use vim edit a config file:
# vim /etc/virt-who.d/esx.conf
[test-esx]
type=esx
server=10.73.2.95
username=Administrator
#password=Welcome1!
owner=ACME_Corporation
env=Library
2. save the file, but don't quit vim, make sure esx.conf.swp exist
3. restart virt-who and check rhsm.log
2016-04-01 11:33:12,662 [virtwho.init INFO] MainProcess(8794):MainThread @virtwho.py:parseOptions:637 - Using reporter_id='hp-z220-10.qe.lab.eng.nay.redhat.com'
================== ERROR Message ================
2016-04-01 11:33:12,665 [virtwho.init ERROR] MainProcess(8794):MainThread @config.py:__init__:341 - Configuration file .esx.conf.swp contains no section headers
=================================================
2016-04-01 11:33:12,665 [virtwho.init DEBUG] MainProcess(8794):MainThread @virtwho.py:__init__:125 - Using config named 'test-esx'
2016-04-01 11:33:12,665 [virtwho.init INFO] MainProcess(8794):MainThread @virtwho.py:main:729 - Using configuration "test-esx" ("esx" mode)
2016-04-01 11:33:12,683 [virtwho.main DEBUG] MainProcess(8796):MainThread @virtwho.py:run:231 - Starting infinite loop with 60 seconds interval
2016-04-01 11:33:12,811 [virtwho.test-esx DEBUG] Esx-1(8804):MainThread @virt.py:run:358 - Virt backend 'test-esx' started
2016-04-01 11:33:12,812 [virtwho.test-esx DEBUG] Esx-1(8804):MainThread @esx.py:_prepare:55 - Log into ESX
......
Actual results:
virt-who will read .esx.conf.swp file
Expected results:
virt-who shouldn't check .esx.conf.swp file
Additional info:
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-2017-0675.html
Description of problem: use vim to open a config file such as: vi /etc/virt-who.d/esx.conf, if don't quit vim, there is a ".esx.conf.swp" file created, virt-who will check the .swp file and feedback error message. the expected result is: virt-who shouldn't check the .esx.conf.swp file. Version-Release number of selected component (if applicable): virt-who-0.16-7.el6.noarch subscription-manager-1.16.8-8.el6.x86_64 python-rhsm-1.16.6-1.el6.x86_64 How reproducible: always Steps to Reproduce: 1. use vim edit a config file: # vim /etc/virt-who.d/esx.conf [test-esx] type=esx server=10.73.2.95 username=Administrator #password=Welcome1! owner=ACME_Corporation env=Library 2. save the file, but don't quit vim, make sure esx.conf.swp exist 3. restart virt-who and check rhsm.log 2016-04-01 11:33:12,662 [virtwho.init INFO] MainProcess(8794):MainThread @virtwho.py:parseOptions:637 - Using reporter_id='hp-z220-10.qe.lab.eng.nay.redhat.com' ================== ERROR Message ================ 2016-04-01 11:33:12,665 [virtwho.init ERROR] MainProcess(8794):MainThread @config.py:__init__:341 - Configuration file .esx.conf.swp contains no section headers ================================================= 2016-04-01 11:33:12,665 [virtwho.init DEBUG] MainProcess(8794):MainThread @virtwho.py:__init__:125 - Using config named 'test-esx' 2016-04-01 11:33:12,665 [virtwho.init INFO] MainProcess(8794):MainThread @virtwho.py:main:729 - Using configuration "test-esx" ("esx" mode) 2016-04-01 11:33:12,683 [virtwho.main DEBUG] MainProcess(8796):MainThread @virtwho.py:run:231 - Starting infinite loop with 60 seconds interval 2016-04-01 11:33:12,811 [virtwho.test-esx DEBUG] Esx-1(8804):MainThread @virt.py:run:358 - Virt backend 'test-esx' started 2016-04-01 11:33:12,812 [virtwho.test-esx DEBUG] Esx-1(8804):MainThread @esx.py:_prepare:55 - Log into ESX ...... Actual results: virt-who will read .esx.conf.swp file Expected results: virt-who shouldn't check .esx.conf.swp file Additional info: