Azure Appliance Deployment fails.

[willryals-typefi]

1. When attempting to deploy the ManageIQ appliance in Azure following the steps listed in the documentation: https://www.manageiq.org/docs/reference/latest/installing_on_microsoft_azure/index.html#enabling-manageiq-user-interface-access
   The vm creation times out, in looking at the serial console log, it looks like the image has no default routes post deployment, causing Azure to fail the deployment.

2. Similar issues have been reported under the following issues: MIQ Deployment failure for Azure image for oparin 1.1  #22384 and oparin-1.1 Azure Install contains no routes #22315 Of note though, I am using the latest version available on the ManageIQ website (Petrosian-1 hash: 68a65d8d7e43a48bb77483cc2d7378ea)

3. I would expect the install to complete without issue and be able to communicate over the network post deployment instead of getting the following line, endlessly repeating, on the serial console:
   2024-04-03T22:28:45.106570Z ERROR Daemon Daemon /proc/net/route contains no routes

In reviewing on my end, it looks like either the Azure WALinuxAgent may not be included in the image, or cloud-init isn't properly configured for Azure deployment. Microsoft has a pretty decent guide here on what steps need to be taken when creating a image vhd for Azure:
https://learn.microsoft.com/en-us/azure/virtual-machines/linux/create-upload-centos#centos-70

4. This error can be reproduced by following the deployment guide listed above

5. Describe your environment, including

   • Version Petrosian-1
   • Environment
     • Azure Appliance

6. Ask @miq-bot to apply additional labels, reviewers, or assignees.
   (As described in https://github.com/ManageIQ/miq_bot#requested-tasks)
   e.g. @miq-bot add-label label_name
@miq-bot add-reviewer @name

[Fryguy]

@agrare @bdunne Can you take a look at this one?

[willryals-typefi]

Hi there, I just wanted to check and see if there are any updates to this one? It's currently holding up our deployment.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

[willryals-typefi]

It looks like this has been resolved via ManageIQ/manageiq-appliance-build#573. Will this be included in the next release, or has it already been applied to the Azure image?

[agrare]

Hey @willryals-typefi ! That PR is still open as there are a few other places which depend on eth0 that I'm working on refactoring. It isn't in any built images yet but hopefully it will get merged shortly.

[agrare]

@willryals-typefi all related PRs have been merged and should land in the next release. If you want to test the fix out you can try with an azure devel image (https://releases.manageiq.org/manageiq-azure-devel.zip) once a new build is done which includes this PR. https://releases.manageiq.org/index.html shows manageiq-azure-devel.zip 2024-07-07T02:25:31.720Z so the next devel build should include this.