Closed akn9050 closed 4 years ago
Hi - which build of the ASDK did you install inside of the Azure VM? My understanding is, if you're using an Azure VM, 1907 is the latest build that works (https://github.com/yagmurs/AzureStack-VM-PoC) so you should use my Azure VM specific version: https://github.com/mattmcspirit/azurestack/tree/AzureStack-VM-PoC
Otherwise, do the modules exist in the path shown in the error message above?
Also, if you edit the AddImage.ps1 file, in your Scripts (in the same folder structure as where your AzSPoC.ps1 file is, and comment out line #423:
Import-Module "$modulePath\Syndication\AzureStack.MarketplaceSyndication.psm1"
We may not need to explicitly call that module any more, so try to see if that fixes it.
Hi Matt,
Thanks, I will try out commenting the line 423, I am using ASDK version 2002-35
Hi Matt,
UbuntuServerImage is still failing, this is the progress from last few hours
What's the error message in the UbuntuServer log, within your logs folder? I don't have an ASDK deployed right now, nor many cycles to validate, so if it's not a simple fix, it may take a few days for me to get to this.
And those screenshots don't show a failure...?
Here is the logs: UbuntuServer-0607-042730.txt
I think this could be the issue:
No existing suitable 16.04-LTS VM image exists. The image in the Azure Stack Platform Image Repository should have the following properties: Publisher Name = Canonical Offer = UbuntuServer SKU = 16.04-LTS Version = 16.04.20200318 Unfortunately, no image was found with these properties. Checking to see if the VHD already exists in an Azure Stack Storage Account
Are steps still executing? If so, which ones?
Let's wait until stuff has finished and then I can try to help troubleshoot, but i won't be online much today i'm afraid.
Hi Matt, No further progress, it still have 20 jobs completed, jobs after 20 doesn't making any change
Has the process completed though? For example, has the script stopped running and shows failed jobs, or are some jobs still in progress?
Some jobs are still in progress
OK, so I'd do the following:
CTRL+C to cancel the running script.
#First let's stop the jobs running and clean up
Get-Job | Stop-Job
Get-Job | Remove-Job
#Then lets reset the progress DB
$sqlServerInstance = '(localdb)\MSSQLLocalDB'
$databaseName = "AzSPoC"
$tableName = "Progress"
$progressStage = "UbuntuServerImage"
Invoke-Sqlcmd -Server $sqlServerInstance -Query "USE $databaseName UPDATE Progress SET $progressStage = 'Incomplete';" -Verbose:$false -ErrorAction Stop
Read-SqlTableData -ServerInstance $sqlServerInstance -DatabaseName "$databaseName" -SchemaName "dbo" -TableName "$tableName" -ErrorAction SilentlyContinue -Verbose:$false
The last step of that code above should show the UbuntuServer stage as incomplete.
Close all PowerShell windows.
Then, log into the Admin Portal - Region Management - Compute - VM Images, and check for an Ubuntu image - if there is one there, delete it. I don't think there will be one, but worth checking.
Then, I'd like you to test this on the ASDK host:
Install-Module -Name 7Zip4PowerShell -Verbose -Force
Does that work? Are there any issues when installing that module?
If that module installs correctly, you should be all set to re-run the script with your initial command.
I'll take a look in the morning.
Thanks Matt
okay Thanks, I will try this now
Hey Matt,
Thank you very much, It worked fine and script execution worked successfully and all the jobs got succeed. The changes you suggested + I changed ubuntu vhd version line $azpkg.vhdVersion = "16.04.20200529"
Thanks - i would avoid changing the vhdversion in future, as I usually update it whenever there is a new ASDK release (i run a test script to validate the Ubuntu image is valid). In this case, it seems that it's worked fine for you, so that's good. I've found some of them randomly not work on Stack Hub, so picking the latest one isn't always successful.
Thanks!
Describe the issue Hi Matt, Ubuntu and windows server image download jobs are failing due to that RP jobs are also failing.
Hardware
Send the logs Sent the logs.zip file in mail.
Additional context I tried in multiple instances facing the same issue.