Issue #552: [spin-kickstarts] resolv.conf on Cloud images are not empty, causing cloud-init automatic network configuration to fail | rhbz#2014526 - blocker-review

fedora-qa / blocker-review

#552 [spin-kickstarts] resolv.conf on Cloud images are not empty, causing cloud-init automatic network configuration to fail | rhbz#2014526

Closed 2 years ago by blockerbot. Opened 2 years ago by blockerbot.

Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2014526
Information from BlockerBugs App:

Current vote summary

Accepted FinalBlocker (+3, 0, -0)
- +1 by bcotton, mattdm, geraldosimiao
FinalFreezeException (+2, 0, -0)
- +1 by adamwill, bcotton

The votes have been last counted at 2021-10-17 20:13 UTC and the last processed comment was #comment-758046

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)

adamwill commented 2 years ago

I'm at least:
FinalFE +1
which is good because neal merged it already...

bcotton commented 2 years ago

FinalFE +1

It's a bit academic since it's already been committed, but I'll vote

FinalBlocker +1

Based on a loose reading of either of these basic release criteria:

Release-blocking cloud images must allow login with the user authentication configuration requested during instance creation.
The installer must run when launched normally from the release-blocking images.