> a.) _is_viable_platform will attempt to log an event even if not on
azure. maybe that shouldnt happen.
Maybe!
> b.) _is_viable_platform will return true even if asset_tag failed, but
/var/lib/waagent/ovf-env.xml existed.
I don't _know_ that this is the reason, but is it possible that the
(Marking this Triaged/Low, as we're talking about cleaning things up,
rather than fixing an issue that we know of, I believe.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868077
Title:
A new
@Mohammed, Thank you for your help. I dont think we need anything
else from you.
Scott
On Mon, Mar 23, 2020 at 2:10 PM Mohammed Sameer B
<1868...@bugs.launchpad.net> wrote:
>
> @Scott,
>
> So shall I consider the issue fixed or still some troubleshooting needs
> to be done?
>
>
> Thanks
>
> --
>
@Scott,
So shall I consider the issue fixed or still some troubleshooting needs
to be done?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868077
Title:
A new feature in cloud-init
@Mohammed,
I was hoping for /var/lib/cloud contents *before* running 'cloud-init clean'.
The other logs look fine.
@Other cloud-init devs,
I'd like someone else to hazard a guess at what went on here.
The general issue is:
* very old cloud-init (0.7.9) booted on azure
* migrated to ec2,
@Scott,
i think it is now working fine after running this command "cloud-init
clean --logs --seed".
I have attached cloud-init collect-logs output and "tar -C /var/lib/
-cvf var-lib-cloud.tar.gz cloud/". Can you please check and confirm that
everything is working fine?
** Attachment added:
++ PFA cloud-init collect-logs
** Attachment added: "cloud-init.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1868077/+attachment/5339792/+files/cloud-init.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It really seem slike you still have /var/lib/waagent around.
See lines in your log like:
2020-03-21 07:36:37,988 - stages.py[DEBUG]: restored from checked
cache:ataSourceAzure [seed=/var/lib/waagent]
For reference, could youp lease attach:
tar -C /var/lib/ -cvf var-lib-cloud.tar.gz cloud/
@Scott,
I have removed walinuxagent and deleted /var/lib/waagent. But when I
restart the server, again I am facing the issue. I have attached cloud-
init collect-logs output for our reference.
Thanks
** Attachment added: "cloud-init.tar.gz"
@Mohammed,
the cloud-init.log clearly shows cloud-init still using the Azure datasource
due to the presense of /var/lib/waagent
I would suggest removing that directory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Scott,
I have updated cloud-init to 19.4 version. But still I am facing the
same issue.
Attached cloud-init collect-logs output for your reference.
Kindly help in fixing the same.
Thanks.
** Attachment added: "cloud-init.tar.gz"
I'd suggest making the changes, and inserting a ssh key that you have
access to into root.
Then reboot and see what happens. You should then be able to log in
and debug a bit, run 'cloud-init collect-logs' and post here.
On Fri, Mar 20, 2020 at 10:20 AM Mohammed Sameer B
@Scott,
I have the image of server before making that change.
So Can you assist me on how to fix cloud-init data source
identification?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868077
@Mohammed,
If you are using an EBS root, then you can detach the volume and attach
to another instance and then collect logs from it.
I might suggest that you make a snapshot, then change the volume to and
add an ssh key to root's ssh keys and then re-attach that volume to the
original instance
Hi Scott,
I removed waagent, ran this command 'rm -Rf /var/lib/waagent' and
upgraded cloud-init to 19.1.
But after reboot, I am unable to login to the server itself.
Can you suggest a way to fix cloudinit data source identification?
Thanks
--
You received this bug notification because you
@Mohammed, I would do a 'rm -Rf /var/lib/waagent' before migrating
future images. And I'd suggest that you can probably just 'touch
/var/lib/cloud/instance/warnings/.skip'. But your system is in a wierd
state.
@Cloud-init devs,
What happened here was:
a.) instance booted on Azure
b.)
Hi Scott,
As requested, I have added the output.
Thanks.
** Attachment added: "cloud-init collect-logs output"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1868077/+attachment/5338954/+files/cloud-init.tar
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => New
Hi Mohammed,
Please attach the output of 'cloud-init collect-logs' and then set this back to
New.
Thanks.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
** Tags added: dsid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The above mentioned server was freshly migrated from Azure CLoud to AWS
cloud
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868077
Title:
A new feature in cloud-init identified possible
19 matches
Mail list logo