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

Provisioning properties tab should reflect that tenant will be chosen automatically #3567

Merged
merged 1 commit into from
Mar 13, 2018

Conversation

mansam
Copy link
Contributor

@mansam mansam commented Mar 9, 2018

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1519496 by indicating on the Properties tab whether automatic placement was selected on the Environment tab.

automaticplacement

@miq-bot
Copy link
Member

miq-bot commented Mar 9, 2018

Checked commit mansam@423dd8e with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
0 files checked, 0 offenses detected
Everything looks fine. 👍

@aufi
Copy link
Member

aufi commented Mar 12, 2018

Looks good to me 👍

@mzazrivec mzazrivec self-assigned this Mar 13, 2018
@mzazrivec mzazrivec added this to the Sprint 82 Ending Mar 26, 2018 milestone Mar 13, 2018
@mzazrivec mzazrivec merged commit 692a804 into ManageIQ:master Mar 13, 2018
simaishi pushed a commit that referenced this pull request Mar 13, 2018
Provisioning properties tab should reflect that tenant will be chosen automatically
(cherry picked from commit 692a804)

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1554832
@simaishi
Copy link
Contributor

Gaprindashvili backport details:

$ git log -1
commit e57679b6ef5189275ce0fba69734dc58c215648e
Author: Milan Zázrivec <[email protected]>
Date:   Tue Mar 13 09:25:26 2018 +0100

    Merge pull request #3567 from mansam/automatic-placement-quota-ui
    
    Provisioning properties tab should reflect that tenant will be chosen automatically
    (cherry picked from commit 692a804babab07248512a6c7b15e8296f9b1fda5)
    
    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1554832

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants