We want to start providing Mac instances for testing for the Containers team as agreed on DevConf.cz 2024 with @mohanboddu and @davdunc.
For this we need to be able to allocate dedicated hosts, what seems to be a requirement for provisioning these instances.
We need at least this permission for aws-fedora-ci, including the automation account:
You are not authorized to perform this operation. User: arn:aws:sts::125523088429:assumed-role/aws-fedora-ci/mvadkert is not authorized to perform: ec2:AllocateHosts on resource: arn:aws:ec2:us-east-1:125523088429:dedicated-host/* because no identity-based policy allows the ec2:AllocateHosts action
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
Metadata Update from @kevin: - Issue assigned to kevin
I have added AllocateHosts. Please test.
thank you, permissions are now ok, but seems we are not allowed to allocate macs on the Fedora AWS account :(
Whatever I try, I always get:
https://matrix.to/#/!eQpVZJMoHpMaLidQfi:matrix.org/$TmjUpgWe6hRfg73u4hYAtvVTueJL82HNB4juJBLnu9s?via=fedora.im&via=matrix.org&via=tchncs.de
Browsing through internets some folks say that:
I manged to resolve this issue by contacting AWS Support where they identified due to confidential reason my AWS account was not whitelisted for this feature.
I mailed @davdunc to see if he can enable whatever we need here.
Checking to see if this is something I can clear for the account.
@davdunc thank you!
@mohanboddu @lsm5 FYI ^
cc @baude
I put in an internal ticket requesting access in us-east-2. That's where they requested that we do the testing.
@davdunc thank you, so I guess I can try it out
@davdunc tried it, I guess the ticket is not yet resolved?
<img alt="mac-dedicated-host-allocation-failed.jpg" src="/fedora-infrastructure/issue/raw/files/e5aaca422e804127df74776354845a36ed74b1589a695d1b9241ff853be3ffd1-mac-dedicated-host-allocation-failed.jpg" />
@davdunc kindly pinging
Any news here?
any update on this?
I tried again on us-east-2, still getting the same error as on the start:
The requested configuration is currently not supported. Please check the documentation for supported configurations.
When trying to allocate a dedicated host.
@kevin can you talk to @davdunc on some meeting on this please? This is blocking podman and folks to onboard their testing against mac to Testing Farm (not to mention we are not even able to start easily on the integration without it)
@davdunc kindly pinging here, I would really love if we could finally get unblocked here.
Log in to comment on this ticket.