-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PA-5570] Added platform file for amazon 2023 aarch64 & amd64 for 7.x #2417
[PA-5570] Added platform file for amazon 2023 aarch64 & amd64 for 7.x #2417
Conversation
Vanagon generic builder is able to build puppet-agent but somehow it is failing to upload it to artifactory. Below is the link to generic builder execution: |
I believe that your build failed because of I would add your changes to the When testing changes to puppet-agent like this, I would use the ad hoc pipeline instead of the Vanagon generic builder, as the ad hoc pipeline is the most similar to our normal CI pipeline and can best replicate what it will look like once changes are merged. I ran your changes in the ad hoc pipeline and ran into another issue: Beaker does not support these versions of Amazon Linux. Jake added support to the Beaker 5 stream, but we are still using Beaker 4: puppet-agent/acceptance/Gemfile Line 15 in cf78697
We have an epic to migrate to Beaker 5, but there's a lot of work to be done before we can do that. I think for now, I would backport Jake's changes to the 4.x branch of Beaker and work with Vox Pupuli on creating a new Beaker 4 release. |
Artifacts for Puppet-Agent 7.x are available in below links: |
@span786 I've released both new Beaker (4.41.0) and packaging (0.112.0) versions today that should support this work. However when I run your PR through the ad hoc pipeline with updated Beaker and packaging, I see a few issues.
This looks like what we've seen in the past with CPR-644, which was solved in Vanagon in the project.spec template. I think the same fix would work here, so you should update Vanagon for Amazon Linux 2023. With aarch64, we see this issue:
I believe this is due to beaker-hostgenerator using "arm64" when everything else in the ecosystem uses "aarch64": https://github.com/voxpupuli/beaker-hostgenerator/blob/64f315292da95440a025223a47b57d767cdd7f0f/lib/beaker-hostgenerator/data.rb#L1114 I would try changing this line and doing a new beaker-hostgenerator release. |
Hi @mhashizume, I have raised following PR, please review them and let me know if any more changes are required. puppetlabs/vanagon#828 I tried running 'ad-hoc' pipeline for Puppet-Agent using the Vanagon changes as per PR-828, it still failed with the same error. Here is the link to pipeline. |
97ecc79
to
cafe14e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After new Vanagon and beaker-hostgenerator releases that include your changes, I ran this through the ad hoc pipeline and was able to get a build that we're able to install.
There are a few test failures, but they're minor and we can tackle those as part of enabling Amazon 2023 in CI (PA-5573). I've ticketed out those test failures as FACT-3448 and PUP-11986.
I see that this PR is still marked as a draft and needs to be rebased on 7.x. Please feel free to merge this after the PR has been taken out of draft and is up-to-date.
cafe14e
to
7d864f6
Compare
Added platform file for amazon 2023 aarch64 & amd64 for 7.x branch