Skip to content
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

bug(maas): register the correct DatasourceMAASLocal in init-local #5068

Merged
merged 1 commit into from
Mar 19, 2024

Conversation

blackboxsw
Copy link
Collaborator

@blackboxsw blackboxsw commented Mar 18, 2024

Proposed Commit Message

    bug(maas): register the correct DatasourceMAASLocal in init-local
    
    Incorrectly registering DataSourceMAAS for init-local DEP_FILESYSTEM
    inadvertently short-circuits the _get_data checks performed by
    DataSourceMAASLocal for presence of network config from initramfs.
    This results in a 2 minute timeout on physical system
    reboots because the network stage DataSourceMAAS expects all system
    networking is already configured and the IMDS to be accessible.
    
    Correct this registration to do the proper initramfs checks and avoid
    trying to perform GETs against the IMDS in init-local timeframe when
    we know network is not yet available.
    
    Fixes GH-5064
    LP: #2057763

Additional Context

Test Steps

Checklist

Merge type

  • Squash merge using "Proposed Commit Message"
  • Rebase and merge unique commits. Requires commit messages per-commit each referencing the pull request number (#<PR_NUM>)

@blackboxsw blackboxsw marked this pull request as draft March 18, 2024 23:38
@blackboxsw blackboxsw marked this pull request as ready for review March 18, 2024 23:40
Incorrectly registering DataSourceMAAS for init-local DEP_FILESYSTEM
inadvertently short-circuits the _get_data checks performed by
DataSourceMAASLocal for presence of network config from initramfs.
This results in a 2 minute timeout on physical system
reboots because the network stage DataSourceMAAS expects all system
networking is already configured and the IMDS to bebe accessible.

Correct this registration to do the proper initramfs checks and avoid
trying to perform GETs against the IMDS in init-local timeframe when
we know network is not yet available.

Fixes canonicalGH-5064
@blackboxsw blackboxsw force-pushed the maas-register-local-ds branch from 10ab82d to 96f26cb Compare March 19, 2024 00:08
Copy link
Member

@holmanb holmanb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@blackboxsw blackboxsw merged commit dbe6739 into canonical:main Mar 19, 2024
29 checks passed
@TheRealFalcon
Copy link
Member

I know this already merged, but reminder in the future to stick to our conventional commits template. It should be fix, not bug. If we start using aliases for different things, it'll make changelog generation that much harder (or wrong).

TheRealFalcon pushed a commit to TheRealFalcon/cloud-init that referenced this pull request Mar 19, 2024
…nonical#5068)

Incorrectly registering DataSourceMAAS for init-local DEP_FILESYSTEM
inadvertently short-circuits the _get_data checks performed by
DataSourceMAASLocal for presence of network config from initramfs.
This results in a 2 minute timeout on physical system
reboots because the network stage DataSourceMAAS expects all system
networking is already configured and the IMDS to be accessible.

Correct this registration to do the proper initramfs checks and avoid
trying to perform GETs against the IMDS in init-local timeframe when
we know network is not yet available.

Fixes canonicalGH-5064
LP: #2057763
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants