![]() 07:55:59,843 - helpers.py: Running config-users-groups using lock ()Īzure.py: Command failed: cmd= stderr='' stdout='' exit_code=1ħ746 08:15:46,703 - azure.py: Command failed: cmd= stderr='' stdout='' exit_code=1ħ747 08:15:46,704 - handlers.py: finish: azure-ds/obtain-dhcp-lease: FAIL: obtain dhcp leaseħ748 08:15:46,704 - handlers.py: finish: azure-ds/_setup_ephemeral_networking: FAIL: _setup_ephemeral_networkingħ749 08:15:46,704 - azure.py: Could not retrieve pps configuration from IMDS: 'extended'ħ750 08:15:46,704 - azure.py: Could not retrieve pps configuration from IMDS: 'extended'ħ751 08:15:46,704 - azure.py: Could not retrieve pps configuration from IMDS: 'extended'ħ752 08:15:46,719 - azure.py: PPS type: Noneħ753 08:15:46,720 - handlers.py: start: azure-ds/validate_imds_network_metadata: validate_imds_network_metadataħ754 08:15:46,720 - handlers.$ bugwrangler coverage -product 'Red Hat Satellite 6' -f 'qe_test_coverage+' -f'sat-6.4.0+' -report 07:55:59,841 - handlers.py: start: init-network/config-users-groups: running config-users-groups with frequency once-per-instance 07:19:22,647 - handlers.py: finish: init-network/config-users-groups: SUCCESS: config-users-groups ran successfully 08:15:49,706 - handlers.py: finish: init-network/config-users-groups: SUCCESS: config-users-groups previously ran 08:15:49,706 - helpers.py: config-users-groups already ran (freq=once-per-instance) ![]() ![]() 08:15:49,706 - handlers.py: start: init-network/config-users-groups: running config-users-groups with frequency once-per-instance 07:55:59,907 - handlers.py: finish: init-network/config-users-groups: SUCCESS: config-users-groups ran successfully 07:19:21,551 - helpers.py: Running config-users-groups using lock () 07:19:21,547 - handlers.py: start: init-network/config-users-groups: running config-users-groups with frequency once-per-instance # grep config-users /var/log/cloud-init.log After reboot(with /bin/false for dhclient), instance can get IP address successfully. I tested the scratch rebase cloud-init-23.1.1 build, the issue is fixed.īut there are some error logs per the test steps of demonstration purposes in Description, could you please help to take a look if this is expected? 03:13:24,039 - handlers.py: finish: init-network/config-users-groups: SUCCESS: config-users-groups ran successfully 03:13:23,944 - helpers.py: Running config-users-groups using lock () 03:13:23,943 - handlers.py: start: init-network/config-users-groups: running config-users-groups with frequency once-per-instance 03:02:25,119 - handlers.py: finish: init-network/config-users-groups: SUCCESS: config-users-groups ran successfully 03:02:23,248 - helpers.py: Running config-users-groups using lock () 03:02:23,247 - handlers.py: start: init-network/config-users-groups: running config-users-groups with frequency once-per-instance grep config-users /var/log/cloud-init.log reboot or clean reboot for demonstration purposesĢ.1 mv /usr/sbin/dhclient /usr/sbin/dhclient.xĤ. create RHEL VM on Azure (config serial console and password login, as can not get IP after demonstration wrong config and reboot)Ģ. We will rebase to cloud-init-23.1 in the next rhel versions(8.9/9.3) which already included this patch.Īnd the rhel-8.8/9.2(cloud-init-22.1) are in the exception+ phase now(Mainly fix urgent/important issues), could we fix this BZ in the rhel-8.8/9.2 first batch update? And on which Z streams would you prefer to backport the patch?ġ. Thanks for raising the issue and the detail test steps, I can reproduce it per comment 0. The upstream patch that should address this failure: 17:30:49,491 - handlers.py: finish: init-network/config-users-groups: SUCCESS: config-users-groups ran successfully 17:30:49,487 - helpers.py: Running config-users-groups using lock () 17:30:49,484 - handlers.py: start: init-network/config-users-groups: running config-users-groups with frequency once-per-instance 15:14:03,279 - handlers.py: finish: init-network/config-users-groups: SUCCESS: config-users-groups previously ran 15:14:03,279 - helpers.py: config-users-groups already ran (freq=once-per-instance) 15:14:03,278 - handlers.py: start: init-network/config-users-groups: running config-users-groups with frequency once-per-instance 16:46:09,851 - handlers.py: finish: init-network/config-users-groups: SUCCESS: config-users-groups ran successfully 16:46:08,017 - helpers.py: Running config-users-groups using lock () 16:46:08,014 - handlers.py: start: init-network/config-users-groups: running config-users-groups with frequency once-per-instance Version-Release number of selected component (if applicable): This will cause cloud-init to reconfigure the VM thinking it is a new instance. Some error cases will cause the instance ID to fall back to a default value of "iid-datasource". Cloud-init may re-configure VM after falling back to non-Azure datasource on Azure.
0 Comments
Leave a Reply. |