Re: [PATCH xenomai-images] kas/ci: Fix bitbake variable referencing themselves

On 01.06.26 12:35, Florian Bezdeka wrote:
> When trying to run a local kas build using the kas/opt/ci.yaml option
> file the following bitbake error occurred as the following two bitbake
> variables were referencing themselves:
> 
> Variables:
>   - AWS_ACCESS_KEY_ID
>   - AWS_SECRET_ACCESS_KEY
> 
> Error:
> bb.data_smart.ExpansionError: Failure expanding variable
> AWS_ACCESS_KEY_ID, expression was ${AWS_ACCESS_KEY_ID} which triggered
> exception
> Exception: variable AWS_ACCESS_KEY_ID references itself!
> The variable dependency chain for the failure is: AWS_ACCESS_KEY_ID
> 
> The problem only exists for local builds as the gitlab project
> configuration defines such variables.
> 
> We can avoid the bitbake error by stopping forwaring the variables to
> bitbake. We don't need those variables inside the build environment.
> The only user is located in the deploy_to_aws.sh script, which is
> executed on gitlab CI level.
> 
> Signed-off-by: Florian Bezdeka <[email protected]>
> ---
>  kas/opt/ci.yaml | 4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/kas/opt/ci.yaml b/kas/opt/ci.yaml
> index e1466a0..01d5c07 100644
> --- a/kas/opt/ci.yaml
> +++ b/kas/opt/ci.yaml
> @@ -23,7 +23,3 @@ local_conf_header:
>      IMAGE_INSTALL:remove = "sshd-regen-keys"
>      IMAGE_INSTALL:remove = "expand-on-first-boot"
>      IMAGE_FSTYPES = "${@ 'ext4.gz' if d.getVar('MACHINE', True).startswith('qemu') else 'tar.gz' }"
> -
> -env:
> -  AWS_ACCESS_KEY_ID: ${AWS_ACCESS_KEY_ID}
> -  AWS_SECRET_ACCESS_KEY: ${AWS_SECRET_ACCESS_KEY}

Check the introducing commit 0e027423275a why those two are probably
needed for bitbake as well.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center