[jira] [Commented] (CLOUDSTACK-10235) Removing Port Forwarding rule deletes public interface on VR (redundant VPC only)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-10235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330069#comment-16330069
]
Alexander Conn commented on CLOUDSTACK-10235:
-
Have confirmed /opt/cloud/bin/cloud-nic.sh is definitely being called to
add/remove the eth1 (public) nic. Does anyone know where exactly this shell
script gets called? Going through the code for 4.9.3 on GitHub and I'm having a
hard time trying to find at what point this gets called.
I modified cloud-nic.sh to add some extra logging, as per below log snippets
the extra output is in bold. It looks like cloud-nic.sh gets called at the end
of removing the PF rule and at the beginning of adding the PF rule
+/var/log/cloud.log when PF rule is removed:+
.
2018-01-18 05:11:39,908 CsRedundant.py _redundant_on:103 Wait for devices to be
configured so we can start keepalived
2018-01-18 05:11:39,908 CsHelper.py execute:184 Executing: ip link show eth3 |
grep 'state UP'
2018-01-18 05:11:39,922 CsRedundant.py _redundant_on:109 Device eth3 is
present, let's start keepalive now.
2018-01-18 05:11:39,923 CsHelper.py execute:184 Executing: mount
2018-01-18 05:11:39,936 CsHelper.py execute:184 Executing: sed -i "s/--exec\
\$DAEMON;/--exec\ \$DAEMON\ --\ --vrrp;/g" /etc/init.d/keepalived
2018-01-18 05:11:39,948 CsFile.py load:39 Reading file
/opt/cloud/bin/checkrouter.sh
2018-01-18 05:11:39,949 CsFile.py greplace:116 Searching for [RROUTER_LOG] and
replacing with /var/log/cloud.log
2018-01-18 05:11:39,949 CsFile.py commit:60 Nothing to commit. The
/opt/cloud/bin/checkrouter.sh file did not change
2018-01-18 05:11:39,949 CsFile.py load:39 Reading file
/etc/keepalived/keepalived.conf
2018-01-18 05:11:39,950 CsFile.py search:124 Searching for router_id and
replacing with router_id r-3882-VM
2018-01-18 05:11:39,950 CsFile.py search:124 Searching for interface and
replacing with interface eth3
2018-01-18 05:11:39,951 CsFile.py search:124 Searching for advert_int and
replacing with advert_int 1
2018-01-18 05:11:39,951 CsFile.py greplace:116 Searching for [RROUTER_BIN_PATH]
and replacing with /ramdisk/rrouter
2018-01-18 05:11:39,952 CsHelper.py copy:251 Copied
/opt/cloud/templates/conntrackd.conf.templ to
/opt/cloud/templates/conntrackd.conf.templ.bkp
2018-01-18 05:11:39,953 CsFile.py load:39 Reading file
/opt/cloud/templates/conntrackd.conf.templ
2018-01-18 05:11:39,954 CsFile.py commit:66 Wrote edited file
/opt/cloud/templates/conntrackd.conf.templ
2018-01-18 05:11:39,954 CsFile.py commit:68 Updated file in-cache configuration
2018-01-18 05:11:39,954 CsFile.py load:39 Reading file
/etc/conntrackd/conntrackd.conf
2018-01-18 05:11:39,954 CsFile.py compare:168 Comparison of CsFiles content is
==> True
2018-01-18 05:11:39,954 CsHelper.py execute:184 Executing: ps aux
2018-01-18 05:11:39,983 CsProcess.py find_pid:50 CsProcess:: Searching for
process ==> ['/etc/conntrackd/conntrackd.conf'] and found PIDs ==> ['4473']
2018-01-18 05:11:39,984 CsHelper.py copy:251 Copied
/opt/cloud/templates/conntrackd.conf.templ.bkp to
/opt/cloud/templates/conntrackd.conf.templ
2018-01-18 05:11:39,984 CsHelper.py execute:184 Executing: rm -rf
/opt/cloud/templates/conntrackd.conf.templ.bkp
2018-01-18 05:11:39,996 CsFile.py load:39 Reading file /etc/cron.d/heartbeat
2018-01-18 05:11:39,997 CsFile.py commit:60 Nothing to commit. The
/etc/cron.d/heartbeat file did not change
2018-01-18 05:11:39,997 CsHelper.py execute:184 Executing: ps aux
2018-01-18 05:11:40,021 CsProcess.py find_pid:50 CsProcess:: Searching for
process ==> ['/usr/sbin/keepalived'] and found PIDs ==> ['4487', '4488', '4489']
*parent command udevd*
*removing 1 Table_eth1 for eth1*
*removed 1 Table_eth1 for eth1*
+/var/log/cloud.log when PF rule is added:+
*parent command udevd*
*adding 1 Table_eth1*
*added 1 Table_eth1*
2018-01-18 05:20:52,017 merge.py load:57 Loading data bag type ips
2018-01-18 05:20:52,018 merge.py process:101 Command of type ips received
2018-01-18 05:20:52,018 merge.py save:68 Writing data bag type ips
2018-01-18 05:20:52,020 merge.py load:57 Loading data bag type ips
2018-01-18 05:20:52,020 merge.py load:57 Loading data bag type cmdline
2018-01-18 05:20:52,020 configure.py main:935 Configuring ip addresses
2018-01-18 05:20:52,021 CsHelper.py execute:184 Executing: ip addr show dev eth3
2018-01-18 05:20:52,033 CsAddress.py is_guest_gateway:680 Checking if cidr is a
gateway for rVPC. IP ==> 10.100.104.254/24 / device ==> eth3
2018-01-18 05:20:52,034 CsAddress.py is_guest_gateway:683 Interface has the
following gateway ==> 10.100.104.254
2018-01-18 05:20:52,034 CsAddress.py compare:668 The IP address in
'\{u'public_ip': u'10.100.104.251', u'one_to_one_nat': False, u'nic_dev_id':
u'3', u'network': u'10.100.104.0/24', u'netmask': u'255.255.255.0',
u'source_nat': False, u'broadcast': u'10.100.104.255', u'add': True,
u'nw_type': u'guest', u'device': u'eth3', u'cidr':
[jira] [Commented] (CLOUDSTACK-10238) Fix for metalink support on SSVM agents
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329991#comment-16329991 ] ASF GitHub Bot commented on CLOUDSTACK-10238: - nvazquez opened a new pull request #2411: CLOUDSTACK-10238: Fix for metalink support on SSVM agents URL: https://github.com/apache/cloudstack/pull/2411 Fix for #2379. In that PR, aria2 dependency is added to system vm template to support metalink downloads on SSVM agents. This feature fixes metalink downloader issue and extends metalink support for OVA and ISO formats. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Fix for metalink support on SSVM agents > --- > > Key: CLOUDSTACK-10238 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10238 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nicolas Vazquez >Assignee: Nicolas Vazquez >Priority: Major > > Fix for metalink support -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CLOUDSTACK-10238) Fix for metalink support on SSVM agents
Nicolas Vazquez created CLOUDSTACK-10238: Summary: Fix for metalink support on SSVM agents Key: CLOUDSTACK-10238 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10238 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nicolas Vazquez Assignee: Nicolas Vazquez Fix for metalink support -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CLOUDSTACK-10237) L2 networks should be allowed to be shared and used in projects
[
https://issues.apache.org/jira/browse/CLOUDSTACK-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Angus reassigned CLOUDSTACK-10237:
---
Assignee: Nicolas Vazquez
> L2 networks should be allowed to be shared and used in projects
> ---
>
> Key: CLOUDSTACK-10237
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10237
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: Centos7, KVM, advanced zones with vlan based isolation
>Reporter: Jean-Francois Nadeau
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Hi all,
>
> I'm testing 4.11-rc1 and the new L2 network type feature as shown at
> [http://www.shapeblue.com/layer-2-networks-in-cloudstack/]
>
> I want to use this as a replacement to a shared network offering with no DHCP
> which works to support an external DHCP server but still required to fill
> some CIDR information.
>
> I thought the intent was that L2 network type was to replace the previous
> approach when required to integrate an existing network/DHCP.
>
> If I attempt to provision a VM in a project as the root admin using the L2
> network I get denied... apparently because they are not shared and I can't
> make them public.
>
> ('HTTP 531 response from CloudStack', , \{u'errorcode': 531,
> u'uuidList': [], u'cserrorcode': 4365, u'errortext': u'Unable to use network
> with id= 7712102b-bbdf-4c54-bdbf-9fddfa16de46, permission denied'})
>
> Provisioning in the root project works just fine but really I want to
> use L2 networks in user projects even if only the admin can do so.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CLOUDSTACK-10237) L2 networks should be allowed to be shared and used in projects
Jean-Francois Nadeau created CLOUDSTACK-10237:
-
Summary: L2 networks should be allowed to be shared and used in
projects
Key: CLOUDSTACK-10237
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10237
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.11.0.0
Environment: Centos7, KVM, advanced zones with vlan based isolation
Reporter: Jean-Francois Nadeau
Hi all,
I'm testing 4.11-rc1 and the new L2 network type feature as shown at
[http://www.shapeblue.com/layer-2-networks-in-cloudstack/]
I want to use this as a replacement to a shared network offering with no DHCP
which works to support an external DHCP server but still required to fill some
CIDR information.
I thought the intent was that L2 network type was to replace the previous
approach when required to integrate an existing network/DHCP.
If I attempt to provision a VM in a project as the root admin using the L2
network I get denied... apparently because they are not shared and I can't make
them public.
('HTTP 531 response from CloudStack', , \{u'errorcode': 531,
u'uuidList': [], u'cserrorcode': 4365, u'errortext': u'Unable to use network
with id= 7712102b-bbdf-4c54-bdbf-9fddfa16de46, permission denied'})
Provisioning in the root project works just fine but really I want to use
L2 networks in user projects even if only the admin can do so.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (CLOUDSTACK-10234) HA fails in cases of PSU failure.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-10234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nux closed CLOUDSTACK-10234.
Resolution: Later
This issue needs a more thorough rethink as it could lead to data corruption.
For now Host HA only works as long as the IPMIs are within reach.
> HA fails in cases of PSU failure.
> -
>
> Key: CLOUDSTACK-10234
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10234
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: 4.11 RC1, NFS storage, CentOS 7 management server and
> hypervisors
>Reporter: Nux
>Assignee: Rohit Yadav
>Priority: Major
> Labels: HA, KVM
>
> To simulate PSU failure I pulled the power from the server physically, HA
> fails to do the right thing and move the affected VMs to other HVs.
> I waited a good while, but alas nothing happened. The VM and VR running on
> the affected hypervisor were never moved to another one (I have another 2
> running).
> Is there any way to at least force the system to mark that HV as bad/offline?
> This is what I see in the management server logs:
> {code:java}
> Caused by: com.cloud.utils.exception.CloudRuntimeException: Out-of-band
> Management action (OFF) on host (57bf86e0-e1cd-484e-a4f1-78b3ca2da125) failed
> with error: Get Auth Capabilities error Error issuing Get Channel
> Authentication Capabilities request Error: Unable to establish IPMI v2 /
> RMCP+ session at
> org.apache.cloudstack.outofbandmanagement.OutOfBandManagementServiceImpl.executePowerOperation(OutOfBandManagementServiceImpl.java:423)
> at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ... 21 more 2018-01-16 17:00:13,396 WARN [o.a.c.alerts]
> (pool-5-thread-7:null) (logid:4f7299f6) AlertType:: 30 | dataCenterId:: 1 |
> podId:: 1 | clusterId:: null | message:: HA Fencing of host id=1, in dc id=1
> performed 2018-01-16 17:00:15,375 DEBUG [c.c.a.t.Request]
> (pool-2-thread-27:null) (logid:6b21a8c1) Seq 5-9115285645797884785: Sending
> \{ Cmd , MgmtId: 161334379813, via: 5(hv03.cloud.local), Ver: v1, Flags:
> 100011,
> [{"com.cloud.agent.api.CheckOnHostCommand":{"host":{"guid":"598d48ef-158d-3e14-ad68-8d02c9368ddf-LibvirtComputingResource","privateNetwork":{"ip":"172.16.25.101","netmask":"255.255.255.240","mac":"0c:c4:7a:40:8e:f6","isSecurityGroupEnabled":false},"publicNetwork":\{"ip":"172.16.25.101","netmask":"255.255.255.240","mac":"0c:c4:7a:40:8e:f6","isSecurityGroupEnabled":false},"storageNetwork1":\{"ip":"172.16.25.101","netmask":"255.255.255.240","mac":"0c:c4:7a:40:8e:f6","isSecurityGroupEnabled":false}},"wait":20}}]
> } 2018-01-16 17:00:15,380 DEBUG [c.c.a.t.Request] (pool-2-thread-5:null)
> (logid:bb993597) Seq 4-6582855280332112812: Sending \{ Cmd , MgmtId:
> 161334379813, via: 4(hv02.cloud.local), Ver: v1, Flags: 100011,
> [{"com.cloud.agent.api.CheckOnHostCommand":{"host":{"guid":"6ebb3010-9c49-3a9c-b620-ecbc9731aca2-LibvirtComputingResource","privateNetwork":{"ip":"172.16.25.100","netmask":"255.255.255.240","mac":"0c:c4:7a:40:8e:8e","isSecurityGroupEnabled":false},"publicNetwork":\{"ip":"172.16.25.100","netmask":"255.255.255.240","mac":"0c:c4:7a:40:8e:8e","isSecurityGroupEnabled":false},"storageNetwork1":\{"ip":"172.16.25.100","netmask":"255.255.255.240","mac":"0c:c4:7a:40:8e:8e","isSecurityGroupEnabled":false}},"wait":20}}]
> } 2018-01-16 17:00:15,423 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-4:null) (logid:) Seq 5-9115285645797884785: Processing:
> \{ Ans: , MgmtId: 161334379813, via: 5, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"Heart is
> beating...","wait":0}}] } 2018-01-16 17:00:15,423 DEBUG [c.c.a.t.Request]
> (pool-2-thread-27:null) (logid:6b21a8c1) Seq 5-9115285645797884785: Received:
> \{ Ans: , MgmtId: 161334379813, via: 5(hv03.cloud.local), Ver: v1, Flags:
> 10, { Answer } } 2018-01-16 17:00:15,423 DEBUG [c.c.a.m.AgentManagerImpl]
> (pool-2-thread-27:null) (logid:6b21a8c1) Details from executing class
> com.cloud.agent.api.CheckOnHostCommand: Heart is beating... 2018-01-16
> 17:00:15,427 DEBUG [c.c.a.t.Request] (AgentManager-Handler-6:null) (logid:)
> Seq 4-6582855280332112812: Processing: \{ Ans: , MgmtId: 161334379813, via:
> 4, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"Heart is
> beating...","wait":0}}] } 2018-01-16 17:00:15,427 DEBUG [c.c.a.t.Request]
> (pool-2-thread-5:null) (logid:bb993597) Seq 4-6582855280332112812: Received:
> \{ Ans: , MgmtId: 161334379813, via: 4(hv02.cloud.local), Ver:
[jira] [Commented] (CLOUDSTACK-9749) cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by password server on lb VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328840#comment-16328840 ] Kris Sterckx commented on CLOUDSTACK-9749: -- I am not clear on what the Apache Jira policy is about "resolved" state. Isn't confusing that a ticket is set to Resolved but the fix is not yet merged in ? It might be just me who is confused. [~bhaisaab] can you clarify the policy about Resolved state in Jira ? > cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by > password server on lb VM > -- > > Key: CLOUDSTACK-9749 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9749 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.10.0.0, 4.9.2.0, 4.8.2.0, 4.11.0.0 >Reporter: Raf Smeets >Assignee: Frank Maximus >Priority: Critical > Fix For: 4.10.0.0 > > Attachments: runinfo.txt > > > cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by > password server on lb VM > Executed test/integration/plugins/nuagevsp/test_nuage_vpc_internal_lb.py > which failed in test_05_nuage_internallb_traffic at the point where it is > checking the lb via wget of file using port 8080. > As port 8080 already is occupied by the password_server, it fails. > I have added the runinfo.txt of the failing test to this bugticket. > Similar issue was reported internally via CLOUD-972. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328815#comment-16328815 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - marcaurele commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358317969 @rhtyd ack, I will - thanks for the link to the docker images This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CLOUDSTACK-10236) Unable to login to ACS after upgrading 4.5 -> 4.11
[
https://issues.apache.org/jira/browse/CLOUDSTACK-10236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Stoyanov updated CLOUDSTACK-10236:
Description:
I've upgraded my CentOS6 env from 4.5 to 4.11 and ended up not being able to
login. I'm getting 'Session expired' message right after I enter my admin
username and password. Here's the management log output:
{code:java}
2018-01-17 13:07:47,383 DEBUG [c.c.u.AccountManagerImpl]
(qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) Attempting to log in user:
admin in domain 1
2018-01-17 13:07:47,389 DEBUG [o.a.c.s.a.PBKDF2UserAuthenticator]
(qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) Retrieving user: admin
2018-01-17 13:07:48,248 DEBUG [c.c.u.AccountManagerImpl]
(qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) CIDRs from which account
'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed to perform API
calls: 0.0.0.0/0,::/0
2018-01-17 13:07:48,249 DEBUG [c.c.u.AccountManagerImpl]
(qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) User: admin in domain 1 has
successfully logged in
2018-01-17 13:07:48,260 INFO [c.c.a.ApiServer] (qtp1310540333-19:ctx-404c4037)
(logid:2d1dd5ba) Current user logged in under UTC timezone
2018-01-17 13:07:48,260 INFO [c.c.a.ApiServer] (qtp1310540333-19:ctx-404c4037)
(logid:2d1dd5ba) Timezone offset from UTC is: 0.0
2018-01-17 13:07:48,267 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) ===END=== 10.1.0.1 – POST
2018-01-17 13:07:48,340 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-16:ctx-390d3282) (logid:b98a9144) ===START=== 10.1.0.1 – GET
command=listCapabilities=json&_=1516194514030
2018-01-17 13:07:48,349 DEBUG [c.c.a.ApiServer] (qtp1310540333-16:ctx-390d3282
ctx-0509900f) (logid:b98a9144) CIDRs from which account
'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed to perform API
calls: 0.0.0.0/0,::/0
2018-01-17 13:07:48,372 DEBUG [c.c.a.ApiServlet] (qtp1310540333-16:ctx-390d3282
ctx-0509900f) (logid:b98a9144) ===END=== 10.1.0.1 – GET
command=listCapabilities=json&_=1516194514030
2018-01-17 13:07:48,439 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-19:ctx-495f6fd0) (logid:67992211) ===START=== 10.1.0.1 – GET
command=listZones=json&_=1516194514137
2018-01-17 13:07:48,449 DEBUG [c.c.a.ApiServer] (qtp1310540333-19:ctx-495f6fd0
ctx-606dcc84) (logid:67992211) CIDRs from which account
'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed to perform API
calls: 0.0.0.0/0,::/0
2018-01-17 13:07:48,474 DEBUG [c.c.a.ApiServlet] (qtp1310540333-19:ctx-495f6fd0
ctx-606dcc84) (logid:67992211) ===END=== 10.1.0.1 – GET
command=listZones=json&_=1516194514137
2018-01-17 13:07:48,549 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-16:ctx-f2bcf13f) (logid:f73a6f0c) ===START=== 10.1.0.1 – GET
command=cloudianIsEnabled=json&_=1516194514249
2018-01-17 13:07:48,556 DEBUG [c.c.a.ApiServer] (qtp1310540333-16:ctx-f2bcf13f
ctx-3e6a3a41) (logid:f73a6f0c) CIDRs from which account
'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed to perform API
calls: 0.0.0.0/0,::/0
2018-01-17 13:07:48,579 DEBUG [c.c.a.ApiServlet] (qtp1310540333-16:ctx-f2bcf13f
ctx-3e6a3a41) (logid:f73a6f0c) ===END=== 10.1.0.1 – GET
command=cloudianIsEnabled=json&_=1516194514249
2018-01-17 13:07:48,645 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-19:ctx-560f926e) (logid:62a5cb2f) ===START=== 10.1.0.1 – GET
command=quotaIsEnabled=json&_=1516194514343
2018-01-17 13:07:48,653 DEBUG [c.c.a.ApiServer] (qtp1310540333-19:ctx-560f926e
ctx-c9a2914a) (logid:62a5cb2f) CIDRs from which account
'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed to perform API
calls: 0.0.0.0/0,::/0
2018-01-17 13:07:48,658 DEBUG [c.c.a.ApiServer] (qtp1310540333-19:ctx-560f926e
ctx-c9a2914a) (logid:62a5cb2f) The given command 'quotaIsEnabled' either does
not exist, is not available for user, or not available from ip address
'/10.1.0.1'.
2018-01-17 13:07:48,660 DEBUG [c.c.a.ApiServlet] (qtp1310540333-19:ctx-560f926e
ctx-c9a2914a) (logid:62a5cb2f) ===END=== 10.1.0.1 – GET
command=quotaIsEnabled=json&_=1516194514343
2018-01-17 13:07:48,738 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-16:ctx-9b8e4337) (logid:3c2cd5ee) ===START=== 10.1.0.1 – GET
command=listProjectInvitations=json=Pending&_=1516194514436
2018-01-17 13:07:48,739 DEBUG [c.c.a.ApiServer] (qtp1310540333-16:ctx-9b8e4337
ctx-9814e0e7) (logid:3c2cd5ee) Expired session, missing signature, or missing
apiKey – ignoring request. Signature: null, apiKey: null
2018-01-17 13:07:48,741 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-20:ctx-a4668354) (logid:337ae399) ===START=== 10.1.0.1 – GET
command=listProjects=json=3daaa51e-fb6a-11e7-ae7e-06efa8010701=true=1=500&_=1516194514440
2018-01-17 13:07:48,742 DEBUG [c.c.a.ApiServer] (qtp1310540333-20:ctx-a4668354
ctx-b627f275) (logid:337ae399) Expired session, missing signature, or missing
apiKey – ignoring request. Signature: null, apiKey: null
2018-01-17
[jira] [Created] (CLOUDSTACK-10236) Unable to login to ACS after upgrading 4.5 -> 4.11
Boris Stoyanov created CLOUDSTACK-10236:
---
Summary: Unable to login to ACS after upgrading 4.5 -> 4.11
Key: CLOUDSTACK-10236
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10236
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.11.0.0
Reporter: Boris Stoyanov
Fix For: 4.11.0.0
I've upgraded my CentOS6 env from 4.5 to 4.11 and ended up not being able to
login. I'm getting 'Session expired' message right after I enter my admin
username and password. Here's the management log output:
{code}
2018-01-17 13:07:47,383 DEBUG [c.c.u.AccountManagerImpl]
(qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) Attempting to log in user:
admin in domain 1
2018-01-17 13:07:47,389 DEBUG [o.a.c.s.a.PBKDF2UserAuthenticator]
(qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) Retrieving user: admin
2018-01-17 13:07:48,248 DEBUG [c.c.u.AccountManagerImpl]
(qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) CIDRs from which account
'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed to perform API
calls: 0.0.0.0/0,::/0
2018-01-17 13:07:48,249 DEBUG [c.c.u.AccountManagerImpl]
(qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) User: admin in domain 1 has
successfully logged in
2018-01-17 13:07:48,260 INFO [c.c.a.ApiServer] (qtp1310540333-19:ctx-404c4037)
(logid:2d1dd5ba) Current user logged in under UTC timezone
2018-01-17 13:07:48,260 INFO [c.c.a.ApiServer] (qtp1310540333-19:ctx-404c4037)
(logid:2d1dd5ba) Timezone offset from UTC is: 0.0
2018-01-17 13:07:48,267 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) ===END=== 10.1.0.1 -- POST
2018-01-17 13:07:48,340 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-16:ctx-390d3282) (logid:b98a9144) ===START=== 10.1.0.1 -- GET
command=listCapabilities=json&_=1516194514030
2018-01-17 13:07:48,349 DEBUG [c.c.a.ApiServer] (qtp1310540333-16:ctx-390d3282
ctx-0509900f) (logid:b98a9144) CIDRs from which account
'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed to perform API
calls: 0.0.0.0/0,::/0
2018-01-17 13:07:48,372 DEBUG [c.c.a.ApiServlet] (qtp1310540333-16:ctx-390d3282
ctx-0509900f) (logid:b98a9144) ===END=== 10.1.0.1 -- GET
command=listCapabilities=json&_=1516194514030
2018-01-17 13:07:48,439 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-19:ctx-495f6fd0) (logid:67992211) ===START=== 10.1.0.1 -- GET
command=listZones=json&_=1516194514137
2018-01-17 13:07:48,449 DEBUG [c.c.a.ApiServer] (qtp1310540333-19:ctx-495f6fd0
ctx-606dcc84) (logid:67992211) CIDRs from which account
'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed to perform API
calls: 0.0.0.0/0,::/0
2018-01-17 13:07:48,474 DEBUG [c.c.a.ApiServlet] (qtp1310540333-19:ctx-495f6fd0
ctx-606dcc84) (logid:67992211) ===END=== 10.1.0.1 -- GET
command=listZones=json&_=1516194514137
2018-01-17 13:07:48,549 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-16:ctx-f2bcf13f) (logid:f73a6f0c) ===START=== 10.1.0.1 -- GET
command=cloudianIsEnabled=json&_=1516194514249
2018-01-17 13:07:48,556 DEBUG [c.c.a.ApiServer] (qtp1310540333-16:ctx-f2bcf13f
ctx-3e6a3a41) (logid:f73a6f0c) CIDRs from which account
'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed to perform API
calls: 0.0.0.0/0,::/0
2018-01-17 13:07:48,579 DEBUG [c.c.a.ApiServlet] (qtp1310540333-16:ctx-f2bcf13f
ctx-3e6a3a41) (logid:f73a6f0c) ===END=== 10.1.0.1 -- GET
command=cloudianIsEnabled=json&_=1516194514249
2018-01-17 13:07:48,645 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-19:ctx-560f926e) (logid:62a5cb2f) ===START=== 10.1.0.1 -- GET
command=quotaIsEnabled=json&_=1516194514343
2018-01-17 13:07:48,653 DEBUG [c.c.a.ApiServer] (qtp1310540333-19:ctx-560f926e
ctx-c9a2914a) (logid:62a5cb2f) CIDRs from which account
'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed to perform API
calls: 0.0.0.0/0,::/0
2018-01-17 13:07:48,658 DEBUG [c.c.a.ApiServer] (qtp1310540333-19:ctx-560f926e
ctx-c9a2914a) (logid:62a5cb2f) The given command 'quotaIsEnabled' either does
not exist, is not available for user, or not available from ip address
'/10.1.0.1'.
2018-01-17 13:07:48,660 DEBUG [c.c.a.ApiServlet] (qtp1310540333-19:ctx-560f926e
ctx-c9a2914a) (logid:62a5cb2f) ===END=== 10.1.0.1 -- GET
command=quotaIsEnabled=json&_=1516194514343
2018-01-17 13:07:48,738 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-16:ctx-9b8e4337) (logid:3c2cd5ee) ===START=== 10.1.0.1 -- GET
command=listProjectInvitations=json=Pending&_=1516194514436
2018-01-17 13:07:48,739 DEBUG [c.c.a.ApiServer] (qtp1310540333-16:ctx-9b8e4337
ctx-9814e0e7) (logid:3c2cd5ee) Expired session, missing signature, or missing
apiKey -- ignoring request. Signature: null, apiKey: null
2018-01-17 13:07:48,741 DEBUG [c.c.a.ApiServlet]
(qtp1310540333-20:ctx-a4668354) (logid:337ae399) ===START=== 10.1.0.1 --
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328674#comment-16328674 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358248079 Let's hold on merging this -- we need to run tests across xenserver, vmware and kvm before this may be accepted. This will potentially break every other outstanding PR, but agree if it needs to be done now is a good time. Let me also find some time to review the PR. Update - another thing that will cause an issue is, forward merging bugfixes from older releases/branches. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328673#comment-16328673 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358248079 Let's hold on merging this -- we need to run tests across xenserver, vmware and kvm before this may be accepted. This will potentially break every other outstanding PR, but agree if it needs to be done now is a good time. Let me also find some time to review the PR. Update - another think that will cause an issue is, forward merging bugfixes from older releases/branches. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-7857) CitrixResourceBase wrongly calculates total memory on hosts with a lot of memory and large Dom0
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328610#comment-16328610
]
Romain Kubany commented on CLOUDSTACK-7857:
---
The issue still exists on CloudStack 4.10, how can we help ?
> CitrixResourceBase wrongly calculates total memory on hosts with a lot of
> memory and large Dom0
> ---
>
> Key: CLOUDSTACK-7857
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7857
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.3.0, 4.4.0, 4.5.0, 4.3.1, 4.4.1, 4.6.0
>Reporter: Joris van Lieshout
>Priority: Major
>
> We have hosts with 256GB memory and 4GB dom0. During startup ACS calculates
> available memory using this formula:
> CitrixResourceBase.java
> protected void fillHostInfo
> ram = (long) ((ram - dom0Ram - _xs_memory_used) *
> _xs_virtualization_factor);
> In our situation:
> ram = 274841497600
> dom0Ram = 4269801472
> _xs_memory_used = 128 * 1024 * 1024L = 134217728
> _xs_virtualization_factor = 63.0/64.0 = 0,984375
> (274841497600 - 4269801472 - 134217728) * 0,984375 = 266211892800
> This is in fact not the actual amount of memory available for instances. The
> difference in our situation is a little less then 1GB. On this particular
> hypervisor Dom0+Xen uses about 9GB.
> As the comment above the definition of XsMemoryUsed allready stated it's time
> to review this logic.
> "//Hypervisor specific params with generic value, may need to be overridden
> for specific versions"
> The effect of this bug is that when you put a hypervisor in maintenance it
> might try to move instances (usually small instances (<1GB)) to a host that
> in fact does not have enought free memory.
> This exception is thrown:
> ERROR [c.c.h.HighAvailabilityManagerImpl] (HA-Worker-3:ctx-09aca6e9
> work-8981) Terminating HAWork[8981-Migration-4482-Running-Migrating]
> com.cloud.utils.exception.CloudRuntimeException: Unable to migrate due to
> Catch Exception com.cloud.utils.exception.CloudRuntimeException: Migration
> failed due to com.cloud.utils.exception.CloudRuntim
> eException: Unable to migrate VM(r-4482-VM) from
> host(6805d06c-4d5b-4438-a245-7915e93041d9) due to Task failed! Task record:
> uuid: 645b63c8-1426-b412-7b6a-13d61ee7ab2e
>nameLabel: Async.VM.pool_migrate
> nameDescription:
>allowedOperations: []
>currentOperations: {}
> created: Thu Nov 06 13:44:14 CET 2014
> finished: Thu Nov 06 13:44:14 CET 2014
> status: failure
> residentOn: com.xensource.xenapi.Host@b42882c6
> progress: 1.0
> type:
> result:
>errorInfo: [HOST_NOT_ENOUGH_FREE_MEMORY, 272629760, 263131136]
> otherConfig: {}
>subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> subtasks: []
> at
> com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:1840)
> at
> com.cloud.vm.VirtualMachineManagerImpl.migrateAway(VirtualMachineManagerImpl.java:2214)
> at
> com.cloud.ha.HighAvailabilityManagerImpl.migrate(HighAvailabilityManagerImpl.java:610)
> at
> com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.runWithContext(HighAvailabilityManagerImpl.java:865)
> at
> com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.access$000(HighAvailabilityManagerImpl.java:822)
> at
> com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread$1.run(HighAvailabilityManagerImpl.java:834)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.run(HighAvailabilityManagerImpl.java:831)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328599#comment-16328599 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358261881 @marcaurele can you fix packaging for CentOS6 and 7. CentOS6 packaging fails due to: + cp -r 'plugins/network-elements/cisco-vnmc/scripts/network/cisco/*' /jenkins/workspace/acs-pr-centos6-pkg-builder/dist/rpmbuild/BUILDROOT/cloudstack-4.12.0.0-shapeblue1671.el6.x86_64/usr/share/cloudstack-common/scripts/network/cisco cp: cannot stat `plugins/network-elements/cisco-vnmc/scripts/network/cisco/*': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.lS7NDO (%install) CentOS7 fails due to: + cp -r 'plugins/network-elements/cisco-vnmc/scripts/network/cisco/*' /jenkins/workspace/acs-pr-centos7-pkg-builder/dist/rpmbuild/BUILDROOT/cloudstack-4.12.0.0-shapeblue1674.el7.centos.x86_64/usr/share/cloudstack-common/scripts/network/cisco cp: cannot stat 'plugins/network-elements/cisco-vnmc/scripts/network/cisco/*': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.mUH4PE (%install) For your local testing, you can use following docker images: https://hub.docker.com/r/bhaisaab/centos7-cloudstack-slave/ https://hub.docker.com/r/bhaisaab/centos6-cloudstack-slave/ This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328592#comment-16328592 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - blueorangutan commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358260428 Packaging result: ✖centos6 ✖centos7 ✔debian. JID-1657 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328590#comment-16328590 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - marcaurele commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358259970 @rhtyd it's removed in this PR This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328587#comment-16328587 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358258909 @marcaurele do we need `marven-standard` now, can we remove that as well? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328561#comment-16328561 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358253140 @blueorangutan package This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328560#comment-16328560 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358249028 @blueorangutan package This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CLOUDSTACK-10234) HA fails in cases of PSU failure.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-10234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohit Yadav reassigned CLOUDSTACK-10234:
Assignee: Rohit Yadav
> HA fails in cases of PSU failure.
> -
>
> Key: CLOUDSTACK-10234
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10234
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: 4.11 RC1, NFS storage, CentOS 7 management server and
> hypervisors
>Reporter: Nux
>Assignee: Rohit Yadav
>Priority: Major
> Labels: HA, KVM
>
> To simulate PSU failure I pulled the power from the server physically, HA
> fails to do the right thing and move the affected VMs to other HVs.
> I waited a good while, but alas nothing happened. The VM and VR running on
> the affected hypervisor were never moved to another one (I have another 2
> running).
> Is there any way to at least force the system to mark that HV as bad/offline?
> This is what I see in the management server logs:
> {code:java}
> Caused by: com.cloud.utils.exception.CloudRuntimeException: Out-of-band
> Management action (OFF) on host (57bf86e0-e1cd-484e-a4f1-78b3ca2da125) failed
> with error: Get Auth Capabilities error Error issuing Get Channel
> Authentication Capabilities request Error: Unable to establish IPMI v2 /
> RMCP+ session at
> org.apache.cloudstack.outofbandmanagement.OutOfBandManagementServiceImpl.executePowerOperation(OutOfBandManagementServiceImpl.java:423)
> at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ... 21 more 2018-01-16 17:00:13,396 WARN [o.a.c.alerts]
> (pool-5-thread-7:null) (logid:4f7299f6) AlertType:: 30 | dataCenterId:: 1 |
> podId:: 1 | clusterId:: null | message:: HA Fencing of host id=1, in dc id=1
> performed 2018-01-16 17:00:15,375 DEBUG [c.c.a.t.Request]
> (pool-2-thread-27:null) (logid:6b21a8c1) Seq 5-9115285645797884785: Sending
> \{ Cmd , MgmtId: 161334379813, via: 5(hv03.cloud.local), Ver: v1, Flags:
> 100011,
> [{"com.cloud.agent.api.CheckOnHostCommand":{"host":{"guid":"598d48ef-158d-3e14-ad68-8d02c9368ddf-LibvirtComputingResource","privateNetwork":{"ip":"172.16.25.101","netmask":"255.255.255.240","mac":"0c:c4:7a:40:8e:f6","isSecurityGroupEnabled":false},"publicNetwork":\{"ip":"172.16.25.101","netmask":"255.255.255.240","mac":"0c:c4:7a:40:8e:f6","isSecurityGroupEnabled":false},"storageNetwork1":\{"ip":"172.16.25.101","netmask":"255.255.255.240","mac":"0c:c4:7a:40:8e:f6","isSecurityGroupEnabled":false}},"wait":20}}]
> } 2018-01-16 17:00:15,380 DEBUG [c.c.a.t.Request] (pool-2-thread-5:null)
> (logid:bb993597) Seq 4-6582855280332112812: Sending \{ Cmd , MgmtId:
> 161334379813, via: 4(hv02.cloud.local), Ver: v1, Flags: 100011,
> [{"com.cloud.agent.api.CheckOnHostCommand":{"host":{"guid":"6ebb3010-9c49-3a9c-b620-ecbc9731aca2-LibvirtComputingResource","privateNetwork":{"ip":"172.16.25.100","netmask":"255.255.255.240","mac":"0c:c4:7a:40:8e:8e","isSecurityGroupEnabled":false},"publicNetwork":\{"ip":"172.16.25.100","netmask":"255.255.255.240","mac":"0c:c4:7a:40:8e:8e","isSecurityGroupEnabled":false},"storageNetwork1":\{"ip":"172.16.25.100","netmask":"255.255.255.240","mac":"0c:c4:7a:40:8e:8e","isSecurityGroupEnabled":false}},"wait":20}}]
> } 2018-01-16 17:00:15,423 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-4:null) (logid:) Seq 5-9115285645797884785: Processing:
> \{ Ans: , MgmtId: 161334379813, via: 5, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"Heart is
> beating...","wait":0}}] } 2018-01-16 17:00:15,423 DEBUG [c.c.a.t.Request]
> (pool-2-thread-27:null) (logid:6b21a8c1) Seq 5-9115285645797884785: Received:
> \{ Ans: , MgmtId: 161334379813, via: 5(hv03.cloud.local), Ver: v1, Flags:
> 10, { Answer } } 2018-01-16 17:00:15,423 DEBUG [c.c.a.m.AgentManagerImpl]
> (pool-2-thread-27:null) (logid:6b21a8c1) Details from executing class
> com.cloud.agent.api.CheckOnHostCommand: Heart is beating... 2018-01-16
> 17:00:15,427 DEBUG [c.c.a.t.Request] (AgentManager-Handler-6:null) (logid:)
> Seq 4-6582855280332112812: Processing: \{ Ans: , MgmtId: 161334379813, via:
> 4, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"Heart is
> beating...","wait":0}}] } 2018-01-16 17:00:15,427 DEBUG [c.c.a.t.Request]
> (pool-2-thread-5:null) (logid:bb993597) Seq 4-6582855280332112812: Received:
> \{ Ans: , MgmtId: 161334379813, via: 4(hv02.cloud.local), Ver: v1, Flags: 10,
> { Answer } } 2018-01-16 17:00:15,427 DEBUG [c.c.a.m.AgentManagerImpl]
> (pool-2-thread-5:null)
[jira] [Commented] (CLOUDSTACK-10233) When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in metadata is missing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328551#comment-16328551 ] ASF GitHub Bot commented on CLOUDSTACK-10233: - fmaximus opened a new pull request #2410: CLOUDSTACK-10233: use namespace in Libvirt domain metadata. URL: https://github.com/apache/cloudstack/pull/2410 The documentation of Libvirt specifies the requirement of using an XML namespace, when having metadata in the Domain XML. The Nuage extenstion metadata was not adhering to this specification, and the lastest Libvirt version ignores it in that case. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in > metadata is missing > --- > > Key: CLOUDSTACK-10233 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10233 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: cloudstack-agent >Affects Versions: 4.11.0.0 > Environment: Nuage VSP plugin on RHEL 7.4 >Reporter: Raf Smeets >Assignee: Frank Maximus >Priority: Critical > > When installed ACS 4.11 on top of Rhel7.4 baseimage with libvirt-3.2.0 ,there > is an issue with the metadata of the created VM in cloudstack. > It leads to password reset failure as the nuage vrs is not allowing passage > to DomainRouter. > After debugging , it was found that the nuage-extension in metadata was > missing. > When cloudstack-agent is preparing xml to be sent to openvswitch it contains > metadata with nuage-extension block as follows > > > > > > In /var/log/openvswitch/vm-monitor.log , the received XML of VM is without > nuage-extension block in metadata as follows: > Jan 15 18:17:17 ovs-1 vm-monitor.log: > So the metadata block is now empty. It seems libvirt 3.2.0 requires an url in > its metada, so the libvirt namespace needs to be adapted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328545#comment-16328545 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358249028 @blueorangutan package This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328544#comment-16328544 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358248079 Let's hold on merging this -- we need to run tests across xenserver, vmware and kvm before this may be accepted. This will potentially break every other outstanding PR, but agree if it needs to be done now is a good time. Let me also find some time to review the PR. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328546#comment-16328546 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - marcaurele commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358249056 @rafaelweingartner thanks, i will as soon as @rhtyd give me a go This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328540#comment-16328540 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358248079 Hold on, we need to run tests across xenserver, vmware and kvm before this may be accepted. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328533#comment-16328533 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - rafaelweingartner commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358245330 @marcaurele please do the honors and merge this one P.S. you are going to generate conflicts in my PRs :( This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328482#comment-16328482 ] ASF GitHub Bot commented on CLOUDSTACK-10105: - DaanHoogland commented on issue #2283: CLOUDSTACK-10105: Maven standard URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358234425 gogogo This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Follow maven standard for all modules > - > > Key: CLOUDSTACK-10105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Marc-Aurèle Brothier >Assignee: Marc-Aurèle Brothier >Priority: Minor > > The goal is to remove the custom module layout used and follow maven standard > structures for all. This will remove one module. It's only a matter of moving > files around to their correct location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CLOUDSTACK-10147) Disabled Xenserver cluster can still deploy VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henko Holtzhausen reassigned CLOUDSTACK-10147: -- Assignee: Henko Holtzhausen > Disabled Xenserver cluster can still deploy VMs > > > Key: CLOUDSTACK-10147 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10147 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, UI >Affects Versions: 4.10.0.0, 4.9.2.0 > Environment: Xenserver 6.2, 7 >Reporter: Glenn Wagner >Assignee: Henko Holtzhausen >Priority: Major > > ENVIRONMENT > = > XenServer Version : 6.2 , 7 > ISSUE > == > Disabled Xenserver Cluster can still deploy VM's , hosts in the cluster are > still active > Repro. steps followed > == > Disabled Cluster from UI. > Deploy a new VM > Expected Behavior > === > After disabling the cluster , the hosts should be disabled. and no VM's can > be deployed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
