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:
cloudinit marker file("/var/lib/cloud/sem/config_scripts_per_once.once") not remove during deprovision process
This file is a marker for cloudinit module "scripts-per-once".So if not remove this file during deprovision process,while deploy a new VM use this,during the new VM's provision process, "scripts-per-once" module check the marker file exists,so the module will skip this module's follow code,and run the next module.
So this will cause some issues in some scenarious.
Version-Release number of selected component (if applicable):
WALinuxAgent-2.2.11-upstream
RHEL Version:
RHEL-7.4/RHEL-6.9
How reproducible:
100%
Steps to Reproduce:
1. Prepare a RHEL7.4 VM in Azure. Install cloud-init，WALA and enable them while booting
(do not modify cloudinit configuration file)
2. Check "/var/lib/cloud/sem" folder
3. Do WALA deprovision process
4. Check "/var/lib/cloud/sem" folder
Actual results:
For step 2:
there is one file exits in folder,named "config_scripts_per_once.once"
For step 4:
the file still exists
Expected results:
Should clean up "/var/lib/cloud/sem/" folder
Additional info:
Now,WALA only clean up below folders,
pa/deprovision/default.py(line 102-106)
Description of problem: cloudinit marker file("/var/lib/cloud/sem/config_scripts_per_once.once") not remove during deprovision process This file is a marker for cloudinit module "scripts-per-once".So if not remove this file during deprovision process,while deploy a new VM use this,during the new VM's provision process, "scripts-per-once" module check the marker file exists,so the module will skip this module's follow code,and run the next module. So this will cause some issues in some scenarious. Version-Release number of selected component (if applicable): WALinuxAgent-2.2.11-upstream RHEL Version: RHEL-7.4/RHEL-6.9 How reproducible: 100% Steps to Reproduce: 1. Prepare a RHEL7.4 VM in Azure. Install cloud-init，WALA and enable them while booting (do not modify cloudinit configuration file) 2. Check "/var/lib/cloud/sem" folder 3. Do WALA deprovision process 4. Check "/var/lib/cloud/sem" folder Actual results: For step 2: there is one file exits in folder,named "config_scripts_per_once.once" For step 4: the file still exists Expected results: Should clean up "/var/lib/cloud/sem/" folder Additional info: Now,WALA only clean up below folders, pa/deprovision/default.py(line 102-106)