[ 
https://issues.apache.org/jira/browse/STRATOS-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lasindu Charith updated STRATOS-1533:
-------------------------------------
    Description: 
This is a duplicate of https://wso2.org/jira/browse/PAAS-166
Original Issue was marked with priority = Higher, hence marking this as 
Critical. Although the original issue was reported for PPaaS 4.0.0/Stratos 
4.0.0, this might still occur in Stratos 4.1.x, hence cross-creating the issue 
in Stratos.

This issue might occur since we create the iaas object and persist it in CC, 
but we don't repopulate those existing entries at restart.

I will keep the original issue open until this is fixed/verified. Once this 
issue is addressed, please drop a note in PPAAS jira, so that we can mark it as 
resolved.

  was:
This is a duplicate of https://wso2.org/jira/browse/PAAS-166
Original Issue was marked with priority = Higher, hence marking this as 
Critical. Although the original issue was reported for PPaaS 4.0.0/Stratos 
4.0.0, this might still occur in Stratos 4.1.x, hence cross-creating the issue 
in Stratos.

The issue might occur since we create the iaas object and persist it in CC, but 
we don't repopulate those existing entries at restart.

I will keep the original issue open until this is fixed/verified. Once this 
issue is addressed, please drop a note in PPAAS jira, so that we can mark it as 
resolved.


> After changing EC2 user account details in the stratos core, it is giving 401 
> Unauthorized error
> ------------------------------------------------------------------------------------------------
>
>                 Key: STRATOS-1533
>                 URL: https://issues.apache.org/jira/browse/STRATOS-1533
>             Project: Stratos
>          Issue Type: Bug
>            Reporter: Lasindu Charith
>            Priority: Critical
>             Fix For: FUTURE
>
>
> This is a duplicate of https://wso2.org/jira/browse/PAAS-166
> Original Issue was marked with priority = Higher, hence marking this as 
> Critical. Although the original issue was reported for PPaaS 4.0.0/Stratos 
> 4.0.0, this might still occur in Stratos 4.1.x, hence cross-creating the 
> issue in Stratos.
> This issue might occur since we create the iaas object and persist it in CC, 
> but we don't repopulate those existing entries at restart.
> I will keep the original issue open until this is fixed/verified. Once this 
> issue is addressed, please drop a note in PPAAS jira, so that we can mark it 
> as resolved.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to