2020-09-02 05:24:40 -0500 | 获得奖牌 | ● 著名问题 (source) |
2020-06-30 15:58:04 -0500 | 获得奖牌 | ● 著名问题 (source) |
2020-06-30 15:58:04 -0500 | 获得奖牌 | ● 热门的问题 (source) |
2020-06-30 15:58:04 -0500 | 获得奖牌 | ● 受欢迎的问题 (source) |
2020-04-15 03:39:22 -0500 | 获得奖牌 | ● 热门的问题 (source) |
2020-04-15 03:39:22 -0500 | 获得奖牌 | ● 著名问题 (source) |
2020-04-15 03:39:22 -0500 | 获得奖牌 | ● 受欢迎的问题 (source) |
2019-11-21 11:15:45 -0500 | 获得奖牌 | ● 热门的问题 (source) |
2019-11-21 11:15:45 -0500 | 获得奖牌 | ● 著名问题 (source) |
2019-10-21 16:19:43 -0500 | 获得奖牌 | ● 好问题 (source) |
2019-10-09 10:03:23 -0500 | 获得奖牌 | ● 热门的问题 (source) |
2019-09-03 20:32:25 -0500 | 评论问题 | unable to attach volume to instance Yes I did try anyway... The target gets set up and torn down within about 1 or 2 seconds, so of course log in failed. |
2019-09-02 20:58:14 -0500 | 评论问题 | unable to attach volume to instance hi, thx for your help. I already mentioned about iscsi - it does not get logged in, although the target gets created. iscsi is to the same host. This is a single host/controller/compute combined. |
2019-08-29 22:23:52 -0500 | 获得奖牌 | ● 受欢迎的问题 (source) |
2019-08-29 02:46:07 -0500 | 评论问题 | unable to attach volume to instance Sure! Could be the problem? - I was checking df -h : |
2019-08-28 20:54:30 -0500 | 评论问题 | unable to attach volume to instance I dont understand it and cannot post full log output here. But it looks like it sets up the iscsi connection, runs some commands then tears it down. It does not mention about trying to log in, or log in failures to the iscsi. |
2019-08-28 20:53:37 -0500 | 评论问题 | unable to attach volume to instance Same messages there in the volume log which say creating target then deleting the target. There are logs in between like "CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C vgs --noheadings --unit=g -o name,size,free,lv_count,uuid --separator : --nosuffix cinder-volumes" returned: 0" |
2019-08-28 02:38:32 -0500 | 问了问题 | how to ask a question for tripleo? Stuck with upgrade from pike I am looking to update the openstack Pike I have. I installed it by going through the guide on the tripleo website http://tripleo.org/ My first task is to update the undercloud instance. However the Pike repo is no longer present, so yum update fails: https://trunk.rdoproject.org/centos7-...: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. The The above no longer exists. I have checked For me to upgrade, my first task is to upgrade to the latest within the current version ( Any ideas how to move forward? |
2019-08-27 09:22:03 -0500 | 评论问题 | unable to attach volume to instance there is volume.log in /var/log/cinder this shows: Creating iscsi_target for volume: volume-73f060fc-e347 attachment_update completed successfully. Terminate volume connection completed successfully Removing iscsi_target: 73f060fc-e347 All for the same volume in question. How to increase verbosity? |
2019-08-27 09:18:52 -0500 | 评论问题 | unable to attach volume to instance volume service list shows all enabled / up: cinder-scheduler cinder-backup cinder-volume |
2019-08-27 04:44:36 -0500 | 问了问题 | unable to attach volume to instance I have a packstack all in one Queens host. It is one host and controller all-in-one and runs iscsi connections to it's own single IP address. For the most part, working well. However, the free memory has been depleted a few times due to load and occasional issues have begun. One of which is the following: At the moment I have one volume that is unable to attach to an instance. This was previously attached and running. But now it's unable to be reattached. command So far I have managed to discover the cinder api log with this: I Think the key part is The above log is always output to the cinder api log when I am attempting:
I googled for the openstack volume attach process and found this page: https://docs.openstack.org/cinder/pik... From what I understand, openstack sets up the iscsi target, saves the chap credentials somewhere and then uses that to login to the target. I tried to attach the volume again and repeatedly ran: It then counted to 47 and I confirmed with: So looks like the target is being created. The api log does show this although shortly after the log also shows the target being deleted and the I conclude that iscsi authentication is failing, but I have not seen this specific message in any cinder log. I have not located any iscsi log either. I googled how to enable debug log and found a how-to post for Centos (we use centos) how to start iscsid in debug mode.. I think it will affect running instances so I have avoided it. In cinder.conf we have: And the iscsi lvm config from cinder.conf: Could anyone help me move forward in the right direction? I am a bit stuck at this point. |
2019-08-26 04:06:08 -0500 | 问了问题 | power state = no state and cannot attach volume to instance Unsure what occurred to lead to this condition but at the moment I have the following: - An instance in shutoff state but with "power state" as NOSTATE - no volume attached to the instance The instance was running and it was noted the instance was no longer running. I attempted to change the power state by running : But this only changed the status frmo "shutoff" to "active" so it appears that I've created another problem to solve. I have searched and cannot locate how to reset the power state. What options do we have? Is the only option to manually edit the db? I am trying to avoid doing that if at all possible. This is the first issue. Once this issue is resolved I think I can re-attach the volume ( fingers crossed :) ). Looking for guidance on the power state here. Any advice appreciated |
2019-05-13 21:56:02 -0500 | 评论问题 | Unable to update cinder volume type property error 400 Any tips for this? |
2019-05-08 23:15:35 -0500 | 评论问题 | no process found ( nova-compute / neutron) I had good results following this https://www.rdoproject.org/install/pa... give it a go.techrepublic might be out of date,,, OR might be a bug in the git repo you pulled from. |
2019-05-08 03:18:24 -0500 | 评论问题 | Problem to install my overcloud with trippleO - No valid host was d I reciprocate ARatcliff - I had this same problem as you when I went about installing openstack. Can you access the director (undercloud) gui? From memory, you need to scan your overcloud hosts and then afterwards, tag them so that openstack knows how to treat them. |
2019-05-08 03:15:00 -0500 | 获得奖牌 | ● 编辑 (source) |
2019-05-08 03:14:48 -0500 | 问了问题 | Unable to update cinder volume type property error 400 I have a volume type configured and it's working well for the most part. I would like to add an extended property to slightly change the behaviour. The volume type is below for reference, with existing properties: So what I am doing here is setting the propertly like this: The error is that the item is in use. In what context is this in use as I do not follow? I have not modified this at all since it was initially set up around a year ago. Back then I dont recall having this error 400 problem. I've tried an older openstack CLI as well as via Horizon with same issues: How do I go about setting the extended property on this volume type? I guess the type is in use, how do I go about making it unused so I can set the property? |
2019-04-02 23:32:45 -0500 | 获得奖牌 | ● 著名问题 (source) |
2019-02-04 03:35:45 -0500 | 获得奖牌 | ● 热门的问题 (source) |
2019-02-04 03:35:45 -0500 | 获得奖牌 | ● 著名问题 (source) |
2018-11-05 05:42:21 -0500 | 获得奖牌 | ● 著名问题 (source) |
2018-09-05 02:04:32 -0500 | 获得奖牌 | ● 热门的问题 (source) |
2018-09-05 02:04:32 -0500 | 获得奖牌 | ● 受欢迎的问题 (source) |
2018-08-13 13:02:55 -0500 | 获得奖牌 | ● 热门的问题 (source) |
2018-07-19 08:58:09 -0500 | 问了问题 | What are the steps to use an external dhcp server with vlan or flat provider? I have a Pike openstack with 1 controller/network node and 2 x compute nodes. The controller / network node is a VM. The compute nodes are physical. I have configured a VLAN network and launched some instances but they are not receiving DHCP most of the time. BTW the gre networks and floating ip's to through the controller/network node is working fine but as it's a VM there's a limitation where I'm unable to use VLANs through the VM. I decided to configure an external dhcp server for the VLAN network. What I find is 1) the external DHCP server offers a DHCP to the instance on openstack, but openstack shows that it has a different IP. This in turn breaks IP connectivity to the instance because the iptables rules do not match the instances IP. I have tried having no dhcp on the openstack network config but I find that openstack still configures an ip there. How can I move completely to external dhcp for the VLAN network? Seems it's conflicting with openstack somewhere, but i am unsure as to where exactly. |
2018-07-18 22:29:09 -0500 | 获得奖牌 | ● 受欢迎的问题 (source) |
2018-07-18 06:30:36 -0500 | 评论问题 | No valid host was found during instance migrate I spent 6 hours looking for ghost logs today lol. openstack compute service list 8 | nova-compute | overcloud-novacompute-1.company.com | nova | enabled | up It's back and running again. |
2018-07-18 06:28:21 -0500 | 评论问题 | No valid host was found during instance migrate ...is deprecated in Pike, but it works. Another thing which helped me was to launch a VM with a flavour that has all storage values as '0' (swap and disk etc). This successfully launched. After increasing nova.conf host disk overcommit, live migration works. |
2018-07-18 06:26:44 -0500 | 评论问题 | No valid host was found during instance migrate Sorry, I forgot to add that yes it does. I have since managed a workaround. (ps this website stops working sometimes, seems like db connection issue). The workaround was to set disk overcommit higher than 1.0. My theory about disk seems correct. BUT the value I changed has a warning that it... |
2018-07-18 06:26:44 -0500 | 获得奖牌 | ● 评论员 |
2018-07-18 01:37:12 -0500 | 评论问题 | No valid host was found during instance migrate i think this issue might have something to do with the fact that the instance flavours have defined swap values which result in consuming disk space on the host for swap only.
|
2018-07-18 01:32:52 -0500 | 问了问题 | No valid host was found during instance migrate I am not sure what I am missing here. I am trying to migrate instances from one host to another but now stuck at "No valid host was found" after migrating some instances successfully. It seems though nova thinks there are no resources but there are no logs at all pertaining to the destination host. I have a 3-node set up: 1 x controller and 2 x compute nodes. I have call the compute hosts compute-0 and compute-1 hosts. The compute nodes have shared iscsi storage from cinder. Before live migrating actions, we have instances running on both hosts without issue. Version is Pike. I was initially trying to migrate instances using the "openstack server migrate" command, but I was getting errors about there not being enough free disk on the destination. This is due to a bug with that specific command and using "nova live-migration" command instead was able to immediately live migrate. But now I have run into another issue and cannot work through it. I am checking logs in: nova-scheduler.log nova-api.log nova-conductor.log nova-placement-api.log nova-manage.log nova-rowsflush.log I am trying to migrate an instance from compute-0 to compute-1. I ran a tail on all of those logs and receive this output below. I cannot see any detail pertaining to compute-1 but the logs state no available hosts. Compute-0 host has the compute service disabled to prevent new VMs from being scheduled there. I am unable to spawn new instances also. I am trying to do this with the command: nova live-migration 8b51e704-b2fb-4674-8d82-debe0c9ea9d2 --block-migrate Log output: (more) |
2018-07-09 08:34:34 -0500 | 获得奖牌 | ● 受欢迎的问题 (source) |
2018-07-06 06:22:34 -0500 | 评论回答 | How to boot windows instance from ISO? virt-install command not found on centos7 so this doesn't work. I guess some extra packages are required to be installed. Looking at the guide that is quite similar to what I had achieved, except I only created the instance using openstack cli and the instant loads using the ISO's already uploaded. |
2018-07-06 06:18:57 -0500 | 回答问题 | How to boot windows instance from ISO? I solved this. I managed to boot an instance with 2 x CDROM devices and 1 x empty volume. = problem solved. |
2018-07-06 03:21:29 -0500 | 问了问题 | How to boot windows instance from ISO? My goal is that I want to run a Windows Server instance in openstack and I'm confused as to how to achieve this. I have a Centos7 server running Queens all-in-one. I have copied the Windows Server ISO to this server as well as a separate ISO which contains the virtio drivers. My problem is that if I do manage to boot an instance from the Windows ISO, there's no way to perform an installation to the empty volume because I need to install drivers (from another ISO) to allow the instance to see the storage volume. I can't see any way of attaching 2 CDROM devices into the instance at boot time. I've tried making a volume out of the windows ISO and booting from the volume with the drivers ISO attached but the volume does not boot the instance and is stuck at the bios screen. Any suggestions on this? I've even tried making a new ISO from the two separate ISOs using centos CLI tools but I couldnt find a good source of info on that so I ended up with a non-bootable ISO. Can we hot-plug CDROM devices? So after booting the windows installer, can I detach and attach the drivers? Then after driver install, detach and attach the windows ISO once more? |