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

UPSTREAM: <carry>: hack in working autoscale reference for oc autoscale #18376

Merged
merged 2 commits into from
Feb 2, 2018

Conversation

deads2k
Copy link
Contributor

@deads2k deads2k commented Jan 31, 2018

I lost your bugzilla. This adds a nasty hack to recognize that we need to specify a different group for autoscaling DCs.

/assign @DirectXMan12
/assign @juanvallejo

@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 31, 2018
@openshift-merge-robot openshift-merge-robot added the vendor-update Touching vendor dir or related files label Jan 31, 2018
@bparees bparees removed their request for review January 31, 2018 20:30
@@ -131,6 +131,11 @@ func RunAutoscale(f cmdutil.Factory, out io.Writer, cmd *cobra.Command, args []s
params["scaleRef-name"] = name
params["scaleRef-apiVersion"] = mapping.GroupVersionKind.GroupVersion().String()

// hack to make scaling DCs work.
if mapping.GroupVersionKind.Kind == "DeploymentConfig" && len(mapping.GroupVersionKind.Group) == 0 {
Copy link
Contributor

Choose a reason for hiding this comment

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

hm, this hurts to read :)

@juanvallejo
Copy link
Contributor

lgtm, could we add a test under test/cmd, perhaps?

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@deads2k
Copy link
Contributor Author

deads2k commented Feb 1, 2018

lgtm, could we add a test under test/cmd, perhaps?

test added

@deads2k deads2k added the lgtm Indicates that a PR is ready to be merged. label Feb 1, 2018
@deads2k
Copy link
Contributor Author

deads2k commented Feb 1, 2018

/retest

@juanvallejo
Copy link
Contributor

/test extended_conformance_install

@deads2k
Copy link
Contributor Author

deads2k commented Feb 1, 2018

/retest

1 similar comment
@deads2k
Copy link
Contributor Author

deads2k commented Feb 1, 2018

/retest

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/test all [submit-queue is verifying that this PR is safe to merge]

@0xmichalis
Copy link
Contributor

Issue to properly fix this?

@openshift-merge-robot
Copy link
Contributor

Automatic merge from submit-queue (batch tested with PRs 18376, 18355).

@openshift-merge-robot openshift-merge-robot merged commit 7a6d8cd into openshift:master Feb 2, 2018
@openshift-ci-robot
Copy link

@deads2k: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/openshift-jenkins/gcp e0ff016 link /test gcp

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

@deads2k
Copy link
Contributor Author

deads2k commented Feb 2, 2018

Issue to properly fix this?

I don't think there will ever be another case of this. This requires creating a separate API version ""/v1, which is explicitly disallowed by kube and cannot be aggregated.

@deads2k deads2k deleted the cli-17-autoscale branch July 3, 2018 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants