Skip to content

Conversation

@himani2411
Copy link
Contributor

Description of changes

  • Update develop branch with changes made in recent release branch

References

  • Link to impacted open issues.
  • Link to related PRs in other packages (i.e. cookbook, node).
  • Link to documentation useful to understand the changes.

Checklist

  • Make sure you are pointing to the right branch.
  • If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
  • Check all commits' messages are clear, describing what and why vs how.
  • Make sure to have added unit tests or integration tests to cover the new/modified code.
  • Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

hanwen-cluster and others added 12 commits April 2, 2025 18:30
`cp -p` fails with the following error on Ubuntu 24:
```
STDERR: cp: preserving permissions for ‘/local/home/ubuntu/.ssh/authorized_keys’: Operation not supported
```

Signed-off-by: Hanwen <[email protected]>
…ernet check

This commit saves time because the os won't retry on unsupported ipv6 and optional Internet connection

Signed-off-by: Hanwen <[email protected]>
* Adding Ubuntu24 for kitchen tests for storage

* Adding Rocky9, rhel9 and al2023

---------

Co-authored-by: Himani Anil Deshpande <[email protected]>
The conditional statement avoids cleaning if the `/etc/resolv.conf` is a symbolic link. It is a symbolic link when it is managed by other systems.

Cleaning the `/etc/resolv.conf` speed up instance launch because it wouldn't try to use name server from the AMI creation environment. The delay was shown in `/var/log/cloud-init.log`:
```
2025-03-19 16:00:07,721 - util.py[DEBUG]: Resolving URL: http://169.254.169.254 took 40.099 seconds
2025-03-19 16:00:07,721 - util.py[DEBUG]: Resolving URL: http://[fd00:ec2::254] took 0.000 seconds
2025-03-19 16:00:17,731 - util.py[DEBUG]: Resolving URL: http://instance-data.:8773 took 10.010 seconds
```

Example content of `/etc/resolv.conf`:
```
cat /etc/resolv.conf
# Generated by NetworkManager
search ec2.internal
nameserver 192.168.0.2
```

Signed-off-by: Hanwen <[email protected]>
The conditional statement avoids cleaning if the `/etc/resolv.conf` is a symbolic link. It is a symbolic link when it is managed by other systems.

Cleaning the `/etc/resolv.conf` speeds up instance launch because it wouldn't try to use name server from the AMI creation environment. The delay was shown in `/var/log/cloud-init.log`:
```
2025-03-19 16:00:07,721 - util.py[DEBUG]: Resolving URL: http://169.254.169.254 took 40.099 seconds
2025-03-19 16:00:07,721 - util.py[DEBUG]: Resolving URL: http://[fd00:ec2::254] took 0.000 seconds
2025-03-19 16:00:17,731 - util.py[DEBUG]: Resolving URL: http://instance-data.:8773 took 10.010 seconds
```

Example content of `/etc/resolv.conf`:
```
cat /etc/resolv.conf
# Generated by NetworkManager
search ec2.internal
nameserver 192.168.0.2
```

Signed-off-by: Hanwen <[email protected]>
1. Only cleanup resolv conf during official AMI build. In the future, we will evaluate to apply this improvement to all AMI builds.
2. Also clean up `/run/systemd/resolve/resolv.conf `. This file exists on Ubuntu

Signed-off-by: Hanwen <[email protected]>
@himani2411 himani2411 added the 3.x label Apr 2, 2025
@himani2411 himani2411 requested review from a team as code owners April 2, 2025 22:33
@himani2411
Copy link
Contributor Author

@himani2411 himani2411 merged commit cc40fa4 into aws:develop Apr 3, 2025
57 of 63 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants