Skip to content

Issues: openshift/origin

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
13 Open 666 Closed
13 Open 666 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

[OKD 3.11] Testing GitLab Build Trigger - payload includes 3 commits and triggers build based on wrong commit area/usability component/build lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/developer-experience
#23799 opened Sep 16, 2019 by miikamoi
7
[RFE] oc CLI should preserve name of contexts area/usability kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P2 sig/master
#18645 opened Feb 16, 2018 by jorgemoralespou
13
oc >= 3.7.0-rc.0 cannot talk to OpenShift servers < 3.6.0-rc.0 area/usability component/cli kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P1
#17648 opened Dec 7, 2017 by elyscape
@mfojtik
5
The oc set deployment-hook should default to Abort for failureStrategy. area/usability component/cli kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P2 sig/user-interface
#17465 opened Nov 27, 2017 by GrahamDumpleton
3
Add oc set deployment-strategy command. area/usability component/cli lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P3
#17462 opened Nov 27, 2017 by GrahamDumpleton
@soltysh @juanvallejo
4
oc status is complaining about missing readiness checks in build pods area/usability component/build component/cli lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#17213 opened Nov 7, 2017 by 0xmichalis
@juanvallejo
5
oc set triggers shouldn't fail with a single container area/usability component/cli lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P3 sig/master
#15185 opened Jul 13, 2017 by 0xmichalis
@mfojtik
4
Switch the deployment strategy based on external condition (PV type) area/usability component/apps lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P3
#15168 opened Jul 12, 2017 by marekjelen
20
Rsync via tar creates nested directories on Windows because slashes are not inverted to Windows style area/usability component/cli kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P2
#14065 opened May 4, 2017 by bdshadow
@csrwng
3
Add ability to label a project area/usability component/restapi kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2
#10315 opened Aug 9, 2016 by jorgemoralespou
@mfojtik
9
registry "disabling cross-mount" message cited as an error area/usability component/imageregistry lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P3
#9649 opened Jun 30, 2016 by gabemontero
@miminar
12
Project deletion area/usability component/cli kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2 sig/master
#4141 opened Aug 13, 2015 by 0xmichalis
@fabianofranz
18
Builds that reference invalid imagestreamtags should be noted. area/usability component/cli component/web kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P3
#2957 opened Jun 8, 2015 by bparees
@bparees
8
ProTip! Add no:assignee to see everything that’s not assigned.