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

coreos ignition creation #20

Closed
jichenjc opened this issue Apr 15, 2019 · 7 comments
Closed

coreos ignition creation #20

jichenjc opened this issue Apr 15, 2019 · 7 comments
Assignees
Labels
future Future Works lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@jichenjc
Copy link
Contributor

/kind feature
need provide a set of configuration scripts for the new deployed guest to run this
in order to boot cluster and join cluster for master/node

coreos ignition will be primary focus for this PR

this might be long term option and need check ibm cloud support coreos or not

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

@jichenjc
Copy link
Contributor Author

confirmed : through slcli virtual create-options we can get following info

os (COREOS) : COREOS_CURRENT_64 :
: : COREOS_LATEST :
: : COREOS_LATEST_64

@jichenjc
Copy link
Contributor Author

/assign

@jichenjc
Copy link
Contributor Author

2019/05/23 09:29:26 [DEBUG] Status Code: 500
2019/05/23 09:29:26 [DEBUG] Response: {"error":"CoreOS Stable is not available as of 03/30/2018 (Item #(6183).","code":"SoftLayer_Exception_Public"}
SoftLayer_Exception_Public: CoreOS Stable is not available as of 03/30/2018 (Item #(6183). (HTTP 500)

we have to hold this for a while....

@jichenjc jichenjc added the future Future Works label May 23, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 21, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 20, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future Future Works lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants