Glance Image 卡在queued状态

问题:

glance image 卡在了queued的状态

分析:

查看glance的图,应该是要走upload的步骤, 可以查glance-api.conf中定义的store是啥,我的定义是swift, 同时glance-api.log中也报错swift.
再查swift的log,发现是swift的的网不通进入swich,查看核对发现vlan id被人改成了错误的

Glance-api:49 ERROR swiftclient [req-5b37596a-f3d6-4ada-8ece-215f4706518c 62870b0414254865a44c83dbd63fc363 8f5ee47c91c34559b16c6f90af804e05 - - -] Container HEAD failed:..
swift-proxy:swift-proxy-server: ERROR with Container server 192.168.112.21:6001/swiftobj re: Trying to PUT /AUTH_b42409b0505344859c2b131e4f39b1cf: ConnectionTimeout (0.5s)

解决:

switch上正确配置swift的网络

背景知识

- Image在glance中的状态:
•queued
The image identifier has been reserved for an image in the Glance registry. No image data has been uploaded to Glance and the image size was not explicitly set to zero on creation.
• saving
Denotes that an image’s raw data is currently being uploaded to Glance. When an image is registered with a call to POST /images and there is an x-image-meta-location header present, that image will never be in the saving status (as the image data is already available in some other location).
• active
Denotes an image that is fully available in Glance. This occurs when the image data is uploaded, or the image size is explicitly set to zero on creation.
• deactivated
Denotes that access to image data is not allowed to any non-admin user. Prohibiting downloads of an image also prohibits operations like image export and image cloning that may require image data.
• killed
Denotes that an error occurred during the uploading of an image’s data, and that the image is not readable.
• deleted
Glance has retained the information about the image, but it is no longer available to use. An image in this state will be removed automatically at a later date.
• pending_delete
This is similar to deleted, however, Glance has not yet removed the image data. An image in this state is not recoverable.

- Tasks在glance中的状态
• pending
The task identifier has been reserved for a task in the Glance. No processing has begun on it yet.
• processing
The task has been picked up by the underlying executor and is being run using the backend Glance execution logic for that task type.
• success
Denotes that the task has had a successful run within Glance. The result field of the task shows more details about the outcome.
• failure
Denotes that an error occurred during the execution of the task and it cannot continue processing. The message field of the task shows what the error was.

Glance Image 卡在queued状态相关推荐

计算机屏保后无法进入登录界面,Win10锁屏界面无法登录卡在登录状态的应对办法...
使用win10系统过程中,在锁屏界面输入密码后一直卡在登录状态,约 20~30 秒系统又自动锁屏并重复这个过程,Win10锁屏界面无法登录卡在登录状态怎么办?现小编介绍Win10锁屏界面无法登录卡在登 ...
排查Pod卡在Terminating状态
排查Pod卡在Terminating状态参考: 终极好文章 https://www.jianshu.com/p/817f11912253 https://www.cnblogs.com/rongfe ...
慧荣SM2246主控开卡一直处于Pretest状态解决方案
最近在调试固态硬盘的时候,发现了一个问题:慧荣SM2246主控开卡时一直显示Pretest,一直过不去,现将相关的调试过程记录及总结归纳如下. 1.查看固态硬盘的各电源状态及电压是否在正常的范围内.经 ...
java项目close wait_java – 排除连接卡在CLOSE_WAIT状态
我一直有同样的问题,我一直在研究套接字来摆脱这个问题. 让我说几句话,但在我必须说我不是Java程序员之前. 我不会解释什么是close_wait,因为Brian White已经说过了应该说的一切. ...
installing selected parcels阶段卡在activating状态
为什么80%的码农都做不了架构师?>>> 问题描述针对退役的datanode节点,进行重新服役,在安装软件包阶段(installing selected parcels),卡 ...
由于docker pull image失败,导致k8s pod卡在ContainerCreating状态
由于国内有一些公有云的服务器,访问docker.io非常不稳定, 导致pull image一直是失败的, nginx.yaml # cat nginx.yaml apiVersion: v1 kind ...
以yarn-client方式提交spark任务，任务一直卡在ACCEPTED状态
问题背景 spark是以客户端的方式安装的,并没有启动spark的mesos集群,这时候的spark就相当与hive客户端. 以local模型和yarn-cluster方式提交任务,都能正确额执行,但 ...
spark submit提交任务一直卡在ACCEPTED状态
千辛万苦写好代码,打成jar包,spark submit提交运行到yarn 然后默默打开yarn界面查看运行的任务,但是半天不见任务名称,这可就奇了怪了查看 yarn application --l ...
eclipse+tomcat 启动已有工程时卡在starting100%状态的解决办法
错误现象错误原因:加载mybatis的问题,有的错误,不会报错,但是会出现上面的现象我的错误地方在mapper.xml文件中我直接使用了类名但是却忘了配置以下内容,对实体类进行扫描,所以不能用别 ...

Glance Image 卡在queued状态

问题:

分析:

解决:

背景知识

Glance Image 卡在queued状态相关推荐

最新文章

热门文章