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

Several issues with Configuration Manager [Ansible Tower] #13744

Closed
patchkez opened this issue Feb 2, 2017 · 8 comments
Closed

Several issues with Configuration Manager [Ansible Tower] #13744

patchkez opened this issue Feb 2, 2017 · 8 comments

Comments

@patchkez
Copy link

patchkez commented Feb 2, 2017

I started ManageIQ appliance today (master.20170202092052_6d1bdbc) and tried to add Tower provider. I was able to fill in all provider details, validation was successful. When I clicked on "Add" button, it seems provider was added, page did not change and "Add" button became unclickable:
screenshot-20170202 152440_new

Clicking on "Cancel" brought me to the list with Config. managers where I could see my provider added already. Selecting Tower manager and performing refresh or Edit actions, thrown error message in the UI:
screenshot-20170202 174240

Please let me know if If you need logs from the appliance.

@mkanoor
Copy link
Contributor

mkanoor commented Feb 2, 2017

@patchkez @bdunne
There has been some name changes from ConfigurationManagement to AutomationManagement, this could be related to that.

@bdunne
Copy link
Member

bdunne commented Feb 2, 2017

@jameswnl and @lgalis are working on the move.

@jameswnl
Copy link
Contributor

jameswnl commented Feb 2, 2017

The data migration PR #13720 is merged

@dclarizio
Copy link

@chessbyte shouldn't this be moved to ui-classic?

@patchkez
Copy link
Author

patchkez commented Feb 9, 2017

@lgalis I am still getting errors when refreshing Tower provider on latest upstream appliance. Was this issue fixed or is it still WIP?

@miq-bot
Copy link
Member

miq-bot commented Oct 7, 2017

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

@miq-bot miq-bot added the stale label Oct 7, 2017
@JPrause
Copy link
Member

JPrause commented Jan 23, 2019

@patchkez is this still a valid issue. If not can you close.
If there's no update by next week, I'll be closing this issue.

@JPrause
Copy link
Member

JPrause commented Jan 29, 2019

Closing issue. If you feel the issue needs to remain open, please let me know and it will be reopened.
@miq-bot close_issue

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

No branches or pull requests

9 participants