This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2158055 - [Azure][RHEL8][Network][cloud-init] Can not acquire IPv6 address
Summary: [Azure][RHEL8][Network][cloud-init] Can not acquire IPv6 address
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cloud-init
Version: 8.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Li Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-04 04:11 UTC by Li Tian
Modified: 2024-11-20 07:49 UTC (History)
22 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 15:44:27 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7277 0 None Migrated None 2023-09-22 15:44:06 UTC
Red Hat Issue Tracker RHELPLAN-143716 0 None None None 2023-01-04 04:15:26 UTC
Red Hat Knowledge Base (Solution) 7002539 0 None None None 2023-03-14 05:22:36 UTC

Description Li Tian 2023-01-04 04:11:20 UTC 
Description of problem:
VMs are not getting IPv6 addresses in client but only shown in Azure Portal. Probable cause is:

# cat /etc/cloud/cloud.cfg.d/91-azure_datasource.cfg 
datasource_list: [ Azure ]
datasource:
   Azure:
      apply_network_config: False

After removing the last 3 lines in this file and do 'cloud-init clean' then reboot. IPv6 address is acquired fine.

Version-Release number of selected component (if applicable):
4.18.0-348.el8.x86_64 with cloud-init 21.1-7.el8 (RHEL 8.5 from Azure Marketplace)

How reproducible:
100%

Steps to Reproduce:
1. Create a VM from any RHEL images in Azure Marketplace (by far, 8.5, 8.6, 8.7... all have this same issue)

Actual results:
No IPv6 address acquired in client.

Expected results:
IPv6 address acquired normally.

Additional info:
1. Ubuntu images in Marketplace don't have above configuration or this issue.
2. Adding the above configuration in any of our images can reproduce this issue.
3. Previously QE has been testing without above configuration until recently. And no additional issues were observed before this.
Comment 1 Yuxin Sun 2023-01-04 06:37:05 UTC 
Hi Anuj,

Could you please help to check why Microsoft has this configuration in the RHEL images? Thanks!

# cat /etc/cloud/cloud.cfg.d/91-azure_datasource.cfg 
...
datasource:
   Azure:
      apply_network_config: False
Comment 2 xiachen 2023-01-05 11:24:56 UTC 
Refer to cloud-init upstream document, https://cloudinit.readthedocs.io/en/latest/topics/datasources/azure.html#configuration
apply_network_config: Boolean set to True to use network configuration described by Azure’s IMDS endpoint instead of fallback network config of dhcp on eth0. 

so by the design of cloud-init, if using network configuration by Azure’s IMDS, it can configure IPv6, however the fallback network configure of dhcp does not support IPv6.

The Microsoft document (https://learn.microsoft.com/en-us/azure/virtual-machines/linux/redhat-create-upload-vhd) shows that,
Configure Azure datasource:
echo "Allow only Azure datasource, disable fetching network setting via IMDS"
cat > /etc/cloud/cloud.cfg.d/91-azure_datasource.cfg <<EOF
datasource_list: [ Azure ]
datasource:
    Azure:
        apply_network_config: False
EOF

so we would like to know why Microsoft has this configuration in the RHEL images to disable fetching network setting via IMDS.
Comment 3 anujmaurya 2023-01-05 11:53:21 UTC 
hi Yuxin and Xiachen,

Adding @anhvo from MS cloud-init team to answer the queries.

Adding Manik, Mayank, and Simrat from my team for visibility.

Thanks,
Anuj Maurya
Comment 4 anhvo 2023-01-24 15:04:18 UTC 
apply_network_config is set to False in RHEL is for backwards compatibility. Azure Linux Agent does not configure networking using IMDS. When we moved from Azure Linux Agent to cloud-init for provisioning, we decided to keep the same behavior to avoid surprises to the customer. The intention was to enable it in a major release of RHEL like RHEL 9. However, given that we already had RHEL 9 released without apply_network_config toggled on, it's probably best to maintain the same behavior until RHEL 10.
Comment 14 RHEL Program Management 2023-09-22 15:42:59 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 15 RHEL Program Management 2023-09-22 15:44:27 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.