[
https://issues.apache.org/jira/browse/CLOUDSTACK-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605322#comment-14605322
]
ASF GitHub Bot commented on CLOUDSTACK-8589:
--------------------------------------------
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/527#issuecomment-116545842
I created the issue and added to the last commit. Did it last week:
https://issues.apache.org/jira/browse/CLOUDSTACK-8589
Perhaps you missed that.
Concerning squashed commits, ew should really have discussed about it when
you were here. I'm 100% if I squash my atomic commits next time you guys will
complain. It seems I haven't been clear enough about that yet.
@remibergsma @miguelaferreira Would you guys give your input on these
"squash commits" matter? I'm a bit tired of this discussion. For me, squashed
commits won't make a review easier, unless there is no review at all or if the
committer has changes a couple of lines in a bash script.
What I would like to see is people testing changes the way I do.
Cheers,
Wilder
> As an operator I want to be able to change the KVM hypervisor credentials
> -------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8589
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8589
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, KVM, XenServer
> Affects Versions: 4.2.0, 4.3.0, 4.4.0, 4.5.0
> Reporter: Wilder Rodrigues
> Assignee: Wilder Rodrigues
> Fix For: 4.6.0
>
>
> API call (updateHostPassword) changes credentials on XenServer hypervisor but
> not on KVM. This should be extended also for KVM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
