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.
Bug 1463093 - [WALA] VM status cannot become running if Provisioning.Enabled=n and Provisioning.UseCloudInit=n
Summary: [WALA] VM status cannot become running if Provisioning.Enabled=n and Provisio...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: WALinuxAgent
Version: 7.4
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Vitaly Kuznetsov
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1639496 1639498
TreeView+ depends on / blocked
 
Reported: 2017-06-20 06:28 UTC by Yuxin Sun
Modified: 2020-01-09 06:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-21 08:38:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github Azure WALinuxAgent issues 756 0 None None None 2017-06-20 06:31:06 UTC
Github Azure WALinuxAgent issues 850 0 None None None 2017-09-28 03:31:30 UTC

Description Yuxin Sun 2017-06-20 06:28:56 UTC 
Description of problem:
When Provisioning.Enabled=n and Provisioning.UseCloudInit=n, the VM status cannot become running. It will keep "starting" for a long time and then failed.

Version-Release number of selected component (if applicable):
WALinuxAgent-2.2.12-1

RHEL Version:
RHEL-7.4/6.9

How reproducible:
100%

Steps to Reproduce:
1. Prepare a VM in Azure. Set "Provisioning.Enabled=n" and "Provisioning.UseCloudInit=n" in /etc/waagent.conf
2. Deprovision this VM. Shutdown and capture as a generalized image. Then create a new VM base on it.
3. Wait for over 10 minutes. Check VM status from https://portal.azure.com

Actual results:
The VM status is always "Starting". And after a long time (about 1 hour) it becomes "Failed".

Expected results:
The VM status is "Running".

Additional info:
Root cause is when "Provisioning.Enabled=n" and "Provisioning.UseCloudInit=n", the wala skip the provisioning phase but not send "ready" report  to Azure.(pa/provision/default.py Line#57-59)
Comment 2 Yuxin Sun 2017-09-28 07:27:26 UTC 
Fixed upstream:
https://github.com/Azure/WALinuxAgent/pull/851

Verified in WALA 2.2.18 upstream pre-release package. Will verify again in WALA-2.2.18-1 rpm package when it releases.
Comment 4 Yuxin Sun 2019-01-21 08:38:02 UTC 
Verified in WALA-2.2.32-1. Pass.
Note You need to log in before you can comment on or make changes to this bug.