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

overrides add zincati-0.0.5-1.module_f30+6699+1eaa40c6.x86_64 #186

Merged
merged 1 commit into from
Sep 27, 2019

Conversation

dustymabe
Copy link
Member

Fast track the new zincati version for our next release of FCOS.

Fast track the new zincati version for our next release of FCOS.
@dustymabe
Copy link
Member Author

cc @lucab since you requested this I believe

@dustymabe
Copy link
Member Author

the test failure is going to fail with error: Packages not found: zincati until this PR is merged so we should ignore that.

Copy link
Contributor

@lucab lucab left a comment

Choose a reason for hiding this comment

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

LGTM
Double-check: this matches the one available in koji https://koji.fedoraproject.org/koji/buildinfo?buildID=1391362

@jlebon jlebon merged commit 0fa0fdb into coreos:testing-devel Sep 27, 2019
@dustymabe dustymabe deleted the newzincati branch March 26, 2020 13:11
dustymabe pushed a commit to jbtrystram/fedora-coreos-config that referenced this pull request Apr 19, 2024
As discussed in coreos#186 the provisioning pages now contain information on how to
connect to the newly spawned VMs.

Additionally, formatting is further standardized between some pages and the
Ignition/Afterburn information is also added to the authentication/default user
page.

The AWS example was split into two to make editing them easier going forward.

Fixes some references to outdated external tools (`gcloud compute ssh`, `govc`)
as well.

Fixes coreos#186
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.

None yet

3 participants